Long access times to Qlik Cloud or when performing reloads using the Direct Access Gateway may be caused by high network latency between your location and the AWS datacenter hosting the affected tenant. 

A possible browser test to check the network connection from a computer to AWS can be found at AWS Latency Test.

This test does not concern Qlik Cloud's platform, and can therefore be used to determine if there are purely network-related issues.

1. Find the correct AWS region for your tenant. You can do so by cross-referencing regions and IP addresses as documented in Allowlisting domains and IP addresses.
   
   For instance, the region for .de tenants is in Frankfurt:
   
   
   
   
2. On the AWS Latency Test, select your region and a couple of other ones to compare results
   
   
   
   
3. Wait for the test results to be returned:
   
   
   
   
4. In case of immediate apparent problems, involve your network team to discuss possible remediations

This is just a first-step tool, not a conclusive one. A latency of 300ms or more might still not affect user experience in Qlik Cloud, but it's still worth using the tool quickly for a first assessment.

Related Content

How to verify and measure transfer speed from Direct Access gateway to Qlik Cloud

Environment

• Qlik Cloud Analytics

In a setup with a local and remote Qlik Replicate server, the remote server's IP address has changed. Does this IP address change require any additional configuration steps?

Resolution

To avoid any issues after an IP address change:

1. Stop all file channel replication tasks on the local Qlik Replicate server
2. Stop all file channel replication tasks on the remote Qlik Replicate server
3. Update the remote Qlik Replicate server IP address in all local file channel tasks
4. Resume the file channel tasks on the remote Qlik Replicate server
5. Verify the connection to the remote Qlik Replicate server
6. Resume all file channel tasks on the local Qlik Replicate server.

Environment

• Qlik Replicate

Is it possible to limit the available output formats for an OnDemand report, such as only allowing PDF rather than allowing multiple formats?

Answer

Qlik NPrinting On-Demand Reports cannot be limited to a certain format (such as PDF). The Qlik Sense On-Demand reporting object will continue to present all available formats to export On-Demand reports to. This is by design.

Environment

• Qlik NPrinting

In some cases, the otherwise correctly enabled Qlik NPrinting audit feature fails to produce output. For information on how to correctly enable auditing, see Audit trail.

Resolution

On the Qlik NPrinting Server:

Always export and backup your client_audit certificate before proceeding.

1. Open the Services MMC from the Windows server control panel
2. Stop the Qlik NPrinting auditing service
3. Open the Windows Certificate Manager > Certificates > Local Computer > Personal certificate folder
   
   
    
4. Delete the client_audit certificate from the cert store shown in the image above
5. Start the Qlik NPrinting Audit service

This will result in the creation of a new certificate and enable the audit service to work normally once again.

Cause

The client_audit certificate that secures the Qlik NPrinting auditing service has become corrupted or contains an invalid signature.

Environment

• Qlik NPrinting

The Qlik Analytics Migration Tool provides a structured and repeatable process for migrating analytics assets to Qlik Cloud. It enables teams to define migration plans, validate each step, and coordinate across roles to ensure secure and accurate execution.

Content

• Core Capabilities
• What Makes the Tool Different
• Why Move to Qlik Cloud
• How to Get Started
• Qlik Analytics Migration Tool (Quick Video Demo)

Core Capabilities

• Migrate Qlik Sense Client-Managed apps, streams, users, groups, data files, data connections, and much more
• Preserve content ownership, access rights, and user-generated content such as apps, private and community sheets, as well as bookmarks through dynamic user mapping
• Automatically rewrite load scripts to reflect updated cloud data connections and paths
• Configure structured plans and jobs to manage projects at scale
• Enable multi-user access to support collaboration and phased execution
• Log, validate, and roll back migration steps as needed
• Partially supports QlikView and Qlik NPrinting migrations to reduce redevelopment

What Makes the Tool Different

