| Table of Contents |
|---|
Pagination in Easy Form Reports
This version adds a setting for controlling to control pagination in the Easy Form Report macros: "Max rows for client-side pagination". The The default value is 10,000 rows:
...
When If the number of rows in the report is less than or equal to the number in this setting then , client-side pagination is used in the report table. Else, server-side pagination is used.
Client-side pagination loads all rows of the report into memory in the browser (and on your server) and this thus, makes sorting and search filtering fast. The tradeoff is that it uses more memory than server-side pagination and, when if the number of pages is very large, it can bog down your server or your browser.
Server-side pagination loads only one page of data into memory in the browser (and on your server). It is a bit slower for sort/search but performs well for very large datasets (that is, reports with many submissions).
You can tune this parameter for your report macro adjusting the number lower give a lower number to give a preference to server-side pagination or higher to give a preference to client-side pagination in this parameter for your report macro. Set it to 0 to always use server-side pagination.
Server-side pagination has some the following limitations in sort/filter operations due to the limitations imposed by SQL and the database schema for reports.
...
:
You cannot sort based on a submission value if you are searching by a submission value . For that at the same time. In this case, you must sort by using another field, like the updated date, and then search by submission value.
Cannot You cannot sort multi-valued submission fields (checkboxes).
Cannot You cannot sort or search by user.
Sort and search are case-sensitive.