Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Problem with OOTB pagination (@baseclass. pyGridPaginator)

SA-1039

Summary



Using the Out of the Box (OOTB) control @baseclass. pyGridPaginator to provide pagination for a repeat grid, we see 3 issues:

1. When we add a row that would take the numbers of rows to the next page, focus remains on the current page instead of advancing to the next page with the new row.

Error Messages



None


Steps to Reproduce



1. add a row that would take the number of rows to the next page
2. delete the last row in a page.
3. input invalid data, then add a row that would take the number of rows to the next page


Root Cause



The root cause of this problem is software use/operation error.
 Row will be added on the same page, but as User's are firing “RefreshSection” onChange of the first element, the complete grid is getting reloaded and the newly added row is moved to next page.
However the focus remains on the first page.

Resolution



Explained to User that this is expected behavior, and the reason behind the behavior is "
Row will be added on the same page, but as User's are firing “RefreshSection” onChange of the first element, the complete grid is getting reloaded and the newly added row is moved to next page.
However the focus remains on the first page."

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us