• Designed from real-world experience and refined for enterprise use
• Fully branded, hardened, and extended since acquisition
• Supports phased and repeatable execution across migration stages
• Adjusts load scripts and metadata automatically during migration
• Maintains user identity, private content, and access policies

Why Move to Qlik Cloud

Qlik Cloud provides continuous innovation, centralized governance, and integrated AI that is not available in on-premises environments. Customers migrating to Qlik Cloud immediately benefit from:

• Qlik Predict for AI-driven forecasting and predictions built into dashboards
• Qlik Answers for intuitive, natural language search and explanation
• Continuous cloud-native feature delivery with automated upgrades
• Real-time access to governed and streaming data sources
• Simplified DevOps, reduced infrastructure management, and tighter security control

How to Get Started

• Download the Qlik Analytics Migration Tool from Qlik's Download page. 
  
  
  
  
• Review full documentation at Qlik Analytics Migration Tool overview | Help.qlik.com 

Qlik Analytics Migration Tool (Quick Video Demo)

Learn More, Ask Questions, Share Experiences

The Qlik Community is the central place to get answers, exchange ideas, and collaborate with peers using the Qlik Analytics Migration Tool. Whether you're preparing for a full environment shift or running phased pilots, we encourage you to share your approach and learn from others moving to Qlik Cloud in the Move to Cloud forum.

Environment

• Qlik Cloud

Over a period of time, attrep_changes tables will significantly contribute to the overall storage cost as the image of a dropped table will persist on Snowflake Storage for the purpose of Time Travel and Fail-Safe (see Working with Temporary and Transient Tables | docs.snowflake.com for details).

Resolution

Create the attrep_changes table as a transient with a limited-to-absent support for Time Travel and Fail Safe. This needs to be done in Snowflake.

1. Create a transient schema (CREATE SCHEMA | docs.snowflake.com) with:
   
   
   • DATA_RETENTION_TIME_IN_DAYS set to 0
     
     
     
     
   • MAX_DATA_EXTENSION_TIME_IN_DAYS set to 0 (Maximum number of days for which Snowflake can extend the data retention period for tables to prevent streams on the tables from becoming stale)
     
     See MAX_DATA_EXTENSION_TIME_IN_DAYS for more information.
     
     
2. In Qlik Replicate, configure the task so that all of the control tables will be created in the transient schema:
   
   
   

Example:

CREATE OR REPLACE TRANSIENT SCHEMA IF NOT EXISTS TRANSIENT_SCHEMA
        DATA_RETENTION_TIME_IN_DAYS = 0
        MAX_DATA_EXTENSION_TIME_IN_DAYS = 0
        COMMENT = 'Transient Schema for Qlik Replicate Control Tables';

No out-of-the-box solution exists in Qlik Replicate for a configurable option to create the attrep_changes table as a transient one. Log an Idea with Qlik if this is a requirement.

Cause

• attrep_changes tables are defined for each task and are dropped or created for each bulk being applied to the target
• attrep_changes tables are created as normal SF tables, which means that they have a Time Travel and Fail-Safe feature enabled (storing old data images and mirroring data)
• The volume of uncompressed data in each instance of attrep_changes table usually varies between 500 MB and 2 GB
• Usually, customers configure a bulk to be dropped into Snowflake every 10 to 20 minutes.
• If we assume that the data is stored uncompressed, then a worst-case scenario would be:
  • 2GB * 6 drops/hour * 24 hours * 90 days (default data retention in enterprise account) = 25,920GB à 26 billable Terabytes after 90 days.
  • Even with a 60% compression ratio, this still produces 9 TB per table after 90 days.

Environment

• Qlik Replicate

If users are behind a proxy, the Qlik Web Connector may return the following errors:

• 407 proxy authentication errors and
• 503 Service Unavailable

Environment:

Qlik Web Connectors 

Under these circumstances, the user has to configure the proxy from the deploy.config file, which is normally located in the root of your Qlik Web Connectors folder.

Disabling the proxy:

This is the best approach for Error 503 Service Unavailable errors. 

