Native Excel Export Performance Degrades with More Columns – Does It Re-run the Grid Query?
Hi everyone,
We're using the native Export to Excel feature on a records-powered read-only grid, and we've noticed that export time increases significantly as the number of columns grows, even when the row count stays roughly the same. I wanted to check with the community on a few points:
-
Does the native export re-execute the underlying query? When a user clicks "Export to Excel," does Appian re-run the same query that populates the grid (re-fetching data from the data source), or does it reuse the dataset that's already loaded/paginated in the grid?
-
Where can we check logs for this? Is there a specific log (e.g.,
tomcat-stdout, application server log, or a dedicated export log) where we can see the actual query being run during export, along with timing/duration details? We'd like to confirm whether the slowdown is on the query side (DB) or on the Excel-generation/serialization side (building the workbook itself).
Thanks in advance!
