Brings a data file down from a Qlik Cloud space into a local folder. The file in the space is left exactly as it is. This is not the same as QOps-ExportQVF, which writes out a whole application — this writes out one data file the applications load from.
Needs Qlik Cloud. Run against a Qlik Sense or QlikView configuration, the command reports that data files are supported only in Qlik Cloud mode and stops without doing anything.
See also QOps-ImportFile for the other direction and QOps-RemoveFile for deleting a file from the space.
Syntax
QOps-ExportFile -Space [Space] -File [File] [-Path] [-Force] [-ChunkSize] [-SliceSize] [-Profile] [-Verbose]
-Space specifies the Qlik Cloud space holding the data files. Required. The space is found by name; the API key you are configured with has to be a member of it.
-File specifies the data file in the space to export, an exact name or a wildcard. Required.
-Path specifies the local folder each exported file is written into. Left out, files land in the folder you are standing in; the folder is created if it doesn't exist.
-Force replaces a local file that already has the name the export wants. Without it, that file is left exactly as it is and the export reports it as Skipped rather than Failed.
-ChunkSize sets how many bytes of the source file are fetched per call. Left out, it is 1 MB. Large exports are fetched in pieces so memory doesn't grow with the file's size; lower this for a tenant with a lower memory limit than the default assumes.
-SliceSize sets how many bytes are read per pass. Left out, it is 32 MB.
-Profile overrides default User Profile with the specified one
-VerboseLog enables full verbose output including complete API response dumps and debug information. By default, QOps now produces concise output summaries.
Examples
QOps-ExportFile -Space Sales -File Customers.qvd -Path .\data
QOps-ExportFile -Space Sales -File *.qvd -Path .\data -Force