Open the deploy.config file, search for Proxy in order to locate the settings and configure them as below.

<Proxy>
    <UseProxy>false</UseProxy>
    <ProxyAddress></ProxyAddress>
    <ProxyUsername></ProxyUsername>
    <ProxyDomain></ProxyDomain>
    <ProxyPassword></ProxyPassword>
</Proxy>
 

Configuring the proxy - Setting it up to true:

This is the best approach for 407 proxy authentication errors. 

If you are behind a proxy you will just need to set UseProxy to true and you might need to enter the proxy credentials as below.

<Proxy>
    <UseProxy>true</UseProxy>
    <ProxyAddress>proxy.sub-domain.mymaindomain.com:port</ProxyAddress>
    <ProxyUsername>username</ProxyUsername>
    <ProxyDomain></ProxyDomain>
    <ProxyPassword>password</ProxyPassword>
</Proxy>

The Data Load Editor in Qlik Sense Enterprise on Windows 2025 experiences noticeable performance issues.

Resolution

The issue is caused by defect SUPPORT-6006. Qlik is actively working on a fix.

Fix Version

A fix is planned for the next possible patches. Review the Release Notes for SUPPORT-6006.

Workaround

A workaround is available. It is viable as long as the Qlik SAP Connector is not in use.

1. In a Windows file browser, navigate to C:\Program Files\Common Files\Qlik\Custom Data\
2. Move the QvSapConnectorPackage directory to a different location

No service restart is required.

Internal Investigation ID(s) 

SUPPORT-6006

Environment

• Qlik Sense Enterprise on Windows

Qlik Sense and Vulnerability “CVE-2025-7783” in NPM Library form-data

In mid-July 2025, a vulnerability was disclosed in the NPM library form-data (GitHub Security Advisory). Qlik became aware of this issue through its standard Secure Development Lifecycle (SDL) processes.

Following an internal review, Qlik R&D and Security teams identified that potentially vulnerable versions of the form-data library were included in some installations of Qlik Sense Enterprise for Windows. However, due to the specific way Qlik utilizes this library, the conditions required for exploitation are not met.

Although the vulnerability was determined to be non-exploitable within Qlik Sense, customers who prefer to upgrade to a version that includes the patched form-data library can do so by installing one of the following releases:

• May 2025 Patch 6
• November 2024 Patch 18 
• May 2024 Patch 24 

Note: An earlier version of this information was mistakenly published indicating that this CVE was directly related to Qlik Sense for Windows.

This article provides an overview of how to send straight table data to Microsoft Teams as a table using Qlik Automate.

The template is available on the template picker. You can find it by navigating to Add new -> New automation -> Search templates, searching for 'Send straight table data to Microsoft Teams as a table' in the search bar, and clicking the Use template option.

You will find a version of this automation attached to this article: "Send-straight-table-data-to-Microsoft-Teams-as-a-table.json".

Content:

• Full Automation
• Automation structure
• Related Content

Full Automation

Automation structure

The following steps describe how to build the demo automation: 

1. Add the 'Get Straight Table Data' block from the Qlik Cloud Services connector to get data from the straight table for a specific app to send to the Microsoft Teams channel as a table. Specify the app ID, Sheet ID, and Object ID in the input parameters. You can use the do-lookup functionality to find value for all these parameters. There is a limit of 100,000 records that can be retrieved through the 'Get Straight Table Data' block. This block will not work with other table types.
   
   
2. Add a 'Loop' block to loop over the keys from the 'Get Straight Table Data' block response which acts as the table header. Use the '{getkeys: {$.GetStraightTableData}}' formula in the 'Loop' block. Within the 'Loop' block add the following blocks:
   
   
   1. Add an object variable called 'teamsTextBlockObject' to build the header and pass this variable to another list variable called 'cardTableColumn'.
      
      
   2. Add another 'Loop' block to loop over all the values for the current key of the straight table. Within the 'Loop' block add the following blocks:
      
      
      1. Add a 'Condition' block to check whether the column value is empty or not.
         
         
         • If the condition block outcome evaluates to true:
           
           
           • Add the 'teamsTextBlockObject' object variable, set the text value as 'NA' since the column value is null/empty, and pass this variable to the 'cardTableColumn' list variable.
             
             
         • If the condition block outcome evaluates to false:
           
           
           • Add the 'teamsTextBlockObject' object variable, set the text value as the column value of the straight table, and pass this variable to the 'cardTableColumn' list variable.
             
             
   3. Add another object variable called 'columnObject' and pass this variable to the 'columns' list variable. These variables are used to build the straight table data into a specific format which is required to build the structure of the team's message as a card attachment.
      
      
