Pagination in grid with property as source
While using property as a source in repeat grid, all the results are fetched shown in the grid. But with report definition as a source it fetched only results in one page and next set of results when we moved to next page.
In case we have lot of result to be shown using property as source, grid shows performance issues. What can be done to solve this issue?
Since we need to fetch results from external system on load of the grid, we need to use grid with property as source. We are using PRPC 6.2 SP2
Infosys
US
Even if we use defer load or progressive loading option, it will load entire data in clipboard so not sure if this can help from performance perspective if we have 500-600 records to be fetched.
Also this option may not work for some functionalities like bulk processing functionalities with select all option.
Pegasystems Inc.
IN
Did you consider using Paginate activity since that is the recommended approach in cases where data set is large and performance is an issue ?
You can populate the clipboard incrementally using the Paginate Activity.
Let us know if this helps
Infosys
US
What logic should be present in paginate activity? For testing I mentioned blank Test activity, but portal was not loading and getting Unhandled exception executing JSP error.
Also I am not sure how this will help to solve mentioned issue.
Consider below scenario,
On load of grid, or on change of drop down, we are calling external system and getting around 500 results. Now portal takes too much time to load since clipboard has huge amount of blob data