ParamQuery grid support forum
General Category => ParamQuery Pro Evaluation Support => Topic started by: jax on June 18, 2014, 10:32:47 am
-
After I click Accept changes, make an ajax call to save the data, the dirty rows/cells are reset back to their original values instead of the newly saved values. The code examples in the demos show that the entire grid is reloaded with data stored in session. Why would you want to reload the entire grid when you have maybe only updated one cell? Is there not a way to leave the grid with newly saved data and not have to reload the entire again?
-
reloading the grid data makes sense if multiple users are working on the same grid or you want to keep the logic of computing dependent cells on server side.
But it's entirely upto you whether you reload the data after accept changes and you can skip it.
-
After I save changes, if I do not reload the entire grid, then the dirty cells are reset back to the original values, and it forces me to have to reload the grid. I do not want to reload the grid again and I do not want the dirty cells to reset the data after I save, how do I prevent this?
-
Either return the changes you want to commit from server side script
or
change $grid.pqGrid("commit", { type: 'update', rows: rows }); to $grid.pqGrid("commit", { type: 'update' }); in success callback.
line number 60 of this demo http://paramquery.com/pro/demos/editing_batch