3. Add a string variable called 'title' which is used to provide the title to the message.
   
   
4. Add the 'Create Attachment Adaptive Card' block from the Microsoft Teams connector to build the structure for card attachment. Make sure to transform the 'columns' list to JSON text using the JSON formula.
   
   
   
   
5. Add 'Send Message' block from the Microsoft Teams connector to send straight table data as a table to the Teams channel with the card attachment which was created in the previous block.
   Specify the Team ID and the Channel ID in the input parameters. You can use the do-lookup functionality to find the value of all these parameters. 
   
   
   

An example output of the table sent to the Teams channel:

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

Related Content

• How to get started with Microsoft Teams
• Send straight table data to Microsoft Teams as a message 
• Send straight table data to email as HTML table

Environment

• Qlik Cloud Analytics
• Qlik Automate

Description

• Error "Object reference not set to an instance of an object" when previewing NPrinting Designer Excel Template Editor reports that contain merged cells

Diagnosis:

• After upgrade, open an NPrinting Report in the NP designer and preview a report that his known to contain merged cells
• Preview the Report
• Error encountered "The preview request failed with message: Object reference not set to an instance of an object"

Environment

• Discovered following an upgrade from older unsupported NP versions (NP November 2019) to Current Supported NP versions

Resolution

• Please note that this issue has been resolved and will be available in NPrinting May 2022 SR 4.
• Keep an eye on the Qlik Community Downloads site and Product release notes for new product and service releases.

Workaround:

• None at this time

Cause

• Product Defect ID: OP-95768

Related Content

• Release Notes | Qlik Community
• Downloads | Qlik Community

Installing, upgrading, and managing the Qlik Cloud Monitoring Apps has just gotten a whole lot easier! With two new Qlik Application Automation templates coupled with Qlik Data Alerts, you can now: 

1. Install/update the apps with a fully guided, click-through installer using an out-of-the-box Qlik Application Automation template. 
2. Programmatically rotate the API key required for the data connection on a schedule using an out-of-the-box Qlik Application Automation template. This ensures the data connection is always operational. 
3. Get alerted whenever a new version of a monitoring app is available using Qlik Data Alerts. Repeat Step 1 to complete the update. 

The above allows you to deploy the monitoring apps to your tenant with a hands-off approach. Dive into the individual components below. 

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

Content:

• Part One: 'Qlik Cloud Monitoring Apps Installer' template overview
• Part Two: 'Qlik Cloud Monitoring Apps API Key Rotator' template overview
• Part Three: How to setup a Qlik Alert to know when an app is out of date
• A Qlik Cloud Monitoring Apps Workflow Demo (Video)
• FAQ

Part One: 'Qlik Cloud Monitoring Apps Installer' template overview

This automation template is a fully guided installer/updater for 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 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 handles pre-requisite settings, roles, and entitlements.
• Installs latest versions from Qlik’s OSS GitHub.
• Creates required API key.
• Creates required analytics data connection.
• Can create custom reload schedules.
• Can reload post-install.
• Tags apps appropriately to track which are installed and their respective versions.
• Supports both user and capacity-based subscriptions

Click-through installer:

Flow:

Note that 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.

 

Part Two: 'Qlik Cloud Monitoring Apps API Key Rotator' template overview

