[puneetdhingrejaParticipant]

Believe me, It’s a very important feature and almost all of the existing market players provide the feature except yours.
Perhaps, you should provide this as a feedback to your developer team

[puneetdhingrejaParticipant]

There is no error message from the grid

[puneetdhingrejaParticipant]

Hello Hristo,
Thanks for replying. I am aware that the columns change their background color. But when you save this state, and visit the grid again after reloading the page, and you want to load the previous persisted state by parsing it to form database queries and getting the filtered data from server, then this background color is not visible and also the columns lose the filter values from the filter options.

When you work with local data, and all data is available to you at once, then this approach works fine with loadstate and savestate APis.

To make things easier to understand, I am doing the following.
1) I perform filtering on the DB server (not local data) when I Sort or Page or Apply filter on columns.
2) At this time the columns that I have applied filtering on, appear with changed background when the grid is loaded.
3) Now, I save this state by calling the savestate Api.
4) Next day, I come back to this page and see if there was a previous state saved for the grid, if yes, then I parse this state on the web server. I form queries from the saved state, hit the DB, get rows and populate the Grid. So , these rows are retrieved looking at data from saved state.
5) But now when the grid is loaded, I don,t see the changed color of the columns on which the filtering was applied, and neither do I see the column filter box retaining the filtered values.
6) This happens when I don’t have a loadstate APi called after I load the grid.
7) Because, If after loading the Grid from the server, I call loadstate on the state retrieved in step 4, then this makes another server call to the method which loads the grid initially.

Did this help you in understanding the situation?

[Author]

Posts