This question is locked. New answers and comments are not allowed.
Hi,
We've run into a couple of issues in the latest release, 2011.1.315, related to the page size drop-down on the grid.
The drop-down works great, but if the user has already paged through the grid and then selects a new larger page size, in some cases it ends up with a current page greater than the total pages. Because the grid stays on the same page when the page size changes, it displays the "No records" message, which can be confusing for the user - you have to page back to a previous page to see the data. (You can see this in the Grid Paging demo.)
Any suggestions for a good work-around, e.g. the best way to page back to the first or last page in that situation?
The other issue is in the GridRouteValues function - it is not saving the page size. We have worked around that by using our own GridRouteValues function & adding the -size to the route values, but we wondered if that would be addressed in a fix or future release.
Thank you.
We've run into a couple of issues in the latest release, 2011.1.315, related to the page size drop-down on the grid.
The drop-down works great, but if the user has already paged through the grid and then selects a new larger page size, in some cases it ends up with a current page greater than the total pages. Because the grid stays on the same page when the page size changes, it displays the "No records" message, which can be confusing for the user - you have to page back to a previous page to see the data. (You can see this in the Grid Paging demo.)
Any suggestions for a good work-around, e.g. the best way to page back to the first or last page in that situation?
The other issue is in the GridRouteValues function - it is not saving the page size. We have worked around that by using our own GridRouteValues function & adding the -size to the route values, but we wondered if that would be addressed in a fix or future release.
Thank you.