This template is intended to be used alongside the Qlik Cloud Monitoring Apps for user-based subscriptions template. This automation provides the ability to keep the API key and associated data connection used for the Qlik Cloud Monitoring Apps up to date on a scheduled basis. Simply input the space Id where the monitoring_apps_REST data connection should reside, and the automation will recreate both the API key and data connection regularly. Ensure that the cadence of the automation’s schedule is less than the expiry of the API key.

Configuration

Enter in the Id of the space where the monitoring_apps_REST data connection should reside.

Ensure that this automation is run off-hours from your scheduled monitoring application reloads so it does not disrupt the reload process.

Part Three: How to setup a Qlik Alert to know when an app is out of date

Each Qlik Cloud Monitoring App has the following two variables:

• vLatestVersion: the latest version of the app released on Qlik’s OSS GitHub.
• vIsLatestVersion: a Boolean of whether the app’s current version is equal to the latest version of the app released on Qlik’s OSS GitHub (1 if true, 0 if false).

With these variables, we can create a new Qlik Data Alert on a per-app basis. For each monitoring app that you want to be notified on if it falls out of date:

1. Right-click on a chart in the app, select Alerts and then Create new alert.
2. Clear out the defaults and provide the alert with a name such as <Monitoring App Name> is Out of Date.
3. Select Add measure and select the fx icon to enter a custom expression. Enter the expression ’$(vLatestVersion)'. Ensure it is wrapped in single quotes, then provide the label for the expression Latest Version.
4. Select Add measure and select the fx icon to enter a custom expression. Enter the expression $(vIsLatestVersion), then provide the label for the expression Is Latest Version.
5. Confirm the Details & data tab resembles the following:
   
   
   
   
6. Navigate to the next tab, Conditions.
7. Set the Measure to Is Latest Version, the Operator to Equal to, and the Value to 0. This way, if the app is not the latest version (0), it will trigger the alert.
8. Confirm that the Conditions tab resembles the following:
   
   
   
   
9. Navigate to the Distribution tab and confirm that the alert is evaluated When data is refreshed.

Here is an example of an alert received for the App Analyzer, showing that at this point in time, the latest version of the application is 5.1.3 and that the app is out of date:

A Qlik Cloud Monitoring Apps Workflow Demo (Video)

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. Run the installer, select which applications should be checked and select the space that they reside in. If any of the selected applications are not installed or are upgradeable, a prompt will appear to continue to install/upgrade for the relevant applications.

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

A: The template scopes the applications install process to a “target” space, i.e., a shared space (if not published) or a managed space. It will scope the API key name to `QCMA – {spaceId}` of that target 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 and 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. The template receives the list of applications dynamically from GitHub. If a new monitoring application is released, it will become available immediately through the template.

Q: I would like to be notified whenever a new version of a monitoring applications is released. Can this template do that?

A: As per the article above, the automation templates are not responsible for notifications of whether the applications are out of date. This is achieved using Qlik Alerting on a per-application basis as described in Part 3.

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

A: 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. Each upgrade will generate a new set of QVDs as the data models for the applications sometimes change due to bug fixes, updates, new features, etc. If you want to preserve the history when updating, the application can be upgraded with the “Publish side-by-side” method so that the older version of the application will remain as an archival application. However note that the Qlik Alert (from Part 3) will need to be recreated and any community content that was created on the older application will not be transferred to the new application.

Qlik Data Gateway erroring out with "Invalid metadata response (DirectAccess-2201) " message. The error could be due to a different issues. 

Resolution

• Verify Privileges on the space where the Gateway was created and the Space where user is attempting to create the connection, our documentation describes the details  here
• If privileges are correct, try to restart Qlik Data Gateway services on the Server where it resides.
• Verify if the issue is specific to a connection, if one user was able to successfully create a connection, attempt to create a new connection with the user that is getting the error.
• If nobody is able to create a connection for an specific Data Source, attempt to configure a DSN ODBC connection from the Data Gateway Server to verify it succeeds. 

