Skip to main content
New Participant
September 10, 2026
Question

Native Excel Export Performance Degrades with More Columns – Does It Re-run the Grid Query?

  • September 10, 2026
  • 2 replies
  • 30 views

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:

  1. 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?

  2. 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!

2 replies

stefanhelzle0001
Brainy
September 10, 2026

Can you share any numbers? How much degradation do you see?

mathieud0001
Brainy
September 10, 2026

 

  • I would assume it does a separate query since the datasubset would only hold the records for the page being displayed.
  • Have you tried looking at query_record_type_trace.csv?

https://docs.appian.com/suite/help/26.8/Logging.html#query-record-type-performance-logs