This is a conceptual question...
I'm doing server-side advanced binding. My data source is stored in session state. The app allows a user to drill in on a particular row of the grid, which redirects to another page showing tons of detail not available in the grid. The detail page has previous and next buttons which allow the user to cursor through the rows that were displayed in the grid.
This works fine unless the user has resorted the grid. Drilling on the first record in the resorted grid, for example, gets me the original first record in the data source, not the data from the first row. (That is to say, DataSetIndex 0 no longer represents the same data as row 0 in the original data source.) It seems this is because the grid is using its own working copy of the data source I originally assigned. I could, of course, listen for sorting changes in the grid and resort the original data source along with what's happening in the grid, but that is a very inelegant solution.
What's a better way to do this?
I'm doing server-side advanced binding. My data source is stored in session state. The app allows a user to drill in on a particular row of the grid, which redirects to another page showing tons of detail not available in the grid. The detail page has previous and next buttons which allow the user to cursor through the rows that were displayed in the grid.
This works fine unless the user has resorted the grid. Drilling on the first record in the resorted grid, for example, gets me the original first record in the data source, not the data from the first row. (That is to say, DataSetIndex 0 no longer represents the same data as row 0 in the original data source.) It seems this is because the grid is using its own working copy of the data source I originally assigned. I could, of course, listen for sorting changes in the grid and resort the original data source along with what's happening in the grid, but that is a very inelegant solution.
What's a better way to do this?
1 Answer, 1 is accepted
0
Hello Tom,
The question set forth has been addressed in the support ticket which you have opened on the matter. To avoid duplicate posts, we can continue our communication there.
All the best,
Yavor
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
The question set forth has been addressed in the support ticket which you have opened on the matter. To avoid duplicate posts, we can continue our communication there.
All the best,
Yavor
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.