You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I found some problems with the DataGrid's loadData/updateDataset API involving paging, and I have a coding solution to fix them. That API call accepts a pagerInfo param with an "activePage" value. If no activePage is passed in, then page 1 is assumed (which is good). However, after going to page 2, then calling the loadData API, the pager will show the requested page number properly, but the grid will render the wrong page of rows.
Notice the pager shows "Page 1" (which is good), but the rendered rows are from page 2
(A similar problem happens when passing in an "activePage" value)
Expected behavior
When using the loadData/updateDataset API, the grid should render the correct page of rows. If no activePage is passed in, then the grid should render page 1's rows. If an activePage is passed in, then the grid should render that page's rows.
Describe the bug
I found some problems with the DataGrid's loadData/updateDataset API involving paging, and I have a coding solution to fix them. That API call accepts a pagerInfo param with an "activePage" value. If no activePage is passed in, then page 1 is assumed (which is good). However, after going to page 2, then calling the loadData API, the pager will show the requested page number properly, but the grid will render the wrong page of rows.
To Reproduce
Steps to reproduce the behavior:
(A similar problem happens when passing in an "activePage" value)
Expected behavior
When using the loadData/updateDataset API, the grid should render the correct page of rows. If no activePage is passed in, then the grid should render page 1's rows. If an activePage is passed in, then the grid should render that page's rows.
Version
Screenshots
Platform
Coding Solution
In datagrid.js find the loadData function and change line 1169 to be this (it fixes both issues):
if (this.pagerAPI) {
this.pagerAPI.activePage = pagerInfo.activePage || 1;
The text was updated successfully, but these errors were encountered: