Qlik Reporting-printed PDFs or Excel exports may not display fonts as expected, specifically when custom fonts are imported using CSS.

Resolution

This is expected behavior: 

• Custom CSS styling applied to sheets is not included in reports; see Customizing sheet styling with CSS | Qlik Cloud for details and recommendations.
• Qlik Reporting uses a set of open-source fonts and will automatically replace an unknown or unavailable font with a preset one; see Qlik Cloud Reporting and font support.
• Importing, for example, Google Fonts through custom CSS for use in reports and exports is not supported.

Related Content

• Customizing sheet styling with CSS | Qlik Cloud 
• Qlik Cloud Reporting and font support
• Fonts do not display properly in reports | Qlik NPrinting

Internal Investigation ID(s)

00463549

Environment

• Qlik Cloud

The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external data sources and tools.

This article provides step-by-step instructions for connecting Antigravity to the Qlik MCP server in any tenant.

Step 1: Create the OAuth client to be used by Antigravity

1. In the Qlik Cloud Administration activity center, go to OAuth.
2. Click Create new and use the following values:
   • Client type: Web
   • Name and Description: Name and describe your client
   • Add the required Scopes: user_default and mcp:execute
   • Redirect url: https://antigravity.google/oauth-callback
3. Click Create and copy the ClientID and Secret 

   Do not forget to save the client secret. Qlik will not show it again.

Step 2: Create the MCP connection in Antigravity

1. In Antigravity, open Antigravity IDE by clicking Open IDE
2. Click the ellipses (...) menu in the top right corner
3. Click MCP Servers
   
   
   
   
4. Click Manage MCP servers (A) in the top right corner and View raw config (B) to open your mcp_config.json
   
   
   
   
   
   
5. Enter your configuration in the following format:
   
   

   {
    "mcpServers" : {
      "qlik-mcp": {
        "oauth": {
          "clientId": "00000000",
          "clientSecret": "00000000" 
        },
        "serverUrl": "https://YOURTENANT.qlikcloud.com/api/ai/mcp" 
      }
    }
   }

   
   
   
   
6. Save your configuration
7. Return to Antigravity, go to Settings > Customization, navigate to installed MCP servers, and click Refresh
8. Click Authenticate 
   
   
   
   
9. A redirect takes you to the Antigravity URL; copy the Authorization code
   
   
   
   
10. Paste the code and click Submit
    
    
    
    
    
    

The connection is now available in a conversation.

Environment

• Qlik MCP
• Qlik Cloud

This article provides answers to the most frequent questions asked about Qlik MCP.

For the more general Qlik Answers FAQ, see Qlik Answers Agentic Analytics FAQ.

How do I troubleshoot my connection to the LLM I’m using?

Qlik Model Context Protocol (MCP) server integrates Qlik Cloud into your LLM workflow, allowing you to work with Qlik Cloud using your LLM without having to leave your LLM. Connection issues will often be tied to misconfiguration.

• Before you begin, review Deploying and administering Qlik MCP server and Connecting to the Qlik MCP server
• If you are using ChatGPT, verify that you are on the correct ChatGPT plan (see Connecting to ChatGPT)
• Typically, OAuth authentication issues with your client will be caused by:
  • Incorrect Remote MCP server URL (<your tenant URL>/api/ai/mcp)
  • Wrong Client ID
    
• If an error code is returned, reconnect; if reconnecting does not resolve the issue, submit the code returned by MCP to your LLM vendor for further troubleshooting

How do I troubleshoot my app if I am not getting the answers I expect?  

In a case where you do not get the response you expect based on the sources, or you receive an error:

• Ask again in case of an error (see the appendix for possible error codes)
• Rewrite the prompt (see Best practices for chatting with Qlik Answers)

Has your app been prepared for Qlik Answers?

• Best practices for preparing applications for Qlik Answers
• Writing master item descriptions for Qlik Answers

How much does the Qlik MCP cost?

For now, Qlik MCP will continue to be priced based on current models for the number of questions asked. You get capacity at corresponding levels in Standard, Premium, and Enterprise editions, as well as Qlik Sense Enterprise SaaS. There is currently no additional cost for structured data questions or task automation requests; a question is a question.

Use of the MCP server consumes questions when Qlik is accessed using Tool Calls. A Tool Call is a request made by the LLM to interact with Qlik's capabilities, such as, but not limited to, querying databases, calling APIs, or performing computations. These are typically visible in the LLM's log.

For Qlik's MCP server, 5 Tool calls consume 1 question. More questions may be purchased for expanded use cases.

See Pricing and the Qlik MCP server product description for details.

Qlik’s pricing does not include your chosen LLM subscription or usage, which will need to be paid separately.

Does Qlik MCP work with my existing Qlik apps?

Yes. Qlik MCP works on top of existing Qlik Sense applications and uses the same data, logic, and security model.

But to get the best experience, apps should be prepared beforehand:

• Best practices for preparing applications for Qlik Answers
• Writing master item descriptions for Qlik Answers

What capacity limitations do we need to consider?

Your Qlik Cloud subscription determines the quota of questions asked by users. If you are licensed for Qlik Answers, both MCP and Qlik Answers will use your monthly question capacity. See Administering Qlik MCP server. 

What happens when we reach a capacity limit?

Question capacity quotes are per month and reset every month. When you hit your limit, users can no longer ask questions until the next month. Overage is only allowed, depending on your subscription. For more information, see Qlik MCP server product description.

For more information on overage, see Overage. 

How do we turn off features?

Features can be turned off for individual users through user scopes.

1. Go to your Administration Center
2. Go to Manage Users
3. Switch to the Permissions tab
4. Click User Defaults and change the scope as required

See Control access to AI features.

The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external data sources and tools.

This article provides step-by-step instructions for connecting Gemini Enterprise to the Qlik MCP server in any tenant.

Step 1: Create the OAuth client to be used by Gemini Enterprise

1. In the Qlik Cloud Administration activity center, go to OAuth.
2. Click Create new and use the following values:
   • Client type: Web
   • Name and Description: Name and describe your client
   • Add the required Scopes: user_default and mcp:execute
   • Redirect URL: https://vertexaisearch.cloud.google.com/oauth-redirect
3. Click Create and copy the ClientID and Secret 

   Do not forget to save the client secret. Qlik will not show it again.

Step 2: Create the MCP connection in Gemini Enterprise

1. Create an application in your Gemini Enterprise console
   
   
   
   
2. Create a datastore
   
   
   
   
3. Select Custom MCP server and configure it as follows:
   • MCP server URL: https://{tenant url}/api/ai/mcp
   • Authorization URL: https://{tenant url}/oauth/authorize
   • Access Token URL: https://{tenant url}/oauth/token
   • ClientId: As copied from your Qlik Cloud OAuth application
   • Client Secret:  As copied from your Qlik Cloud OAuth application
   • Scopes: user_default mcp:execute 

     Scopes are separated by a space.

     
     
     
4. Once all details are filled, click Login and approve the consent dialog
5. Click Continue and optionally enter an MCP Server Description, as well as MCP Agent Instructions
6. Click Continue and provide a Data connector name
   
   
   
   
7. Click Create
8. Select the Datastore name
   
   
   
   
9. Click Actions in the menu to the left
   
   
   
   
10. Click Refresh custom actions
    
    
    
    
11. Select all tools to enable them and click Enable actions
    
    
    
    

Step 3: Using the connection

1. Return to your application and click Configure web application
   
   
   
   
2. Click the database icon
   
   
   
   
3. In the pop-up, click Authorize
   
   
   
   
4. You are now ready to test and use the application.

Environment

• Qlik MCP
• Qlik Cloud

For Qlik Sense Enterprise for Business (Cloud), see Loading of an app is hanging when using Qlik Cloud.

Working in a Qlik Sense app after remaining inactive causes fails with the error: 

Connection to the Qlik Sense engine failed for unspecified reasons. Refresh your browser or contact our system administrator

The issue specifically affects external users who have been inactive until a network device's (Firewall, Router, etc.) idle timeout was reached. This is followed by a connection reset for the TCP WebSocket session.

Cause:

TCP WebSocket connection is terminated by the firewall because the firewall is not receiving any TCP traffic such as keep-alive packets from client browser (e.g. Firefox, older Chrome versions).  Specific web browsers have their own tcp keep-alive behavior. 

This issue may be found with less frequency with IE because it sends the TCP Websocket keep-alive more frequent than any other main stream browser. Here are the default intervals for the three main browsers latest releases as of September 2020:

Default TCP-Keep-Alive intervals:

• Chrome: 45 sec
• Edge: 45 sec
• Internet Explorer: 30 sec (see IE: Change Keep-Alive timeout)
• FireFox 81.0: 10sec for ~2 minutes (115sec) period, then a keep-alive packet every 10 minutes; More details under Mozilla Networking Preferences.

General Information

This functionality is by default switched off not to affect any existing customers. Customers who do not experience any issues with web sockets terminated by the network due to inactive SHOULD NOT switch this feature ON since it will send unnecessary traffic on the network. See How are WebSockets used in QlikSense ? for more information.

How to configure?

1. Stop the Qlik Sense Proxy Service
2. Edit the file C:\Program Files\Qlik\Sense\Proxy\Proxy.exe.config This location may not be available if Qlik Sense was not installed in the default location.
3. Add the configuration key:
   

   <add key="WebSocketPingInterval" value="0"/>   <!-- Interval in seconds for the web socket ping to the client (a value of "0" is disabling the ping)–>

   Where value is a suitable positive number depending on the inactive web socket timeout setting in the network. The effective interval that the Qlik Sense Proxy server will send keep-alive messages towards the client my oscillate between 2 x value and 1 x value, since it also takes into account backend inter-process socket activity. Eg: setting the value of WebSocketPingInterval to 30 may lead to keep-alive messages sent to the client every 30 or 60 seconds.
   
   Note: The Qlik Sense Proxy service may not send keep-alive packets if it detects activity on that client's Websocket tcp session.
   
   Recommended is 60-300 second range, shorter interval generates more load on Proxy CPU and network. It should be set as high as possible, meaning it's best to identify at which interval an intermediate proxy cuts the connection when it perceives it as idle, and then set the ping interval to a slightly smaller value.
   
   A too small number (e.g. less than 30) will load the proxy and the network and IS NOT recommended. Suitable numbers could be 60 to 300 (i.e. 1 minute to 5 minutes), but it all depends on the network configuration (if the network removes web sockets that have been inactive for more than 5 minutes then, of course, the value must be set something less than 5 minutes (i.e. less than 300)). If a lower value is required, it is recommended to investigate the components involved in the connection, such as third party proxies and network load balancers to configure them with less restrictive timeouts. 
   
   It is possible that the same WebSocketPingInterval value has different behaviors in each Qlik Sense Hub section due to third party network device. The value may keep the connection live in Dashboardbut, but still lose connection in Data Load Editor. You may test with a lower WebSocketPingInterval value until the proper value is found to keep connection in all sections. For example, when connectingCloudFlare as web application firewall, theWebSocketPingInterval value may need to set to 10 seconds otherwise "connection lost" may still be received in Data Load Editor even the rest of Qlik Sense Hub keeps connected.
   
   
4. Restart the Qlik Sense Proxy Service.

Related content:

• Hub access times out with: Error Connection lost. Make sure that Qlik Sense is running properly  
• How are WebSockets used in QlikSense ?
• Loading of an app is hanging when using QlikSense Cloud
• Browser Timeout
• Qlik Sense HUB timeout even with session timeouts configured correctly
• Increase session timeout in QlikSense

Executing a data replication task with the SAP ODP endpoint on an SAP system that has the June 9th Security Patch installed may lead to the following error:

Failed to unload dataset – Unpermitted caller error message
Return type: E: Return row: 0 ID:RSAR number: 051

Resolution

According to SAP Note 3731818, there is an option to allow restricted ODP-RFC calls on systems with the security patch installed to proceed without interruption.  SAP Program RODPS_REPL_SECUREACCESS_OPTOUT is included in the SAP Security Patch from SAP Note 3635619. 

This program is executed on the SAP system with the Opt-Out of Secure Access to ODP API checkbox checked to disable the SAP Security Patch restrictions.  This program will be disabled with a future SAP Note to be released at the end of 2026 (Date TBD).

Cause

After installing the June 9th Security Patch, any Qlik Replicate using the SAP ODP endpoint will fail. The patch validates incoming ODP-RFC calls and blocks those from non-SAP applications. Pipelines will stop replicating until a migration to an alternative path is completed.

SAP provides a time-limited option to revert to unrestricted ODP-RFC calls, but this option expires in December 2026 and is explicitly at the customer's own risk. 

For Qlik's announcement on the same, see Important update on SAP Data Access Restrictions and your Qlik Integration: SAP ODP-RFC Changes.

Environment

• Qlik Replicate

This article walks through Send Message To Slack Channel as an action, a Qlik Automate template that is now available in the template gallery.

This template is a good starting point if you want to:

• Trigger a Slack notification directly from the Qlik Answers Assistant, an agent built on Qlik MCP, or a button on a sheet in Qlik Sense application, without writing any custom integration code.
• Accept just a channel name and a message at runtime, instead of hardcoding values inside the automation.
• Automatically resolve a channel name into the channel ID that Slack's API actually requires, for both public and private channels.
• Get back a clear, human-readable success or failure result, including Slack's own error details when something goes wrong.
• Reuse the same pattern as a base for sending action-driven alerts through other communication platforms, like email or Microsoft Teams

The template is available in the template picker. Go to Add new > New automation > Search templates, search for Send Message To Slack Channel as an action, and select Use template.

You will find a version of this automation attached to this article: "Send-Message-To Slack-Channel-as-an-action.json".

Content

• What this template does
• Before you start
• Step-by-step walkthrough
• Step 1: Start and Inputs
• Step 2: Slack - List Channels
• Step 3: Condition – Did List Channels fail?
• Step 4: Filter the list and set slackChannelId
• Step 5: Condition 2 - Was a matching channel found?
• Step 6: Slack - Send Message
• Step 7: Condition 3 – Was the message sent successfully?
• Why the run titles matter
• Customization ideas
• Tips for new users
• Troubleshooting
• Summary

What this template does

When this automation is called as an action, it does the following:

1. Collects a target Slack channel and a message through an Input block.
2. Pulls the full list of channels the connected Slack app can see, both public and private.
3. Looks up the channel ID that matches the channel name you provided.
4. Sends the message to that channel if a match was found.
5. Reports back a clear success or failure result and updates the run title so the outcome is visible at a glance in the automation run history.

Before you start

Before using this template, make sure you have:

• A Qlik Cloud tenant with permission to create and run automations.
• A Slack connection already configured and authenticated in your tenant.
• The exact channel name you want to send messages to, with the leading # optional

Step-by-step walkthrough

Step 1: Start and Inputs

This is the entry point of the automation.

How it works:

The Start block is set to manual run mode, but in practice, this automation is meant to be invoked as an action rather than run on a schedule. The Inputs block immediately following the Start block defines the two values every caller must provide:

• Slack message (textarea, required): the body of the message to send
• Slack channel (text, required): the channel to send it to

These two fields are effectively the contract for this automation. Whatever calls the automation (Qlik Answers Assistant, a Qlik MCP tool call, or a button on a Qlik Sense Application Sheet) has to supply both.

What you need to configure:

Nothing to get started. You can edit the field labels or help text, but keep both fields required since every later block depends on them.

Step 2: Slack - List Channels

How it works:

This block calls Slack's API to retrieve every public and private channel visible to your connection. It's needed because Slack's Send Message endpoint expects a channel ID, not a channel name; this block is the lookup table that makes that translation possible later in the flow.

What you need to configure:

• Connection: Make sure this block is connected to your Slack connection.
• Everything else is pre-set (the block already pulls both public_channel and private_channel types).

Step 3: Condition – Did List Channels fail?

How it works:

This condition checks whether the previous block returned an API error (an error response body or status).

Yes branch (List Channels failed):

The automation shows Slack's raw error response using an Output block and updates the run title to 'List Channels block failed with an error message' using an Update Run Title block.

No branch (List Channels succeeded):

The automation continues to the filter step to look up the channel.

What you need to configure:

Nothing. This condition is pre-built error handling.

Step 4: Filter the list and set slackChannelId

How it works:

This block filters the full channel list down to whichever entry's name exactly matches the channel name you provided, after stripping off a leading # (if you included one). The matching item (there should be at most one, since channel names are unique) is looped through, and its ID is written into a variable called slackChannelId. If nothing matches, slackChannelId stays empty, since it was initialized that way at the start of the run.

What you need to configure:

Nothing. This step runs automatically based on your "Slack channel" input.

Step 5: Condition 2 - Was a matching channel found?

How it works:

This condition checks whether slackChannelId ended up empty.

Yes branch (channel found):

The automation moves on to send the message.

No branch (channel not found):

The automation shows I can't find this channel... Please try again using an Output block, updates the run title with the same message using the Update Run Title block, and then ends without sending anything.

What you need to configure:

Nothing. This condition is pre-built.

Step 6: Slack - Send Message

How it works:

This block posts your message to the channel ID resolved in Step 4, using the text from the Slack message input. The message is sent with the display name Qlik Automate as a tool, so anyone reading it in Slack can tell at a glance it came from this automation rather than a person. A few optional Slack parameters in this block, like an icon or thread reply, are left blank by default and can be filled in for richer messages.

What you need to configure:

• Connection: Make sure this block is connected to your Slack connection.
• Everything else is wired automatically from earlier steps.

Step 7: Condition 3 – Was the message sent successfully?

How it works:

This condition checks the ok flag Slack returns from the Send Message endpoint.

Yes branch:

The automation shows 'Message was sent successfully ' and updates the run title to match.

No branch:

The automation shows Slack's raw error response body using an Output block and updates the run title to Send Message block failed with an error message using Update Run Title block, so you can see exactly why Slack rejected it.

What you need to configure:

Nothing. This condition is pre-built.

Why the run titles matter

Every outcome in this automation (a failed channel lookup, a channel that couldn't be found, a successful message send, or a failure) updates the automation run title to match. That means you can scan the automation's run history and immediately tell what happened in each run without opening a single run history, which is especially useful once this automation is being called repeatedly by an Assistant, MCP tool, or button rather than run by hand.

Customization ideas

You can adapt this automation to fit your own needs:

• Swap the destination: route notifications to a different destination platform, such as email, Microsoft Teams, or any other supported messaging connector instead of Slack. Depending on the connector you choose, you may need to adjust the Input block to provide the required parameters.
• Add more inputs: extend the Inputs form with fields like a thread reply ID, an emoji icon, etc., and then map them into the Send Message block's optional parameters.
• Simplify for a single channel: if this automation will only ever post to one channel, you can hardcode the channel ID and remove the Slack channel input text from the Input block / List Channels / Filter / Condition 2 branch entirely for a faster, simpler version.
• Add a fallback channel: instead of stopping when a channel can't be found, route the "Condition 2: No" branch to a default channel ID so the message always lands somewhere.

Tips for new users

• Test the automation with a channel name you know exists before wiring it up to a button, the Qlik Answers assistant, or an MCP tool.
• For List Channels and Send Message block to work, double-check that the Qlik's Slack app behind your connection has actually been invited to the channel; otherwise, it won't appear in the List Channels result, and you'll get the "can't find this channel" message even though the channel exists.
• Type only the channel name (for example, general); the leading # is optional and is removed automatically.
• Check the run history first. The run title alone tells you whether the channel was found, the message sent, or something failed; no need to open the output every time.

Troubleshooting

The automation fails with the following error messages:

"I can't find this channel... Please try again":

• Check the channel name for typos.
• Confirm Qlik's Slack app behind your connection has been added to the channel.

"List Channels block failed with an error message":

• This is most likely a connection issue; re-check or re-authenticate your Slack connection.
• The output shows a detailed error response from Slack. 

"Send Message block failed with an error message":

• The output shows a detailed error response from Slack.

Summary

This template gives you a ready-to-call building block for posting Slack messages as an action from anywhere in Qlik, the Qlik Answers Assistant, a Qlik MCP-connected agent, or a simple button on a Qlik Sense Application. By resolving channel names to IDs automatically and reporting a clear success or failure result at every step, it keeps the calling side simple: pass in a channel and a message, and get an outcome back. You can adapt it by changing the destination platform or swapping Slack out for email, Microsoft Teams, or adding richer message options.

It is not possible (or difficult) to select part of an expression containing right-to-left languages or a combination of Latin and Hebrew or Arabic.

Selecting and copying the entire formula with CTRL+A and CTRL+C functions as expected. 

This limitation complicates editing formulas, especially if they contain set analysis.

Resolution

While this is currently considered working as designed due to a third-party limitation, Qlik is actively working on improving the expression editor in the future. Stay up to date by reviewing our Release Notes in future releases.

Internal Investigation ID(s)

SUPPORT-10479, TLV-1477

Environment

• Qlik Cloud

When purchased, our Qlik products are delivered with a 16-digit license key (LEF) and/or the Signed License key (SLK). What key is applied may differ depending on your requirements or the version of the product. See The Qlik Signed License Key and the License Enabler File for details.

To manually obtain your LEF:

1. Make sure to have the 16-digit license key at hand
2. Open the LEF Server (http://lef1.qliktech.com/manuallef/default.aspx)
3. Type in the license key
4. Check the "I'm not a robot" box and complete the identification task if prompted
5. Click Request LEF

The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external data sources and tools.

Connecting Perplexity to the Qlik MCP server means you can get Perplexity’s real-time web search and reasoning alongside Qlik’s governed analytics data in a single conversation, or have it take action to manage operations within your Qlik Cloud tenant.

What you'll need

• A Qlik Cloud tenant with the MCP server enabled by a tenant administrator. Review Deploying Qlik MCP server for a tenant for details.
• A Perplexity Pro, Max, or Enterprise account (accurate at time of writing). If using an enterprise account, you must have permission to create new connectors, or ask an administrator to help.
• Tenant administrator access in Qlik Cloud to create an OAuth client.

How the Qlik MCP server works

A short orientation before touching any settings:

• The MCP server URL follows the pattern https://<your tenant URL>/api/ai/mcp.
• All connections are user-bound: access tokens are scoped and time-limited, and data access is enforced by the same access controls as when a user uses the interface directly.

See Qlik MCP server for details.

Which OAuth client type should I use?

Before creating the OAuth client in Qlik Cloud, decide which client type fits your situation. For connecting Perplexity, the relevant choice is between Web and Native.

Web client (recommended for most organisations)

A Web client issues a client secret in addition to a client ID. The secret is stored server-side on Perplexity and is never exposed to the browser or end user. This makes it the more secure option: even if someone obtains the client ID, they cannot complete the OAuth flow without the secret.

Use a Web client when:

• You are rolling out the connector to a team or organisation and want an additional layer of credential protection.
• Your organisation’s security policy requires confidential client flows.
• You have an admin who can manage secret rotation if needed.

Copy the client secret at creation time. Qlik will not show it again. For a Web client, you will paste it into Perplexity during connector configuration.

Native client (lightweight public client)

A Native client does not use a client secret. It relies on the OAuth PKCE flow, which protects against code interception without requiring a shared secret. This is a valid and commonly used pattern for public clients.

Use a Native client when:

• You want the simplest possible setup with no secret to manage or rotate.
• Your organisation permits public client flows for internal tooling.

At a glance

Both client types work with Perplexity’s custom remote connector flow.

Step 1: Prepare the OAuth client in Qlik Cloud

The tenant administrator creates the OAuth client:

5. In the Qlik Cloud Administration activity center, go to OAuth and click Create new.
6. Select Web or Native as determined above.
7. Add the required scopes: user_default and mcp:execute.
   Optionally add offline_access to reduce re-authentication frequency to once every 30 days from the default 6-hour expiry.
8. For the redirect URL, enter Perplexity’s OAuth callback:
   
   
   • https://www.perplexity.ai/rest/connections/oauth_callback
   • For organisations on the Perplexity Enterprise subdomain, use https://enterprise.perplexity.ai/rest/connections/oauth_callback instead.
     
     See Adding Custom Remote Connectors for more details.
9. If using a Web client, copy the client secret immediately. Qlik will not show it again.
10. Note down the Client ID.

See Deploying Qlik MCP server for a tenant for details. 

Step 2: Add the connector in Perplexity

1. Go to Account settings > Connectors and click + Custom connector, then select Remote.
2. Fill in the required fields:
   • Name: Qlik Cloud (or your tenant name).
   • MCP Server URL: https://<your-hostname>.<your-region>.qlikcloud.com/api/ai/mcp
   • Authentication: OAuth 2.0. Enter the Client ID from step 1. For a Web client, also enter the Client Secret. For a Native client, leave the secret field blank.
   • Transport: Streamable HTTP.
3. Acknowledge the data-sharing warning and click Add.
4. Navigate back to the connector listing and find the new connector.
5. Click Add Connector on the connector card to start the Qlik OAuth flow, sign in to your Qlik Cloud tenant, and click Approve.

By clicking Approve, you are authorising the Qlik server to share your Qlik Cloud data with Perplexity, a third-party system not managed by Qlik. Check your organisation's AI data-sharing policies before proceeding.

If the Qlik MCP server supports OAuth discovery (via /.well-known/oauth-authorization-server), Perplexity can detect endpoints and scopes automatically, and you may not need to enter them manually.

Step 3: Enable the connector and test it

Toggle the connector on under Sources in a Perplexity thread. You can also type the connector name, and it’ll suggest adding it to the thread.

Try these example prompts to confirm the connection is working:

• “What apps are available in my Qlik Cloud tenant?”
• “Summarise the key metrics from [your data product name].”
• “What does [KPI name] look like this month compared to last?”

Organisation members can add custom remote connectors if admins have enabled them. Only admins can share a connector with the entire organisation, done from the Permissions screen in Enterprise settings.

A Qlik Talend Cloud data task using an SAP ODP source endpoint may fail when connecting to an SAP system where the June 9th SAP Security Patch has been applied.

The task fails during dataset unload with the following error:

Failed to unload dataset with errors:
Return type: E, Return row: 0, ID: RSAR, number: 051, Message: Unpermitted Caller; Call rejected See SAP Note 3635619
; Failed during unload

Resolution

According to SAP Note 3731818, SAP provides a temporary option to allow existing ODP-RFC integrations to continue operating on SAP systems where the security patch from SAP Note 3635619 has been applied.

The SAP program RODPS_REPL_SECUREACCESS_OPTOUT, delivered as part of the SAP security update, can be executed on the SAP system to opt out of the newly introduced ODP-RFC security restrictions.

To enable the temporary compatibility mode:

1. Execute the SAP program:
   
   RODPS_REPL_SECUREACCESS_OPTOUT
   
   
2. Select the Opt-Out of Secure Access to ODP API checkbox.
   
   
   
   
3. Apply the change to disable the new ODP-RFC caller restrictions.

After completing this step, Qlik Talend Cloud SAP ODP data tasks should be able to resume replication without encountering:

ID: RSAR
Number: 051
Message: Unpermitted caller

This opt-out mechanism is a temporary SAP-provided compatibility option. SAP has indicated that this program will be disabled through a future SAP Note planned for release toward the end of 2026 (exact date to be decided). Customers should plan migration to a supported long-term integration approach before the opt-out option is removed.

Cause

After applying the SAP June 9th Security Patch, Qlik Talend Cloud data tasks using the SAP ODP source endpoint may fail because of additional security validation introduced by SAP for incoming ODP-RFC calls.

The security change restricts ODP extraction calls from non-SAP applications, causing Qlik Talend Cloud pipelines using the SAP ODP endpoint to stop replicating and return the following error:

Return type: E; Return row: 0 ID: RSAR Number: 051
Message: Unpermitted caller

SAP provides a temporary compatibility option to allow unrestricted ODP-RFC calls; however, this option is time-limited and is planned to expire in December 2026. SAP explicitly states that enabling this workaround is at the customer's own risk.

Customers should plan migration to the supported alternative integration approach before the temporary option is removed.

Environment

• Qlik Talend Cloud

In this article, we walk you through the requirements and process of how to upgrade and unbundle an existing Qlik Sense Repository Database (see supported scenarios) as well as how to install a brand new Repository based on PostgreSQL. We will use the Qlik PostgreSQL Installer (QPI).

For a manual method, see How to manually upgrade the bundled Qlik Sense PostgreSQL version to 12.5 version.

Using the Qlik Postgres Installer not only upgrades PostgreSQL; it also unbundles PostgreSQL from your Qlik Sense Enterprise on Windows install. This allows for direct control of your PostgreSQL instance and facilitates maintenance without a dependency on Qlik Sense. Further Database upgrades can then be performed independently and in accordance with your corporate security policy when needed, as long as you remain within the supported PostgreSQL versions. See How To Upgrade Standalone PostgreSQL.

Index

• Supported Scenarios
• Upgrades
• New installs
• Requirements
• Known limitations
• Installing anew Qlik Sense Repository Database using PostgreSQL
• Qlik PostgreSQL Installer - Download Link
• Upgrading an existing Qlik Sense Repository Database
• The Upgrade
• Next Steps and Compatibility with PostgreSQL installers
• How do I upgrade PostgreSQL from here on?
• Troubleshooting and FAQ
• Related Content

Video Walkthrough

Video chapters:

• 01:02 - Intro to PostgreSQL Repository
• 02:51 – Prerequisites
• 03:24 - What is the QPI tool?
• 05:09 - Using the QPI tool
• 09:27 - Removing the old Database Service
• 11:27 - Upgrading a stand-alone to the latest release
• 13:39 - How to roll-back to the previous version
• 14:46 - Troubleshooting upgrading a patched version
• 18:25 - Troubleshooting upgrade security error
• 21:15 - Additional config file settings

Supported Scenarios

Upgrades

The following versions have been tested and verified to work with QPI: 

Qlik Sense February 2022 to Qlik Sense November 2024.

If you are on a Qlik Sense version prior to these, upgrade to at least February 2022 before you begin.  

Qlik Sense November 2022 and later do not support 9.6, and a warning will be displayed during the upgrade. From Qlik Sense August 2023 a upgrade with a 9.6 database is blocked.

New installs

The Qlik PostgreSQL Installer supports installing a new standalone PostgreSQL database with the configurations required for connecting to a Qlik Sense server. This allows setting up a new environment or migrating an existing database to a separate host.

Requirements

• Review the QPI Release Notes before you continue

• Using the Qlik PostgreSQL Installer on a patched Qlik Sense version can lead to unexpected results. If you have a patch installed, either:

  • Uninstall all patches before using QPI (see Installing and Uninstalling Qlik Sense Patches) or
  • Upgrade to an IR release of Qlik Sense which supports QPI

• The PostgreSQL Installer can only upgrade bundled PostgreSQL database listening on the default port 4432.
• The user who runs the installer must be an administrator.
• The backup destination must have sufficient free disk space to dump the existing database  
• The backup destination must not be a network path or virtual storage folder. It is recommended the backup is stored on the main drive. 
• There will be downtime during this operation, please plan accordingly
• If upgrading to PostgreSQL 14 and later, the Windows OS must be at least Server 2016

Known limitations

• (Limitation removed in QPI 2.1 | Release Notes) Cannot migrate a 14.17 embedded database to a standalone
• (Limitation removed in QPI 2.1 | Release Notes) Using QPI to upgrade a standalone database or a database previously unbundled with QPI is not supported.
• The installer itself does not provide an automatic rollback feature.

Installing a new Qlik Sense Repository Database using PostgreSQL

1. Run the Qlik PostgreSQL Installer as an administrator 
   
   
2. Click on Install 
   
   
3. Accept the Qlik Customer Agreement 
   
   
4. Set your Local database settings and click Next. You will use these details to connect other nodes to the same cluster. 
   
   
5. Set your Database superuser password and click Next
   
   
6. Set the database installation folder, default: C:\Program Files\PostgreSQL\14

   Do not use the standard Qlik Sense folders, such as C:\Program Files\Qlik\Sense\Repository\PostgreSQL\ and C:\Programdata\Qlik\Sense\Repository\PostgreSQL\.

7. Set the database data folder, default: C:\Program Files\PostgreSQL\14\data

   Do not  use the standard Qlik Sense folders, such as C:\Program Files\Qlik\Sense\Repository\PostgreSQL\ and C:\Programdata\Qlik\Sense\Repository\PostgreSQL\.

8. Review your settings and click Install, then click Finish
   
   
9. Start installing Qlik Sense Enterprise Client Managed. Choose Join Cluster option.
   
   The Qlik PostgreSQL Installer has already seeded the databases for you and has created the users and permissions. No further configuration is needed.
   
   
10. The tool will display information on the actions being performed. Once installation is finished, you can close the installer.  
    
    If you are migrating your existing databases to a new host, please remember to reconfigure your nodes to connect to the correct host. How to configure Qlik Sense to use a dedicated PostgreSQL database 
    

Qlik PostgreSQL Installer - Download Link

Download the installer here.

Qlik PostgreSQL installer Release Notes

Upgrading an existing Qlik Sense Repository Database

The following versions have been tested and verified to work with QPI (1.4.0): 

February 2022 to November 2023.

If you are on any version prior to these, upgrade to at least February 2022 before you begin.  

Qlik Sense November 2022 and later do not support 9.6, and a warning will be displayed during the upgrade.  From Qlik Sense August 2023 a 9.6 update is blocked.

The Upgrade

1. Stop all services on rim nodes 
   
   
2. On your Central Node, stop all services except the Qlik Sense Repository Database 
   
   
   
   
3. Run the Qlik PostgreSQL Installer. An existing Database will be detected. 
   
   
   
   
4. Highlight the database and click Upgrade 
   
5. Read and confirm the (a) Installer Instructions as well as the Qlik Customer Agreement, then click (b) Next.
   
   
   
   
6. Provide your existing Database superuser password and click Next.
   
   
7. Define your Database backup path and click Next.
   
   
   
   
8. Define your Install Location (default is prefilled) and click Next.
   
   
   
   
9. Define your database data path (default is prefilled) and click Next.
   
   
    
10. Review all properties and click Upgrade.
    
    The review screen lists the settings which will be migrated. No manual changes are required post-upgrade.
    
    
    
    
11. The upgrade is completed. Click Close.
     
12. Open the Windows Services Console and locate the Qlik Sense Enterprise on Windows services.
    
    You will find that the Qlik Sense Repository Database service has been set to manual. Do not change the startup method. 
    
    
    
    You will also find a new postgresql-x64-14 service. Do not rename this service. 
    
    
    

     

13. Start all services except the Qlik Sense Repository Database service. 
    
    
14. Start all services on your rim nodes.
    
    
15. Validate that all services and nodes are operating as expected. The original database folder in C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\X.X_deprecated
    

     

16. Uninstall the old Qlik Sense Repository Database service.

    This step is required. Failing to remove the old service will lead the upgrade or patching issues.

    1. Open a Windows File Explorer and browse to C:\ProgramData\Package Cache
       
       
    2. From there, search for the appropriate msi file.
       
       
       
       If you were running 9.6 before the upgrade, search PostgreSQL.msi
       If you were running 12.5 before the upgrade, search PostgreSQL125.msi
       
       
    3. The msi will be revealed.
       
       
    4. Right-click the msi file and select uninstall from the menu.
       
       
       
       
    
    
17. Re-install the PostgreSQL binaries. This step is optional if Qlik Sense is immediately upgraded following the use of QPI. The Sense upgrade will install the correct binaries automatically. 
    

    Failing to reinstall the binaries will lead to errors when executing any number of service configuration scripts. 

    If you do not immediately upgrade:
    
    
    1. Open a Windows File Explorer and browse to C:\ProgramData\Package Cache
       
       
    2. From there, search for the .msi file appropriate for your currently installed Qlik Sense version
       
       
       
       For Qlik Sense August 2023 and later: PostgreSQL14.msi
       Qlik Sense February 2022 to May 2023: PostgreSQL125.msi
       
       
    3. Right-click the file
    4. Click Open file location
       
       
       
       
    5. Highlight the file path, right-click on the path, and click Copy
       
       
       
       
    6. Open a Windows Command prompt as administrator
       
       
    7. Navigate to the location of the folder you copied
       
       Example command line: 
       
       cd C:\ProgramData\Package Cache\{GUID}
       
       Where GUID is the value of the folder name.
       
       
    8. Run the following command depending on the version you have installed: 
       
       Qlik Sense August 2023 and later
       
       msiexec.exe /qb /i "PostgreSQL14.msi" SKIPINSTALLDBSERVICE="1" INSTALLDIR="C:\Program Files\Qlik\Sense"
       
       Qlik Sense February 2022 to May 2023
       
       msiexec.exe /qb /i "PostgreSQL125.msi" SKIPINSTALLDBSERVICE="1" INSTALLDIR="C:\Program Files\Qlik\Sense"
       
       This will re-install the binaries without installing a database. If you installed with a custom directory adjust the INSTALLDIR parameter accordingly. E.g. you installed in D:\Qlik\Sense then the parameter would be INSTALLDIR="D:\Qlik\Sense".
       
       
18. Finalize the process by updating the references to the PostgreSQL binaries paths in the SetupDatabase.ps1 and Configure-Service.ps1 files. For detailed steps, see Cannot change the qliksenserepository password for microservices of the service dispatcher: The system cannot find the file specified.

If the upgrade was unsuccessful and you are missing data in the Qlik Management Console or elsewhere, contact Qlik Support.  

Next Steps and Compatibility with PostgreSQL installers

Now that your PostgreSQL instance is no longer connected to the Qlik Sense Enterprise on Windows services, all future updates of PostgreSQL are performed independently of Qlik Sense. This allows you to act in accordance with your corporate security policy when needed, as long as you remain within the supported PostgreSQL versions.

Your PostgreSQL database is fully compatible with the official PostgreSQL installers from https://www.enterprisedb.com/downloads/postgres-postgresql-downloads. 

How do I upgrade PostgreSQL from here on?

See How To Upgrade Standalone PostgreSQL, which documents the upgrade procedure for either a minor version upgrade (example: 14.5 to 14.8) or a major version upgrade (example: 12 to 14). Further information on PostgreSQL upgrades or updates can be obtained from Postgre directly.

Troubleshooting and FAQ

1. If the installation crashes, the server reboots unexpectedly during this process, or there is a power outage, the new database may not be in a serviceable state. Installation/upgrade logs are available in the location of your temporary files, for example:
   
   C:\Users\Username\AppData\Local\Temp\2
   
   A backup of the original database contents is available in your chosen location, or by default in:
   
   C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\backup\X.X
   
   The original database data folder has been renamed to:
   
   C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\X.X_deprecated
   
   
2. Upgrading Qlik Sense after upgrading PostgreSQL with the QPI tool fails with:
   
   This version of Qlik Sense requires a 'SenseServices' database for multi cloud capabilities. Ensure that you have created a 'SenseService' database in your cluster before upgrading. For more information see Installing and configuring PostgreSQL.
   
   See Qlik Sense Upgrade fails with: This version of Qlik Sense requires a _ database for _.
   
   To resolve this, start the postgresql-x64-XX service.

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support. The video in this article was recorded in a earlier version of QPI, some screens might differ a little bit.

Related Content

Qlik PostgreSQL installer version 1.3.0 Release Notes  
Techspert Talks - Upgrading PostgreSQL Repository Troubleshooting
Backup and Restore Qlik Sense Enterprise documentation
Migrating Like a Boss
Optimizing Performance for Qlik Sense Enterprise
Qlik Sense Enterprise on Windows: How To Upgrade Standalone PostgreSQL
How-to reset forgotten PostgreSQL password in Qlik Sense
How to configure Qlik Sense to use a dedicated PostgreSQL database
Troubleshooting Qlik Sense Upgrades 

According to the Qlik Cloud Platform document, Qlik leverages our cloud providers for backups to maintain copies of content for 30 days.

Can I restore one of those backups?

No, those backups cannot be restored. They are kept for disaster recovery purposes (see Disaster recovery/backup and recovery) and encompass entire regions. 

It's therefore not possible to recover a tenant's previous stage.

It's the tenant admin's responsibility to make sure that copies of the content are regularly backed up on any platform of choice for easy restoration. See Qlik Cloud Administration: Backup Responsibilities for details. 

Environment

• Qlik Cloud Analytics

About Qlik's proactive breaking change notification programme

Qlik's proactive change notification programme exists for breaking product changes where we cannot be confident that our usual in-product and Community notification channels will reach the intended audience.

It is not used for routine deprecations or planned changes; those continue to be communicated through our standard channels. If you have received an email directing you to this article, it is because our records show your tenant may be affected by one of these exceptional changes, and action is required on your part.

Who receives these notifications?

Notifications go to the registered Service Account Owner (SAO) for the affected tenant, the person who can log in to the Qlik Cloud console and My Qlik to list and create tenants and view subscription details. You are likely the SAO if you created the tenant originally, or if it appears listed against your account when you log in to the Cloud console.

We can currently only send to this one address per subscription; we cannot add further recipients.

How we make sure the notification reaches you

Before sending, we check that the SAO has a registered Qlik account (they have registered on Community or logged in to My Qlik) and that their email is not known to be dead. If either check fails, the tenant is skipped and no further action is taken.

If the wrong person was notified

If you believe the wrong person is receiving these notifications, please follow the change SAO process to update our records. Note that this also changes who can log in to manage the tenant and view subscription details, since it is a single linked role rather than a distribution list.

Looking ahead

• A Service Account Owner (SAO) is the only user who has admin rights to manage Qlik Cloud subscriptions on the My Qlik portal (e.g. subscribe, renew, upgrade/downgrade number of users, access to personal information, and subscription details, payment details and invoices), and to recover their tenants in case users lose access.

Relevant resources:

How to Access My Qlik Portal
Managing Your Subscription in My Qlik

Who is the default Service Account Owner?

• For subscriptions purchased through Qlik Sales or via a Qlik Partner:
  The default Service Account Owner is the Sold To contact email address on the quote linked to your purchased order. If you don’t know who the Sold To is, please reach out to your dedicated Qlik Sales Representative or Qlik Partner.
   
• For subscriptions purchased directly from My Qlik portal:
  The default Service Account Owner is the email address linked to the Qlik Account you have used to purchase your subscription online on my Qlik Portal. If you can’t remember the email address linked to your Qlik Account, see How to create a case to contact Qlik Support.

Is the Service Account Owner also the Tenant Admin?

• The Service Account Owner is the Tenant Admin by default, unless:
  • If the Tenant Admin was already changed in the past to someone else (see: Managing tenant admins).
  • If the tenant was created programmatically, rather than via My Qlik, it will not have an initial interactive Tenant Admin deployed. In this case, use the APIs to add a tenant admin using the regional OAuth client credentials you used to create that tenant.

Can I change the Service Account Owner?

• Yes, you can change the Service Account Owner(SAO) associated with your purchased subscription.

How to change the Service Account Owner (SAO)?

• The change is a manual process and requires you to contact Qlik Support (see How to contact Qlik Support). When raising such a request, please make sure to provide the below information:
  
  
  • Reason for change
  • Old email/New email
  • Subscription ID/License key
  • Tenant URL

Please do the following before requesting the change:

• Advise NEW SAO to register for a Qlik account
• Advise NEW SAO to log in at least once to  myqlik.qlik.com/portal
• Advise OLD SAO to transfer the Tenant admin rights to NEW SAO

When changing the Service Account Owner, does the Tenant Admin automatically change?

• No, the Tenant Admin will not change. If a change of Tenant Admin is needed, the current Tenant Admin will need to invite the new Tenant Admin and give him/her Tenant Admin Role in the Management Console. It is always recommended but not a requirement to assign two Tenant Admins per subscription. If one Tenant Admin leaves the company, the other one will still be able to administrate the tenant. If there is only one Tenant Admin who has left the company, please contact Qlik Support for further assistance (see How to contact Qlik Support)
  
  Additional Note:
  
  If the old Tenant Admin stored apps in his/her personal space, it is important for the new Tenant Admin to do either (a) or (b):
  1. Update who is the apps’ owner (See Changing app owners Changing app owners)
  2. Publish and share apps on a shared space (See Working in shared spaces)

Areas that are particularly sensitive when you remove a user:

• All private content on published apps will be lost. There is no API method to transfer ownership
• The connections created by the OLD SAO will be deleted and this will have to be recreated.
  • All data connections with credentials. These will all need to have their credentials updated once the data connection ownership is transferred

How to change the Tenant Admin?

Does the Tenant Admin need to consume a Professional or Analyzer user?

Capability

While there is a lot of hype around #AI in the world, there is no denying it's power ... for the RIGHT USE CASES.

Imagine the ability to ask Natural Language questions of the data you have in ServiceNow without needing to pre-load the data in Qlik. Pretty cool in any situation. But downright required in situations where there are reasons for the data to not egress out of ServiceNow. 

ServiceNow provides something called AI Agents, that are very similar to Qlik Answers, in that users are able to simply ask natural language questions about their data. You gotta LIKE that.

Also like Qlik Answers, ServiceNow AI Agents are able to be called via a well documented REST API. Which means you can consume those endpoints from within Qlik. You gotta LOVE that. 

Scenario

That capability provides tremendous value for our joint customers for so many scenarios. The one I will focus on in this article is regarding a Customer Success Manager working in a Qlik.

The Qlik application they utilize has lots and lots of data that they can do analytics with using traditional dashboarding and visualization. Of course they simply open Qlik Answers to ask questions of any data that is already loaded in the application. Assume for this scenario that the CSM is focusing on customer renewals for whatever product they might be selling. 

They come across an account that is due for renewals soon, they can see that Qlik Predict has predicted that the account is likely to churn, and has ranked their health very low. They can see the NPS scores for the account have dropped significantly. Oh boy, they need to turn that frown, upside down. 

Before they call the customer, they would also like to know if they have any outstanding trouble incidents/problems. 

Not hard to imagine this use case. Having access to that information provides vital insights that the CSM needs to know how to effectively communicate with the customer when they call. How they get access also matters. They could always stop their day job, working in Qlik, and go login to ServiceNow, become a master in filtering and find the incidents that are open for this specific customer. But with the handy dandy Qlik Sense extension called ServiceNow Agent Dream shared in this post they don't have to. They simply ask "Do they have any open incidents?" 

Scenario Demonstration

I've created a simple Next - Next - Finish type demonstration that allows you to see this scenario in action. You simply start the tour, and press Next when you are ready to advance through it. 

Walk through the CSM Demonstration

ServiceNow AI Agent Dream Setup

If your goal was simply understand the capability and the scenario so you know "what's possible" then you can stop reading. But if your goal is to actually try and get this dream capability up and running in your environment then please continue. The next link is a very similar demo where you simply press Next to advance through, that walks you through how to create the same ServiceNow AI Agent that I used in my scenario. 

Walk through creating a ServiceNow AI Agent

Now that you at least understand the capability it's time to dive into the 3 attachments for this post:

1. Incident_Intelligence_Agent_Guide.docx - This document will walk you through how to build the ServiceNow AI agent since you will need 1 in your environment to call. Please refer to ServiceNow help on the topic or your BFF Claude/ChatGPT for help should anything in your environment differ from mine. 

2. ServiceNowAgentDream_Setup_Guide.docx - This document will walk you through how to install the ServiceNow Agent Dream extension and then how to configure it. OAuth authentication is required for ServiceNow AI Agents, so I walk you through how to do that as well. 

3. ServiceNowAgentDream.zip - This is the Qlik Sense extension that you need to download and install in your Qlik Sense environment/tenant. 

This document is a general guide and is provided as is. Modifications to the process may be necessary depending on your individual database setup.

If you have installed a standalone PostgreSQL database, or if you have used the Qlik PostgreSQL Installer (QPI) to upgrade and decouple your previously bundled database, then you can upgrade PostgreSQL at any time. This means you control maintenance and can immediately react to potential PostgreSQL security concerns by upgrading to a later service release or a later major version.

Content

• Requirements:
• Preparation
• Upgrading to a later service release
• Upgrading to a new major PostgreSQL release

Requirements:

• Only upgrade to a supported version of PostgreSQL. See the Qlik Sense Enterprise on Windows System Requirements for details. 
• This guide covers deployments where PostgreSQL has been installed separately or previously unbundled using the Qlik PostgreSQL installer. 

This document covers the following scenario:

• Windows Server OS. The use of Linux, in managed cloud deployments or on-prem, is not covered. 
• Generic PostgreSQL deployment. Stream replication, SSL, or any other advanced configuration are not covered.

Preparation

Run a complete backup of Qlik Sense Enterprise on Windows site as described in Backup and restore Qlik Sense Enterprise on Windows.

• Qlik Sense Repository Database (from PostgreSQL database server)
• Qlik Sense share folder
• Qlik Sense CA-signed certificates

Upgrading to a later service release

These steps apply if you are upgrading within a major PostgreSQL release (example: 14.5 to 14.8). 

1. Download the PostgreSQL installer from them PostgreSQL site
2. Stop the Qlik Sense Enterprise on Windows services. Leave your standalone PostgreSQL database running.
3. Run the PostgreSQL installer and follow the instructions.
4. Start the Qlik Sense Enterprise on Windows services.

No further steps are required.

Upgrading to a new major PostgreSQL release

If you are moving to a higher major version, an in-place upgrade will not be possible. Instead, we will install the the new version in parallel, then then migrate the old database and eventually uninstall the old version. Our example is written using PostgreSQL 12 to 14. 

1. Download the PostgreSQL installer from them PostgreSQL site
   
   
2. Run the installer
   
   During install:
   
   
   • Install the database on the standard 5432 port. 
     
     This allows us to have 12 running on the Qlik Sense default 4432 port and the 14 instance on 5432.
     
     
   • Set the same password as the one currently in use with the version 12 PostgreSQL instance. 
     
     
3. Open a Windows File explorer and create a backup folder, such as C:\backup 
   
   
4. Backup your version 12 database 
   
   This step is crucial. You may have already backed up your site, but in this step we will create the specific backup we will use to migrate your database, using a modified command.
   
   To do so:
   
   
   1. Stop all Qlik Sense Enterprise on Windows services on all nodes. Leave postgresql-x64-12 service (your current repository) running
      
      
   2. Stop postgresql-x64-14 (your newly installed PostgreSQL instance)
      
      
   3. Open a Windows Command Line (CMD) as administrator
      
      
   4. Run:
      SET PGPASSWORD=postgrespassword (replace this with the actual password)
      
      
   5. Run:
      cd “C:\Program Files\PostgreSQL\12\bin”
      
      
   6. Run
      pg_dumpall.exe -h localhost -U postgres -p 4432 -f c:\backup\backup_db.sql
      
      
   7. Follow the onscreen instructions and wait until the backup is finished
      
      Note: If you are prompted to input the password (even if it was previously entered correctly), you will need to modify pg_hba.conf. 
      
      Location: C:\Program Files\PostgreSQL\12\data\pg_hba.conf
      
      Change md5 to trust and restart the postgresql-x64-12 service. See Changing the Database Superuser Password without Qlik Sense Installed for details.
      
      Once the backup has completed, revert back to md5.
      
      
5. Migrate from 12 to 14
   
   We are now moving our Qlik Sense repository from the earlier release of PostgreSQL into the new one.
   
   
   1. Start the postgresql-x64-14 service
      
      
   2. Stop postgresql-x64-12
      
      
   3. Open a Windows Command Line (CMD) as administrator
      
      
   4. Run:
      cd “C:\Program Files\PostgreSQL\14\bin”
      
      
   5. Run
      psql -h localhost -U postgres -p 5432 -f c:\backup\backup_db.sql
      
      
   6. Follow the onscreen instructions.
      
      Note: If you receive the error password authentication failed for user "postgres", (even if it is correct), you will need to modify pg_hba.conf. 
      
      Location: C:\Program Files\PostgreSQL\14\data\pg_hba.conf
      
      Change scram-sha-256 to md5 and restart the postgresql-x64-14 service  and redo step e). See Changing the Database Superuser Password without Qlik Sense Installed for details.
      
      
6. With the import finished, copy the following two files from your old 12 data folder into your new 14 data folder:
   
   
   • pg_hba.conf 
   • postgresql.conf 
     
     
7. Open postgresql.conf and verify that the port is set to 4432 (the standard Qlik Sense port)
   
   
8. (If not done already) stop the postgres-x64-12 service
   
   
9. Restart the postgres-x64-14 service
   
   
10. Start all Qlik Sense services
    
    
11. Once you have confirmed all functionality and tested, uninstall PostgreSQL 12. This can be done directly from the Windows Control Panel and Programs and Features

Related Content:

Upgrading and unbundling the Qlik Sense Repository Database using the Qlik PostgreSQL Installer 
How to manually upgrade the bundled Qlik Sense PostgreSQL version to 12.5 version 
Changing the Database Superuser Password without Qlik Sense Installed 

This template was updated on December 4th, 2025 to replace the original installer and API key rotator with a new, unified deployer automation. Please disable or delete any existing installers, and create a new automation, picking the Qlik Cloud monitoring app deployer template from the App installers category.

Installing, upgrading, and managing the Qlik Cloud Monitoring Apps has just gotten a whole lot easier! With a single Qlik Automate template, you can now install and update the apps on a schedule with a set-and-forget installer using an out-of-the-box Qlik Automate template. It can also handle API key rotation required for the data connection, ensuring the data connection is always operational.

Some monitoring apps are designed for specific Qlik Cloud subscription types. Refer to the compatibility matrix within the Qlik Cloud Monitoring Apps repository.

'Qlik Cloud Monitoring Apps deployer' template overview

This automation template is a set-and-forget template for managing the Qlik Cloud Monitoring Applications, including but not limited to the App Analyzer, Entitlement Analyzer, Reload Analyzer, and Access Evaluator applications. Leverage this automation template to quickly and easily install and update these or a subset of these applications with all their dependencies. The applications themselves are community-supported; and, they are provided through Qlik's Open-Source Software (OSS) GitHub and thus are subject to Qlik's open-source guidelines and policies.

For more information, refer to the GitHub repository.

Features

• Can install/upgrade all or select apps.
• Can create or leverage existing spaces.
• Programmatically verified prerequisite settings, roles, and entitlements, notifying the user during the process if changes in configuration are required, and why.
• Installs latest versions of specified applications from Qlik’s OSS GitHub.
• Creates required API key.
• Creates required analytics data connection.
• Creates a daily reload schedule.
• Reload applications post-install.
• Tags apps appropriately to track which are installed and their respective versions.
• Supports both user and capacity-based subscriptions.

Requirements

The user running the automation needs to have:

• API permission; see Permission settings — Features and actions | help.qlik.com.
• The tenant admin role; see Permissions granted by security roles | help.qlik.com.
• The audit admin role (when deploying the Answers Analyzer application); see Permissions granted by security roles | help.qlik.com.

Configuration

Update just the configuration area to define how the automation runs, then test run, and set it on a weekly or monthly schedule as desired.

Configure the run mode of the template using 7 variable blocks

Users should review the following variables:

1. configuredMonitoringApps: contains the list of the monitoring applications which will be installed and maintained. Delete any applications not required before running (default: all apps listed).
2. refreshConnectorCredentials: determines whether the monitoring application REST connection and associated API key will be regenerated every run (default: true).
3. reloadNow: determines whether apps are reloaded immediately following updates (default: true).
4. reloadScheduleHour: determines at which hour of the day the apps reload at for the daily schedule in UTC timezone (default: 06)
5. sharedSpaceName: defines the name of the shared space used to import the apps into prior to publishing. If the space doesn't exist, it'll be created. If the space exists, the user will be added to it with the required permissions (default: Monitoring - staging).
6. managedSpaceName: defines the name of the managed space the apps are published into for consumption/ alerts/ subscription use.If the space doesn't exist, it'll be created. If the space exists, the user will be added to it with the required permissions (default: Monitoring).
7. versionsToKeep: determines how many versions of each staged app is kept in the shared space. If set to 0, apps are deleted after publishing. If a positive integer value other than 0, that many apps will be kept for each monitoring app deployed (default: 0).

App management:

If the monitoring applications have been installed manually (i.e., not through this automation), then they will not be detected as existing. The automation will install new copies side-by-side. Any subsequent executions of the automation will detect the newly installed monitoring applications and check their versions, etc. This is due to the fact that the applications are tagged with "QCMA - {appName}" and "QCMA - {version}" during the installation process through the automation. Manually installed applications will not have these tags and therefore will not be detected.

FAQ

Q: Can I re-run the installer to check if any of the monitoring applications are able to be upgraded to a later version?

A: Yes. The automation will update any managed apps that don't match the repository's manifest version.

Q: What if multiple people install monitoring applications in different spaces?

A: The template scopes the application's installation process to a managed space. It will scope the API key name to `QCMA – {spaceId}` of that managed space. This allows the template to install/update the monitoring applications across spaces and across users. If one user installs an application to “Space A” and then another user installs a different monitoring application to “Space A”, the template will see that a data connection and associated API key (in this case from another user) exists for that space already. It will install the application leveraging those pre-existing assets.

Q: What if a new monitoring application is released? Will the template provide the ability to install that application as well?

A: Yes, but an update of the template from the template picker will be required, since the applications are hard coded into the template. The automation will begin to fail with a notification an update is needed once a new version is available.

Q:I have updated my application, but I noticed that it did not preserve the history. Why is that?

A: Each upgrade may generate a new set of QVDs if the data models for the applications have changed due to bug fixes, updates, new features, etc. The history is preserved in the prior versions of the application’s QVDs, so the data is never deleted and can be loaded into the older version. 

Loop and Reduce will remove an app's section access that was defined through the load script. Offline usage needs to be enabled in your tenant's management console in order to use the Loop And Reduce block on an app outside a personal space. More information on offline usage.

See How to Loop and Reduce with always one selected value fields if your app contains always one selected value fields.

This article explains how a loop and reduce operation can be performed on a Qlik Sense app by using Qlik Application Automation. It covers two examples, in the first one, the reloaded apps will be (re)published to one space. In the second example, each reduced app will be (re)published to a separate space.

This article covers two advanced examples, a more basic example can be found here .

Covered in this article:

• 1. Loop and reduce to one space
• 2. Loop and reduce to multiple spaces

The source app used in this article can be downloaded here.

Attached to this article are 2 files of the exported automations used in this article. More information on importing automations can be found here.

1. Loop and reduce to one space

In this example, all reduced apps will be (re)published to the same space.

Create a new automation and follow these steps to perform a loop and reduce action on a Qlik Cloud app:

1. Go to the Qlik Cloud Services connector and search for the block "Loop And Reduce". Drag this block inside the automation editor.
   
   
2. Specify the id for the app that should be used as a source app. The reduction will be performed on this app. Next, specify the field name over which the loop should run, for each unique value of the specified field name, a reduced app will be created. In this example, CountryName will be used as the reduction value.
   
   
   

    

3. The reduced apps are stored on the Temporary File services. The Loop And Reduce block will return a list of file ids together with the unique value of the reduction field and a list of sheet ids for the sheets that were public on the source app.
   
   
4. The next step is to import the apps from the Temporary File services. To do this search for the block "Import App From Export Id" and drag this block in the loop that's created by the Loop And Reduce block. This block will import one app from the temporary file services into your personal space.
   
   Tip: Specify the reduced value that will be returned by the Loop and Reduce block in the Name parameter of the Import block.
   
   See (Import App From Export) for an example:
   
   

   

5. When an app is imported, all sheets will be made private, this is the default behavior of the import app block. The next step is to publish the sheets that were public in the source app.
   
   
6. Because each reduced app will have a list of sheets that are public, a Loop block is necessary to loop over the list. Search for a "Loop" block in the block menu or find it under Basic and connect it right below the "Import App From Export Id" block. Specify the "Public Sheets" list returned by the Loop And Reduce block as the value for the "Loop over items of list" input parameter of the Loop block.
   
   

   

7. Now, to publish each sheet of the imported app, search for the block Publish Sheet in the Qlik Cloud Services connector and drag that block in the loop generated by the Loop block. In this block, specify the id returned by the Import App block as App Id and use the current item in the loop as Sheet Id.
   
   

   

8. The next step is to publish or republish the imported app to a managed space. This can be done with the Publish App To Managed Space block. Search for this block in the Qlik Cloud Services connector and connect it below the loop block. Set the Run Mode to "(Re)publish by name", if the managed space already contains an app with the same name as the imported app, the imported app will be republished, or else it will be published.
   
   
9. In the configuration of the Publish App To Managed Space block, set the App Id equal to the id returned by the Import App From Export Id block. For the Space Id, perform a lookup or manually enter an id, make sure you're specifying a managed space. The Data parameter should be set to "source".
   
   

   

10. Finally, when your app is published to a managed space, the imported app will still exist in your personal space. To remove this app, search for the block "Delete App" in the Qlik Cloud Services connector and connect it to the Publish App To Managed Space block. Specify the id returned by Import App From Export Id as the App Id in the block's settings.
    
    

An example of a completed automation:

Attached example file: loop_and_reduce_to_same_space.json

2. Loop and reduce to multiple spaces

In this example, each reduced app will be published to a different space. We'll use the Insurance Claims app and the automation for the first example again. Since this app reduces on the field CountryName, we'll start by creating a managed space for each unique value that's found for CountryName. 

Next is to create a mapping for each unique reduction value and the corresponding space's id. There are multiple ways to achieve this. In this example, this mapping is stored in a JSON list of objects with the keys reduction_value and space_id. Feel free to use an automation to create the managed spaces and build this list.

Example:

[
	{
		"reduction_value": "Scotland",
		"space_id": "6138a3062c1054d8158c189a"
	},
	{
		"reduction_value": "Northern Ireland",
		"space_id": "6138a318faed485d36ae911f"
	},
	{
		"reduction_value": "England",
		"space_id": "6138a337faed485d36ae9126"
	},
	{
		"reduction_value": "Wales",
		"space_id": "6138a33f98b0d0bf7e719dfb"
	},
	{
		"reduction_value": "Guernsey",
		"space_id": "6138a349faed485d36ae912b"
	},
	{
		"reduction_value": "Isle of Man",
		"space_id": "6138a35aba392246d331e611"
	},
	{
		"reduction_value": "Jersey",
		"space_id": "6138a3653ec592fe53a8d55b"
	}
]

The next step is to store the mapping in the automation. Execute the following steps to do this:

1. Search for the Variable block and add this to the automation.
   
   
2. Go to the block's settings, click Manage variables and add a new variable of type list.
   
   
3. Go to the operations section of the variable and set the first operation to empty the variable.
   
   
4. Add a second operation Merge other list into... and click the List input field of that operation, in the dropdown that appears, select Add Formula.
   
   
5. From the formula picker, search for the formula Object and select it. Copy the JSON mapping to the json input field of the Object formula and click Save.
   
   
6. Add the block to the beginning of the automation from the first part of this article:
   
   

   

7. The next step is to find the right space id for each reduced app. To do that, add the block Lookup Item In List in the automation right before the block Publish App To Managed Space.
   
   
8. Go to the settings of the Lookup Item In List block and specify the variable that contains space_id/reduction_value mapping as input list. The condition inside the lookup should compare the mapping's reduction_value to the Reduced Value of the current item in the loop of Loop And Reduce. See the below image for an example:
   
   

   

9. Finally, specify the space_id from the output of the lookup block as Space Id in the settings of the Publish App To Managed Space.
   
   
   

    

Attached example file: loop_and_reduce_to_mulitple_spaces.json

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.