Export Analysis
Open an analysis, then choose Analysis Tools > Export Analysis. The collection must be loaded and analyzed before it can be exported. A complete analysis export is separate from Grid Export, which exports the current grid's displayed data.
Download a file
Choose to CSV, to Excel, or to SQLite to download the analysis tables.
| Format | Download |
|---|---|
| CSV | A ZIP archive containing the analysis tables as CSV files. |
| Excel | An .xlsx workbook containing the analysis tables. |
| SQLite | A .db SQLite database containing the analysis tables. CLI --output can choose another filename. |
These formats use the schema selected in Settings > Project Config > Project Options > Export Analysis schema. The setting applies to all three download formats. Latest is the default and resolves to V38 in QSDA 3.8. V38 replaces each resource table's MetaId column with its corresponding Linktable key name, for example Key_Expression.
If an existing ingestion script expects MetaId, select V37 before exporting, or select V38.Migrate to export the V38 columns alongside MetaId while the script is updated. See Export options and migration. The CSV archive includes export-schema.json with the resolved schema version and table/column descriptions, and a generated sample-export-loadscript.qvs matched to that schema. Use these to validate or update an ingestion script.
The CLI also supports these formats and can override the schema for one export:
qsda-cli collectors export-views <collectorId> --format xlsx --schema V37 --load --output analysis.xlsx
For the API, use GET /api/v1/collectors/<collectorId>/exportviews?format=csv&schema=V37. Send the request through the UI address and include the required bearer token; see QSDA API.
Excel exports also include QsdaExport and Doc worksheets for export metadata and column documentation; SQLite exports include tables with those names. Excel cells are limited to 32,767 characters, so longer values are truncated and marked ...[truncated]. Choose CSV or SQLite when long scripts or expressions must be preserved in full.
Export to Qlik
Choose Analysis Tools > Export Analysis > to Qlik to create a new Qlik app populated with this analysis's exported metadata.
- Select the destination Connection.
- Optionally choose a Stream or space. Leave it blank to use the work area or personal space. Desktop connections do not use streams or spaces.
- Optionally supply a Template AppId or Name. Otherwise, QSDA uses QSDA Export Template, uploading its bundled template if necessary.
- Choose Export. QSDA copies the template, sets its load script, and reloads the new app. A selected QSEoW stream causes the app to be published there; a selected Qlik Cloud space is used as the destination for the app.
- Review the result and use the created app link when available.
The connection's Qlik identity needs permission to create or copy apps, set the script, and reload. Uploading the default template or publishing/moving an app requires the corresponding permissions too. The export writes to the destination environment; it does not alter the source app being analyzed.
The Export to Qlik row limit defaults to 50,000 total data rows, excluding the Linktable. Increase it in Project Options if an export exceeds the limit. It is not a limit for CSV, Excel, or SQLite downloads.
If QSDA reports that the app was created but reloading failed, open that app and inspect its reload log. A failed Qlik Cloud space move can leave the app in the connection user's personal space; check the destination and service log before retrying, since another export creates another app.
Export to Qlik Template App
The only requirement for a QSDA Pro Export to Qlik template app is a special line in the load script that indicates where QSDA Pro will insert the exported data. The following line must appear exactly as shown somewhere in the load script of the template.
/*-- QSDA PRO EXPORT DATA --*/
Any additional script may appear before or after this line.
Collection exports and reports
Analysis Tools > Export Collection for support downloads a collection that another QSDA installation can import. Analysis Tools > Report generates a static HTML report. These serve different purposes from exporting the analysis tables. All can contain sensitive application information; see Data Privacy.