The scenario,
I am populating a grid using a stored procedure that pivots 2 normalized tables. When a user changes a cell value I send that change back to the database where a transaction is run to recalculate certain values in the normalized tables. I then rebind the updated stored procedure to the grid.
Problem
if the grid is being grouped by a column and it is expanded the grid resets and redraws itself thus collapsing itself. Obviously this is bad for the User.
My question is, is there a way I can update the grid without resetting/redrawing it. Would using a middle datasource work? I guess I could also save row state on the client side.
Thanks
I am populating a grid using a stored procedure that pivots 2 normalized tables. When a user changes a cell value I send that change back to the database where a transaction is run to recalculate certain values in the normalized tables. I then rebind the updated stored procedure to the grid.
Problem
if the grid is being grouped by a column and it is expanded the grid resets and redraws itself thus collapsing itself. Obviously this is bad for the User.
My question is, is there a way I can update the grid without resetting/redrawing it. Would using a middle datasource work? I guess I could also save row state on the client side.
Thanks