Cause

The cause of the issue is usually configuration, if the suggestions above didn't fix the issue it will be necessary to report the issue for further analysis. 

Related Content

Qlik Data Gateway: Direct Access Data Gateway failing with Internal Error 

Environment

• Qlik Cloud 
• Qlik Data Gateway 

The Qlikview server has been set up with Kerberos authentication. When navigating to the QlikView Management Console the following errors are shown:

Login Failed

This web page cannot be displayed

Environment

• QlikView 
• Kerberos authentication

Kerberos authentication is not supported in the QlikView Management Console.

For information regarding the AccessPoint, see Kerberos support using QlikView Webserver

How to get started with R-Script integration within Qlik Sense

The architecture of the integration at a High-level looks like this:



 

Qlik Sense Advanced Analytics integration is essentially an extension to Qlik Sense’s expression syntax, and as such it can be used in both Chart Expressions, and in Load Script Expressions.
 

With this new capability, we are now able to add syntax to a chart expression that tells Qlik Sense that particular expression should not be evaluated on the Qlik Sense server, but instead, all the information and data needed to calculate that expression should be sent via the server side extension on to the backend R system for calculation.

 After the advanced analytic calculations are completed, the data is sent back to the Qlik Sense Server and to the client for visualization.

Environment:

• Qlik Sense Enterprise on Windows , all versions

Resolution:

This video shows an example of how Qlik Sense connects to an R server for extending expression capabilities in Qlik Sense Apps while offloading the calculations to the R server engine.

Click here for Video Transcript

In order to start displaying a simple "Hello World" in Qlik Sense using a R-Script, we will do the following:

1. Have R & R-studio installed in your system. (RGui included with R for Windows can also be used) R can be downloaded at https://cloud.r-project.org/

2. We need a package in R to extend R functionality to applications via TCP/IP. The package name is "Rserve()"
Install the package using the below command in RStudio GUI:

install.packages('Rserve')

3. Now we need to invoke that library and start Rserve. In order to do so, execute the below scripts:

library(Rserve)
Rserve()

4.The communication method from Sense to R is taken care using gRPC. R is not a supported language in gRPC by default.

So a possible solution for this is to develop a connector in any of the supported languages of gRPC. Qlik provides an open-source connector developed in C# which in turn access Rserve to be able to run R scripts.
qlik-oss/sse-r-plugin
Once you built the connector,  start the SSEtoRserve.exe (ideally on the Rserve server itself)

Note: Qlik Support does not support this plugin directly. Inquiries should be submitted via GitHub under sse-r-plugin - Issues

5. Now we will have to configure the plugin:

For Qlik Sense Desktop June 2019 and up:

Add the following line in the settings.ini file:

SSEPlugin=R,localhost:50051

The settings.ini is located in this location: 

For previous Qlik Sense Desktop:

Add the following line in the settings.ini file:

SSEPlugin=R,localhost:50051

The settings.ini file is located in this location:

For Qlik Sense Enterprise/Server:

a. In the QMC, add a new Analytic Connection.
b. Restart the Qlik Sense Engine service.

Please refer to the screenshot below for creating a new connection.

Note: If the R-Plugin (SSEtoRserve.exe) was installed on the R-Server (where Rserve runs) or another machine, point to that machine name instead of 'localhost'. Also, in multi-node environments with multiple Qlik Sense Engines, even if the plugin was installed on the Central node, make sure to add the Central node's hostname instead of 'localhost' as the other Rim node Engine services need the correct DNS/Netbios name to reach the plugin.



6. Now Open a Qlik Sense App and add a KPI object in the sheet. This can be one of the Apps included with the  plugin itself under <storage path>\sse-r-plugin-master\sense_apps

Note that the example apps also need data connections to be created to the data files included with these apps files in the above location.

7. Otherwise, a new app can be created and any data may be loaded for the SSE example below.

8. For the measure, add the following expression which contains an R-script:

