Streaming Export Driven by the Row-based Engine

Version

Function Description

Excel export, especially big-data Excel export, takes up a lot of memory, and may cause server memory overflow during high concurrency.
Therefore, the streaming export function is supported. Like draining a pool of water only from a small outlet (rather than from a pool of the same volume), the streaming export function greatly reduces memory usage.
Using the Excel Streaming Export Driven by the Row-based Engine plugin, you can export massive amounts of information (millions of rows of data records) with low memory usage and fast server response to the browser.

Streaming Export as Excel

Streaming export is supported in FineReport 11.0 by default. You just need to add the export parameter (rather than any other parameters) to enable streaming export.

After previewing the template, suffix the link with &format=excel and press Enter to streamingly export the template.

Note:

If you cannot open the exported file, your computer has locked the Excel file exported streamingly. You need to unlock the file in Properties, as shown in the following figure.

Streaming Export as Excel 2007 After the Row-based Engine Is Enabled

After enabling the row-based engine, the common export method is used as the FineReport export method by default. In this case, you can install the Excel Streaming Export Driven by the Row-based Engine plugin.

Plugin Installation

Download the Excel Streaming Export Driven by the Row-based Engine plugin.

For details about how to install the plugin in the designer, see Designer Plugin Management.

For details about how to install the plugin on the server, see Server Plugin Management.

Enabling the Report Engine Attribute

Choose Template > Report Engine Attribute to open the row-based engine setting page, as shown in the following figure.

Effect Display

The export result is the same as that in section "Streaming Export as Excel."

(1) Due to interface limitations, streaming export only supports Excel 2007 and later versions.

(2) The function is not supported on mobile terminals.