Data Entry Pagination 

Problem

During data entry preview on the frontend, all data is displayed on a single page. If the data volume is too large, the speed of displaying all data will be extremely slow due to the performance limitation of the frontend browser, affecting user experience.

In this case, to improve the speed of the data entry preview, during data entry preview, can reports be displayed in pages like the effect of pagination preview? The following figure shows the effect.

Solution

During data entry preview (op=write), you can use the parameter __cutpage__ (namely, suffixing the template preview URL with the parameter &__cutpage__=v) together with the pagination setting in Condition Attribute to realize the pagination effect.

Notes

1. cutpage is enclosed in double underscores.

2. The effect cannot be displayed on mobile terminals. Column pagination (namely, Paginate After Column and Paginate Before Column) is not supported.

3. After pagination, functions related to the page number, such as $$page_number, $$totalPage_number, and {A1}, cannot take effect.

4. When the solution is used together with the JS used to obtain cells, only the cells on the current page can be obtained.

5. After realizing data entry pagination with this solution, when you re-execute the query on the parameter panel, the page of the original page number will be displayed instead of returning to the first page. For example, when you browse through page five, if you click the Query button on the parameter panel, the system still attempts to display page five even if the new query result only contains three pages in total. In this case, a blank page may appear, or no data is displayed.

Data Preparation

1. Create a general report.

2. Create a dataset with the SQL statement SELECT * FROM OrderDetails_new limit 1000.

Template Design

Designing the body of the template

1. Drag the dataset fields into the corresponding cells.

2. Set Data Setting to List for cells A2 to F2.

3. Add text widgets for cells A2 to F2, respectively.

Setting Pagination After Row

Setting Paginate After Row aims to limit the number of rows displayed on each page.

1. Select cell A2, select Condition Attribute, and click + to add a condition attribute.

2. Set Attribute to Pagination and select Paginate After Row.

3. Add the formula condition (row() - 1) % 200 = 0 or seq() % 200 = 0.

Through this formula, each page displays 200 rows. If the page is still laggy, you can reduce the value.

Note: 

Since the sample report contains one header row, you need to subtract one from the total row numbers to exclude the number from pagination calculations. This explains why -1 is used in this formula. Modify the subtracted value based on the number of header rows in your reports in actual use.

Effect Display

Save the template, click Data Entry Preview, suffix the preview URL with the parameter &__cutpage__=v, and press Enter. The following figure shows the effect.

Note: 

The solution does not support mobile preview.

For details, you can download the template Data Entry Pagination.cpt.

Enabling Data Entry Pagination for Templates Mounted on the Platform

If you need to set pagination for data entry templates mounted on the platform, you can realize the effect in Parameter Setting. Set Name to __cutpage__, Type to String, and Value to v.

Freezing the Title Row

If you want to keep title rows fixed after pagination, you can set Repeat/Freeze, as shown in the following figure.