Exports the data of any generic object to an Excel file or a open XML file. If the object contains excluded values, those excluded values are not exported. This API has limited functionality and will not support CSV export from all types of objects. Consider using Excel export instead. Treemap and bar chart are not supported.
ExportData method is not supported in SaaS Editions of Qlik Sense.
Default limitations in number of rows and columns
The default maximum number of rows and columns in the Excel export file is:
- 1048566 rows per sheet. For pivot tables: 1048566 column dimensions. 10 rows can be added after the export.
- 16384 columns per sheet. If the number of columns exceeds the limit, the exported file is truncated and a warning message is sent.
Default limitation in number of columns
The default maximum number of columns in the export file is:
- 1000 to export to a CSV file
The exported file is truncated if the number of cells exceeds the limit. A warning message with code 1000 is sent.
There is an option to export only the possible values ( qExportState is P).
Default limitation in size
If the exported file is larger than the maximum value, then an out-of-memory error with code 13000 is returned.
Exported files are temporary and are available only for a certain time span and only to the user who created them.
Type of the file to export.
Path to the definition of the object to be exported. For example, /qHyperCubeDef . This parameter is mandatory if the file type is CSV_C or CSV_T .
Name of the exported file after download from browser. This parameter is optional and only used in Qlik Sense Desktop.
Defines the values to be exported. The default value is A.
If the exported file should be served only once This parameter is optional and only used in Qlik Sense Enterprise (Windows) Default value: false
<url of the exported file>
 Maximum number of cells in exported file exceeded. Data has been truncated.
|Array of Integer|
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!