R.ScriptEvalStr('paste(q$firstWord, q$secondWord);', 'Hello' as firstWord, 'World' as secondWord)

9. If everything is configured properly, the R-script shown in bold above should be executed fine and it should display a "Hello World" message.

Understanding the R-script & Function:

R.ScriptEvalStr('paste(q$firstWord, q$secondWord);', Only([First Word]) as firstWord, Only([Second Word]) as secondWord)

Eight script functions are automatically added to the functionality of the plugin. What is needed to be covered on the plugin side to fulfill the functionality is to implement the EvaluateScript rpc function.

The syntax of these functions is: 

<EngineSSEName>.<FunctionName>(Script [,Parameter...])

Where the Script is an R-Script to be evaluated & Parameter is the data sent from Qlik's end.

Here, we use the ScriptEvalStr function which accepts argument of type String & returns a String. The 'paste' function in R concatenates vectors after converting to character. We pass two data fields of type string from Qlik (First Word & Second Word). The R-script then references these data fields through the q dataframe (structure already taken care in R) (q$firstWord and q$secondWord). The script/function finally returns a String back to Qlik Sense.

Related Content:

• Analytic Connections - Qlik Sense for Administrators 
• Script Regular Statements - Load - Qlik Sense on Windows 
• Creating an Advanced Analytics Server in 15 minutes using AWS 
• Qlik Server-Side Extension (SSE) with Analytic Connections 
• Getting Started with Advanced Analytics in Qlik Sense using Python 
• How to call an external / custom function in Qlik Sense? 
• Qlik Sense Analytic Connection (SSE) Error when reloading App 
  
  
   

Setting up Qlik Web Connectors may require you to provide administrator approval and consent for the respective apps (such as Azure storage, Office 358 Sharepoint, and similar). This article aims to provide you with information on what needs to be requested.

Account Types 

Personal Account: Once the connector has authorization to access the Microsoft account, there will be a corresponding entry in "My apps": https://myapps.microsoft.com/

Example:

Enterprise Account: These require additional configuration.

Granting Access for Enterprise Accounts

Once the enterprise application is selected, an application list will appear that the user can filter by searching for Qlik Web Connector:

• Enabled for users to sign-in? (Yes)
• User assignment required? (Yes) This field is only mandatory if the administrator wants to restrict access to the users.
• Visible to users? (Yes)
   
   

Testing (with administrator rights)

1. Open the Qlik Office 365 SharePoint connector
2. Select "Can Authenticate"
3. Press the green button "Authenticate"
   
   
   
   
4. You will be redirected to a Microsoft login page that should look similar to the following picture:
   
   
   
   
5. If Azure grants access, the Qlik Webconnector application will generate a code as follows:
   
   

Testing (without administrator rights)

If a basic (non-admin) user attempts to authenticate, the following message would appear in Azure:

To fix this, the administrator needs to grant access to the users.

Once the administrator grants access, the user will see the warning:

Need admin approval

A list of required API permissions for each connector

At this stage, you will need to request your administrator to enable the following API permissions for your user:

Azure Storage

• https://storage.azure.com/user_impersonation
• https://graph.microsoft.com/User.Read
  
  

MSCRM V2

• https://admin.services.crm.dynamics.com/user_impersonation
• https://graph.microsoft.com/User.Read
  
  

Office365 SharePoint

• https://graph.microsoft.com/User.Read
• https://microsoft.sharepoint.com/AllSites.Manage
• https://microsoft.sharepoint.com/AllSites.Read
• https://microsoft.sharepoint.com/MyFiles.Read

OneDrive V2

• https://graph.microsoft.com/User.Read
  
  Files.Read.All will also be required, although this is not set in the app registration.
  
  

Outlook 365

• https://graph.microsoft.com/Calendars.Read
• https://graph.microsoft.com/Calendars.Read.Shared
• https://graph.microsoft.com/User.Read
• https://graph.microsoft.com/User.Read.All
• https://graph.microsoft.com/User.ReadBasic.All
  
  contacts.read, contacts.read.shared, files.read, files.read.all, mail.read, mail.read.shared will also be required, although this is not set in the app registration. 

