Report Row-based Engine-FineReport Help Document

Last update： 2020-12-14

I. Overview

1) When the data volume in a report is extremely large, it requires a long time to load data.

2) By default, the function of report engine is not used, but you can use this function to improve the loading speed of the report if the data volume is large and all data come from the same dataset.

3) The mechanism that report engine improves the loading speed:

a) Not use report engine: The report is rendered after all data are read.

b) Use report engine: The system only reads data for the page that a user is viewing, and then renders the report.

4) This article uses a MySQL database as an example to explain the methods to use report engine.

You will learn
Set attributes of report engine The scope of use

II. Steps

1. Create a new DB Query dataset

1) Create a new dataset [ds1].

2) Drag table [ORDERDETAIL].

2. Drag data columns to report body

1) Drag data columns of [ds1] to B3~E3.

2) B2~E2：Enter a title and fill with grey.

3) B2~E3：Align at the center and add borders.

3. Set the attributes of report engine

1) Choose [Template] > [Report Engine Attributes]

2) Check [Execute reports by row-based engine]. Check [Use page-based computation and separately execute report] and enter 30 as the number of records per page.

3) Choose Pagination Preview. Only 30 rows of data are displayed in each page.

III. The scope of use of report engine

1. Functions that are not supported by report engine

The aim of report engine is to improve the efficiency of reading data and the computation of each page is independent. Therefore, some complex functions are not supported when using report engine:

filter
summary of data columns
duplicate end rows
row height, column width, hyperlink, pagination after row, display and widget in conditional formatting
expansion attributes excluding vertical cell expansion
floating element
hierarchical cell indexing
row/column split
cross-sheet calculation
sub report, chart and formula
export to Excel