September 2026
Data files in a Qlik Cloud space: put them in, take them out, remove them
Three new commands work on the data files a load script reads with lib://<space>:DataFiles/<file> — QOps-ImportFile, QOps-ExportFile and QOps-RemoveFile. Each takes a name or a wildcard, so a whole folder of extracts goes up, or a set comes down, in one command.
An import replaces a name already in the space in place, so re-running it after a change is the same command each time. An export writes a file only after its length matches what the space reports, so a short export never arrives looking complete; a name already on disk is left alone unless -Force says otherwise. Large files come down in pieces, so a several-hundred-megabyte export takes minutes rather than failing. Removing deletes in Qlik immediately, with no local copy — take one first with QOps-ExportFile if you need it. All three are Qlik Cloud only.
Data connections from a Qlik Cloud tenant
QOps-PrepareDataConnections now reads a Qlik Cloud tenant as well as a Qlik Sense site, and writes one folder per connection under DataConnections, so the definitions travel with the rest of the project. The connection each space carries for its own data files is left out — Qlik owns that one — and the run reports how many.
Where the account cannot read a particular connection, the run carries on through the others: that one is named with the reason the server gave. This is the reading half; QOps-BuildDataConnections still talks to the on-premise service directly, and QOps-ShowDataConnections and QOps-AddDataConnections are unchanged.
Build or prepare one part of an application
QOps-Build and QOps-Prepare take a new -Path flag and act only on the objects under it — a folder such as Dimensions, one object such as Sheets/<id>, or a pattern such as Variables/v*. Everything outside the path is left as it is, on the server and on disk.
On a build the path is also a delete instruction: an object you deleted on disk inside the path is deleted in the application, while everything outside it stays untouched. A scoped build only ever edits an application that already exists — it never creates one and never leaves a copy behind — and where it cannot, it is skipped with the reason. The description and thumbnail live outside every object folder, so a scoped run leaves them alone unless the path names that file directly.
-Path works on Qlik Sense and Qlik Cloud; on QlikView it is refused with a message rather than silently ignored.
All of it from the Portal, with the buttons you choose
The Operations panel used to run five commands. It now runs twelve — the three data-file commands, the four data-connection commands, and -Path on Build and Prepare — and which of them get a button is your decision. All commands opens the full list, and anything in it runs straight from the list whether or not it's pinned. Up to nine commands can be pinned at a time.
Commands that don't work on applications ask for what they need in a dialog and show the exact command before it runs. Two say something extra first: Remove file deletes in Qlik immediately, and Add connections runs two commands when the filter is left empty, because only then does the second command read what the first one found. For a scoped run the panel shows what the scope implies: while a path is set, In-place is on and can't be changed.
Every command has its own reference page, reachable from the ⓘ next to it and from the Commands index. Your pinned set is kept per account, so it survives a restart and an update.
Changes to behaviour you may be relying on
A command that only connects leaves no configuration file behind. QOps-Prepare writes a .qopsconfig where you run it, because that file is what makes the folder a project. A command that connects and prints — QOps-Apps and its kind — no longer does: it keeps what it needs for the session in memory and leaves the folder as it found it. Inside a repository that already has a configuration file, it keeps being updated exactly as before.
Changing the line-ending setting now applies it to the configuration file itself, so the file carrying the choice is written in the endings it names.
A licence folder QOps cannot reach no longer stops the command. Where the folder holding the licence can't be read or written, the command continues and names the path and the reason. Commands that genuinely cannot proceed without the licence still stop, and now name the folder as well.