Environment:

• Qlik Cloud Analytics
• Qlik Sense Enterprise on Windows
• Qlik Web Connectors

Some connectors require an encryption key before you create or edit a connection. Failing to generate a key will result in:

Error retrieving the URL to authenticate: ENCRYPTION_KEY_MISSING - you must manually set an encryption key before creating new connections.

Environment

Qlik Sense Desktop February 2022 and onwards
Qlik Sense Enterprise on Windows February 2022 and onwards
all Qlik Web Storage Provider Connectors 
Google Drive and Spreadsheets Metadata 

Resolution

PowerShell demo on how to generate a key:

# Generates a 32 character base 64 encoded string based on a random 24 byte encryption key
function Get-Base64EncodedEncryptionKey {
$bytes = new-object 'System.Byte[]' (24)
(new-object System.Security.Cryptography.RNGCryptoServiceProvider).GetBytes($bytes)
[System.Convert]::ToBase64String($bytes)
}

$key = Get-Base64EncodedEncryptionKey
Write-Output "Get-Base64EncodedEncryptionKey: ""${key}"", Length: $($key.Length)"

Example output:

Get-Base64EncodedEncryptionKey: "muICTp4TwWZnQNCmM6CEj4gzASoA+7xB", Length: 32

Qlik Sense Desktop

This command must be run by the same user that is running the Qlik Sense Engine Service (Engine.exe). For Qlik Sense Desktop, this should be the currently logged-in user.

Do the following:

1. Open a command prompt and navigate to the directory containing the connector .exe file. For example:

   "cd C:\Program Files\Common Files\Qlik\Custom Data\QvWebStorageProviderConnectorPackage"
   
   

2. Run the following command:

   QvWebStorageProviderConnectorPackage.exe /key {key}

   Where {key} is the key you generated. For example, if you used the OpenSSL command, your key might look like: QvWebStorageProviderConnectorPackage.exe /key zmn72XnySfDjqUMXa9ScHaeJcaKRZYF9w3P6yYRr

3. You will receive a confirmation message:

   Info: Set key. New key id=qseow_prm_custom.

   Info: key set successfully!

Qlik Sense Enterprise on Windows

The {sense service user} must be the name of the Windows account which is running your Qlik Sense Engine Service. You can see this in the Windows Services manager. In this example, the user is: MYCOMPANY\senseserver.

Do the following:

1. Open a command prompt and run:

   runas /user:{sense service user} cmd. For example:runas /user:MYCOMPANY\senseserver

2. Run the following two commands to switch to the directory containing the connectors and then set the key:

   1. "cd C:\Program Files\Common Files\Qlik\Custom Data\QvWebStorageProviderConnectorPackage"

   2. QvWebStorageProviderConnectorPackage.exe /key {key}

      Where {key} is the key you generated. For example, if you used the OpenSSL command, your key might look like: QvWebStorageProviderConnectorPackage.exe /key zmn72XnySfDjqUMXa9ScHaeJcaKRZYF9w3P6yYRr

3. You should repeat this step, using the same key, on each node in the multinode environment.

4. Encryption keys will be stored in: "C:\Users\{sense service user}\AppData\Roaming\Qlik\QwcKeys\"

   For example, encryption keys will be stored in "C:\Users\QvService\AppData\Roaming\Qlik\QwcKeys\"

Always run the command prompt while logged in with the Qlik Sense Service Account which is running your Qlik Sense Engine Service and which has access to all the required folders and files. 

Cause

This security requirement came into effect in February 2022. Old connections made before then will still work, but you will not be able to edit them. If you try to create or edit a connection that needs a key, you will receive an error message: Error retrieving the URL to authenticate: ENCRYPTION_KEY_MISSING) - you must manually set an encryption key before creating new connections.

Related Content

Setting an encryption key