Originally posted by proggy
View Post
Client wants Grids on a form. The Grids represent hierarchical data. It must be possible to manipulate the Grids (add and delete parent and child rows) without persisting any data to the database tables until the form is submitted.
So this means I have to maintain a DataTable per grid in memory.
There is some GUI logic that says if the "Count" column of the Parent row does not have the correct number of child records then prevent form submission and display some client side validation.
Owing to the constraints of the BPM framework, this can only be done on the client side. So I need to effectively keep a client side copy of the DataTable.
JSON looked like a good approach. If you have to create JSON objects prepopulated with garbage then I agree, they are not what I need.
What would be a better client side technology? I wanted to stay away from basic arrays. JSON had lots of cool stuff baked in to decorate the columns with constraints which I liked.
Comment