QOps 3.1.2

November 2026

Updates and version switching: the latest build of your channel, in both PowerShell editions

The version panel in the Portal works with the latest build of the update channel you chose. Check for updates says either You do not have the latest build from the <channel> channel, with Download <version>, or You already have the latest build from the <channel> channel, with Switch to <version>. After a confirmation the Portal installs the build or switches to it, and offers Restart on <version> right away, also when that build is older than the one the Portal runs. A switch to an older version says that features, bug fixes and settings from newer versions are not available in it. The panel, the status bar and the What's new link show the QOps version the Portal was started from.

From PowerShell, QOps-Update -IgnoreInstalledFromOtherChannels installs the latest build of the channel this computer is set to, or of the one given with -Channel, even when a newer build from another channel is installed, for example to go back to the release build after trying a pre-release. QOps-Update -CheckOnly reports whether that build is installed. See QOps-Update.

Every update goes into a folder of its own named after the version, on Windows as on Linux and macOS, including QOps-Update -Force. No PowerShell window is closed and no other version is removed, and the new folder is checked to load QOps before QOps switches to it.

QOps-SetVersion, QOps-Update and QOps-Version -Installed work with the module folder of the PowerShell you run them in, so PowerShell 7 switches to the PowerShell 7 build. A Portal started from Windows PowerShell 5.1 runs QOps commands in PowerShell 7 when it is installed, so QOps-Prepare on Qlik Cloud works from such a Portal. QOps-SetVersion also switches the MCP server that assistants such as Claude Desktop start; restart the assistant after switching. A Portal started from Windows PowerShell on an earlier version updates and restarts into this version from the Portal. Leaving an earlier version from the console still needs one PowerShell restart; every switch after that works.

The QOps-Setup installer installs for all users

QOps-setup.msi installs for all users of the machine and asks for administrator rights when the installation starts. Its Destination Folder page shows the Windows PowerShell 5.1 and PowerShell 7 module folders. For a per-user install without administrator rights, use QOpsModule.msi. A QOps-Setup installed earlier with Install just for you is not removed by the upgrade; remove it from Settings > Apps. The installers are on the Installation page.

GitHub Codespaces: the repository is ready when the Portal starts

In a GitHub Codespace, QOps-StartPortal registers the repository the Codespace was opened on, so the Portal and the AI assistant list it without Add repository. When your QOps configuration has no default profile yet, an empty one is added for you to fill in with your Qlik connection. Outside a Codespace nothing changes.

AI assistant (MCP): more chart settings, safer chart changes, shorter answers

  • More chart settings. The assistant knows the full list of settings it can change for each chart type, explained in plain words: titles, legend, labels, axes, grid lines, colours, sorting, number formatting, reference and trend lines, conditions, alternative dimensions and measures, table totals and pagination, and the Styling panel. It sorts a chart's dimension and changes each setting the same way Qlik does when you set it in the properties panel.
  • Safer chart changes. A property name, value or Styling setting the chart does not read, or a chart setting sent to a sheet, is refused before anything is written, and the answer names the right one. Settings behind an Auto switch, such as pie chart labels, are applied in one step.
  • Register a repository from the assistant. Ask it to register a repository folder and it is added to the same list the Portal uses, under the same rules as Add repository in the Portal.
  • Answers that fit the assistant's conversation. Master item, variable, object, application, lineage and data tools answer with a summary or a page first and give the rest on request, and the qops operation tools return the end of the command output. A complete answer that is too long for one reply is written to the repository's self-ignoring .mcp-files folder, where the assistant can search it. Prompts or scripts that read full details from these tools need includeDetails, includeProperties, section or full=true.

Fixes

  • A global configuration that cannot be read is kept when you save. The Portal refuses the change and shows the file's path and the reason, and offers Back up and start fresh; on the command line the same reset is QOps-Configure -ResetGlobal. The file is written to a temporary file first, so an interrupted write leaves the previous file intact.
  • QOps-Release -Sort sets the build and publish order, and parameters without effect are refused. -SkipCustomProperties on QOps-Build and QOps-Release, and -Ignore on QOps-Release, stop the command before anything is changed. QOps-Build has no -ServiceUrl parameter, and QOps-Reload and QOps-Publish have no -Placeholders parameter.
  • QOps-Publish on Qlik Cloud publishes an app copied or imported a moment earlier, and names an id that matches no app.
  • QOps-Prepare says when no app on the server matches the filter, and names the server and how many apps it returned for the profile.
  • An expired licence key is reported as expired, and a refused key does not block activating a valid one afterwards.
  • The version panel stops showing a failed restart once the Portal has been started again.
  • Add repository in the Portal refuses a relative path and an id with characters other than letters, digits, -, _ and .; repositories already registered under such an id keep working.