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.
A refusal is now explained instead of returning the silence that looks like a search with no matches — the run says why it declined.
Syntax
QOps-ExportFile -Space [Space] -File [File] [-QlikPath [QlikPath]] [-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. A space can hold folders, and -File looks through all of them, matching the full name a file has in the space. Nothing matching is not an error: the command says what it searched for and how many data files the space holds, and returns nothing.
-QlikPath specifies the folder inside the space to read from, written with / or \, relative to the space. Optional. Named, the search is confined to that folder and -File may be the plain file name, because you have said where to look. The folder you name includes everything under it: -QlikPath archive reads archive/sales.qvd and archive/2025/sales.qvd alike.
-QlikPath is the folder on Qlik; -Path is the folder on your disk. It is the same -QlikPath that QOps-ImportFile puts a file into and that QOps-RemoveFile deletes in.
-Path specifies the local folder each exported file is written into. Optional. An absolute path is used exactly as written. A relative path is counted from the folder you are standing in (the one Get-Location reports), whether or not the repository's .qopsconfig sits above you. The folder is created if it is not there yet.
Left out altogether, the files are written into the repository's folder, the one holding .qopsconfig, which is not necessarily the folder you are standing in. Write -Path . when you mean the folder you are in; leaving the switch out and writing . are not the same request.
A file that sits inside a folder of the space keeps the folders below the one you named, and the one you named is not repeated. Without -QlikPath, archive/2025/sales.qvd is written to <-Path>\archive\2025\sales.qvd. With -QlikPath archive, the same file is written to <-Path>\2025\sales.qvd. The folders in between are created for you, two files with the same name in different folders stay separate files on disk, and nothing is ever written outside -Path. That is what makes -QlikPath on the way out and QOps-ImportFile -Root on the way back inverses of each other.
-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
QOps-ExportFile -Space Sales -QlikPath archive/2025 -File *.qvd -Path .\data