Pageinated Listview retain current page when update method called.
When we page through data on our forms and then update an list item, the Listview rebinds and goes back to page 1. This is incredibly painful. Would it be possible to have an option to maintain the page in which we are currently on.
It seems to me that the cause of this is that all the data for the Listview is loaded upfront and then paged from K2 and not the database which means that when an update occurs the in memory representation is not consistent has to be reloaded. At this point K2 has no idea where you are within the paged results and so puts you back at page 1.
As support for SQL 2008 is dropping off, I suggest using offset, fetch and next from SQL 2012:
- To track where a user is within a Listview to return them to that place when the update has occurred.
- Faster initial query performance (as only returning the first page of data).
- Faster rebind performance as only showing the page that has changed.
I do realise that normal paging may suffer a little as would have to go to the database for each page of results but feel that this is far more usable than the current implementation allows.