Question
3
Replies
48
Views
Posted: November 23, 2020
Last activity: December 1, 2020
Table with large data support (about 600,000 rows in DB and pagination with 1,000 rows per page)
Currently, we have requirements about table displaying for huge amounts of data with features as follows:
- support about 600,000 rows fetched from external database
- display pagination with 1000 rows per page with acceptable UI responsiveness
- support filtering/sorting/inline editing
We tried to POC those requirements, but the result is unacceptable by users due to slow UI responsiveness.
Anybody, please suggest me for the best approach for this.
Thank you in advance,
Reporting facilities in Pega are designed to support interactive reporting, and 600 pages with 1,000 rows per page exceeds that definition. Scrolling through 1,000 rows is not user friendly nor is paging through 600 pages. You need to think a bit more about how your users will be using this report.
If it truly needs to be used interactively inside the application, then you need to provide some reasonable initial filtering to substantially reduce the volume of data being presented. Your end users can then alter the filtering to suit their specific needs.
Make sure you are not trying to present a "one size fits all" report. If writing multiple reports against this external DB cuts down on the data for any given report and serves specific users better, then that is something that should be done.
Finally, if this report is being run specifically to export it (e.g., to Excel) then you should probably use BIX.