Information from Qlik support :
Qlik Sense has a default limitation for export to Excel from the app. The exported file is truncated when the below number of cells are exceeded.
- Maximum 1,000,000 (1 million) cells are exported to an Excel file
- Maximum 5,000,000 (5 million) cells are exported to an CSV file
- 1,048,566 rows per sheet. 10 empty rows are added added at the end of the exported sheet.
- 16,384 columns per sheet.
Thanks for pointing this out. The April 2018 documentation lists both cell and row limitations which is a bit confusing. Wouldn't the cell limitation overrule the row limitation? Could you clarify if we should be disregarding the inclusion of cell limitation in this April 2018 documentation?
To confirm, in versions 3.x, should the rows go beyond the 1,048,566 limit you mentioned, does it automatically create a second tab sheet in excel to place the surplus rows or will the user still get a "truncated data" error message when exceeded?
Same question, for when the columns have exceeded 16,384? Exceeding column amount is not an issue for us, but just good to know.
What is the expected behavior of a session when exporting large volumes of data? Export is instantaneous? Export can make session appear to be locked up while processing the export request? Many times users get the false impression that that this is a straight forward process and there is never a mention of the experience. What happens on the server side? Can the server be impacted by submitting such requests? Is it possible to crash a server with such requests? I know I ask a slew of questions, but these types of questions are often encountered by accident after all of the above have already been identified as a challenge to the user and/or the administrator. Thoughts?