Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team
Qlik offers a range of opportunities to assist you in troubleshooting, answering frequently asked questions, and contacting our experts. In this article, we guide you through all available avenues to secure your best possible experience.
For details on our terms and conditions, review the Qlik Support Policy.
Index:
We're happy to help! Here's a breakdown of resources for each type of need.
Support | Professional Services (*) | |
Reactively fixes technical issues as well as answers narrowly defined specific questions. Handles administrative issues to keep the product up-to-date and functioning. | Proactively accelerates projects, reduces risk, and achieves optimal configurations. Delivers expert help for training, planning, implementation, and performance improvement. | |
|
|
(*) reach out to your Account Manager or Customer Success Manager
Your first line of support: https://community.qlik.com/
Looking for content? Type your question into our global search bar:
Leverage the enhanced and continuously updated Knowledge Base to find solutions to your questions and best practice guides. Bookmark this page for quick access!
Subscribe to maximize your Qlik experience!
The Qlik Design Blog
The Design blog is all about product and Qlik solutions, such as scripting, data modelling, visual design, extensions, best practices, and more! (click)
The Product Innovation Blog
By reading the Product Innovation blog, you will learn about what's new across all of the products in our growing Qlik product portfolio. (click)
The Support Updates Blog
The Support Updates blog delivers important and useful Qlik Support information about end-of-product support, new service releases, and general support topics. (click)
Q&A with Qlik
Live sessions with Qlik Experts in which we focus on your questions).
Techspert Talks
Techspert Talks is a free webinar to facilitate knowledge sharing held on a monthly basis.
Qlik Fix
Qlik Fix is a series of short video with helpful solutions for Qlik customers and partners.
Suggest an idea, and influence the next generation of Qlik features!
Search & Submit Ideas
Ideation Guidelines
Get the full value of the community.
Register a Qlik ID:
Incidents are supported through our Chat, by clicking Contact Support on any Support Page across Qlik Community.
To raise a new issue, all you need to do is chat with us. With this, we can:
How to create a case using chat
Log in to manage and track your active cases in Manage Cases. (click)
Your advantages:
If you require a support case escalation, you have two options:
A collection of useful links.
Qlik Cloud Status Page
Keep up to date with Qlik Cloud's status.
Support Policy
Review our Service Level Agreements and License Agreements.
Live Chat and Case Portal
Your one stop to contact us.
Qlik Cloud is a modern analytics and data platform built on the same software engine as QlikView and Qlik Sense Client-Managed and adds significant value to empower everyone in an organization to make better decisions daily. Qlik Cloud allows you to use one common platform for all users – executives, decision-makers, and analysts.
Navigation:
Migrating to Qlik Cloud can help your organization:
Q&A with Qlik: Qlik Sense Migration to Qlik Cloud
Articles relevant to migration and new Qlik Cloud users
This site provides you the tools to monitor, manage, and execute a migration from Client-Managed Qlik Sense to Qlik Cloud.
Index and home
Planning your migration
Setting up the Qlik Cloud migration tools
Create and configure a cloud tenant
This site provides you the tools to begin your journey to move from QlikView to Qlik Sense and Qlik Cloud.
March 14th 2023: You may have upgraded Qlik Sense and located a warning banner in your Management Console stating that this version of PostgreSQL is not supported. If you are running a standalone PostgreSQL database later than 9.6, this message can be disregarded. We are working on resolving the underlying cause.
In this article, we walk you through the requirements and process of how to upgrade an existing Qlik Sense Repository Database from PostgreSQL 9.6 to PostgreSQL 12.5 (see supported scenarios) or install a brand new Repository based on PostgreSQL 12.5.
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
PostgreSQL 9.6 has reached End of Life Reference: PostgreSQL Versioning Policy.
Download the installer here.
Qlik PostgreSQL installer version 1.2.1 Release Notes
Before using the Qlik PostgreSQL Installer, upgrade to a supported version of Qlik Sense Enterprise on Windows. Then use the Qlik PostgreSQL Installer to upgrade PostgreSQL.
We tested and validated Qlik Sense Enterprise on Windows from February 2022 to February 2023. Note that November 2022 and later do not support 9.6, and a warning will be displayed during the Sense upgrade.
Qlik Sense Enterprise on Windows installations other than in C:\Program Files\Qlik\Sense are currently not supported.
If the upgrade was unsuccessful and you are missing data in the Qlik Management Console or elsewhere, contact Qlik Support.
No further steps are needed unless you plan to upgrade Qlik Sense Enterprise on Windows to the next major release. If you plan to upgrade to, for example, November 2022, the old Qlik Sense Repository Database service must be removed from the server.
Perform the following steps to delete the Qlik Sense Repository Database Service:
This version of the upgrade tool is fully compatible with the official PostgreSQL installers from https://www.enterprisedb.com/downloads/postgres-postgresql-downloads.
If you need to upgrade to a higher release than Qlik provides, you can install the same minor PostgreSQL release 12.x.
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.
Qlik PostgreSQL installer version 1.2.1 Release Notes
Techspert Talks - Upgrading Qlik Sense Repository Service
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
Loading files larger than 50MB from either Dropbox or SharePoint with their respective connectors leads to:
Data file size exceeded file streaming buffer size. Adjust the StreamingBufferSizeMB setting.
Qlik Sense Enterprise on Windows
Qlik Cloud
The solution requires us to modify the Qlik Sense Engine settings.ini. See How to modify Qlik Sense Engine settings.ini for details on the procedure.
The value cannot be configured in Qlik Cloud. A workaround is to split the big data files by e.g. months.
QLIK-83207
CP-4120
QLIK-82097
When trying to connect to Qlik Sense Hub/QMC or QlikView Access point/QMC using a DNS ALIAS (or CNAME) record you are prompted to authenticate.
After validating your credentials, it doesn't work and you are prompted again until the page goes completely blank.
In the Windows System Event logs you will see this message:
Connecting to Qlik Sense/QlikView outside the QlikSense Server works.
Connecting from Qlik Sense/QlikView Server using the server name or the IP address in the URL works.
For this issue with Qlik Sense you may also have the below Audit_Proxy warning:
4783 20200414T025339.978+0200 WARN SERVERNAME Audit.Proxy.Proxy.Core.Connection.Validation.ConnectionDataValidator 27 03f227fe-53e8-478f-857c-8099358a7963 DOMAIN\QLIKSENSEACCOUNT Http request Host is not allowed: 79.137.105.56. 0 18716f09-d684-48fc-bf1b-feb97f63e430 ::ffff:193.118.52.26 0024ddbcac7413c72adefc2ff4ce78e0f91eae88
Environment:
This article shows you how to locate your Qlik Cloud license number (Subscription ID) as well as your Tenant Hostname, your Tenant ID, and your Recovery Address.
If you are looking to change your Tenant Alias or Display name, see Assigning a hostname Alias to a Qlik Cloud Tenant and changing the Display Name.
Qlik Sense allows for three settings that may influence the perceived connection and session timeout period. These are the "Session Inactivity Timeout", "Keep-Alive Timeout", and "TCP Websocket keep-alive" settings.
Note: Adjusting the below settings can help when working with slow internet connectivity or wanting to extend the session inactivity. However, session disconnect issues can be caused by other network connectivity issues and by system resource shortage as well and may require additional troubleshooting. See Hub access times out with: Error Connection lost. Make sure that Qlik Sense is running properly
This is the maximum timeout for a single HTTP request. The default value is 10 seconds. During the defined keep alive timeout value, the connection between end user and Qlik Sense will remain open.
It serves as protection against denial-of-service attacks. That is, if an ongoing request exceeds this period, Qlik Sense proxy will close the connection.
Increase this value if your users work over slow connections and experience closed connections for which no other workaround has been found. Make sure to take the mentioned DoS consideration above into account.
This is the browser authentication session time out ( 30 minutes by default set under Virtual Proxy in QMC ). This sets a cookie on the client machine with the name X-Qlik-Session. This cookie can be traced in Fiddler or Developer tools under the header tab.
If the session cookie header value does not get passed, is destroyed, or modified between the end user client and the Qlik Sense server while 'in-flight' the user session is terminated and the user is logged out.
By default, it will be destroyed after 30 minutes of inactivity or when the browser is closed.
This is another setting that may help keep the connection open in certain environments. See Enabling TCP Keep Alive Functionality In Qlik Sense. Note that customers who don't experience any issues with web sockets terminated by the network due to inactive SHOULD NOT switch this feature ON since it may potentially cause Qlik Sense to send unnecessary traffic on the network towards the client.
Let's imagine you have millions/billions of rows of disparate data. That's not hard to imagine. You do.
Let's imagine that you need to create analytics from all that data. That's not hard to imagine. You do.
Let's imagine that you have a data integration pipeline with change data capture to keep changes constantly flowing for those sources. That's not hard to imagine. You do.
Let's imagine that you want to quickly get those changes into your analytics applications being used by thousands of end users without having to touch the other millions/billions of rows of disparate data you already loaded. WOW! Now that is hard to imagine.
Before I propose a super simple solution to that hard to imagine issue, I need to share just a few Qlik basics to solidify my proposal:
Those concepts are different. They are unique. Sometimes those things can be frustrating for those new to Qlik because it makes them think differently than they have for their entire life. I get that. It is these differences that allow Qlik customers to associate disparate data sources in-memory for speed of thought insights with minimal impact to underlying source systems.
Don't get me wrong. You do not have to take advantage of them, or follow this model at all. You can absolutely use Qlik like other tools. You can push down any SQL you want, including statements that contain as many JOIN clauses as needed. You can pull data live from your data sources on the fly via Direct Query, On Demand Application Generation or Dynamic Views. Each of those options have use cases that they are well suited for. They just aren't suited for this enterprise use case where we have millions/billions of rows of data that we need to analyze. While also rapidly incorporating any changes that might be flowing through our data integration pipelines so that our impact of reading the data, and the costs associated are kept to a minimum.
Those Qlik basics I referred to, have always enabled Qlik architects to perform incremental loads of data. The changes. Regardless of whether the source systems involved:
Qlik architects could write script that would load and merge those incremental changes as required. Allowing for super rapid data refreshes that had little impact on the source systems. While awesome, there were some minor issues. Architects had to know what the source systems allowed, and had to write different types of scripts for each of the use cases. Deletions were thought provoking for sure. Neither is hard to overcome because there are a ton of posts online you can find with examples. Including Qlik's own help site.
The only thing that could make the situation any easier is if the source systems would flat out say "You need to insert/update/delete this row of data." If they did that, Qlik data architects could simply say "Here is the existing data I already have loaded into memory, now go merge these changes that the system has."
Assuming of course that Qlik provided a MERGE function that would:
The great news is that Qlik does indeed provide a MERGE function that will do just that. But what about the source systems? As it turns out whether you are using Qlik Replicate on-premise, or Qlik Cloud Data Integration in your SaaS/PaaS tenant, the change tables written provide the information needed for the merge function to work. Here is an example of data stored in the change table.
Well lookie theire. The update, insertion and deletion are clearly identified as well as the values impacted.
Here is an example of the code I wrote that passes that data to the Merge function in my load script:
To understand the merge function ... assume that I currently have a table called "DemoTable" in memory that has millions/billions of rows with the following columns in it: KeyField, DemoTable_Field1, DemoTable_Field2, DemoTable_Field3.
The "on" clause of the merge command indicates the field that represents the primary key for the table, in my case it is simply called "KeyField."
The "concatenate" clause of the merge command indicates the in-memory table that you want to merge data into/with.
The "select" clause is simply a typical SQL select statement that will pull the data that you want to merge. The first field of the return will have the values for update, insert, or delete so that the merge function will know what to do with that row.
The "where" part of the clause simply filters the selection to the rows in the change data capture table that have occurred since the last time I reloaded my data. Which in my case is stored in a variable and updated after each time the merge is performed.
Let's imagine that you want to quickly get changes that are flowing from your source systems with change data capture into your analytics applications being used by thousands of end users without having to touch the other millions/billions of rows of disparate data. Hard to imagine?
Not anymore, my friends, not anymore. Your load scripts can now quickly and easily incorporate these merges keeping your QVD files/applications up to date with very minimal impact on your systems, with minimal cost on your budget.
But wait, there's more! Because it is so lightweight/efficient, this merge functionality also provides the benefit of being able to be utilized via partial reloads. Meaning you can allow your end users to take action in their own sessions to perform the merge in use cases where it makes sense. Thus, enabling them to have the confidence that they are indeed seeing the very latest/greatest/newest/freshest data. You gotta be loving that.
If you aren't already using Qlik Replicate or Qlik Cloud Data Integration and still want to take advantage of the Merge function you can. You just need a method of getting the update, insert and delete information from the system you are reading from. If you are using Snowflake you can take advantage of their time travel functionality as well. Click this link to read my post on using Snowflake's time travel with the merge function.
* Qlik QVD files typically offer 70-95% space savings over original data/text files.
Analyzer Capacity Licenses can be assigned automatically based on Analyzer Capacity License Rules. These rules can be set up to provide Analyzer Capacity to users, groups, or anonymous users.
This article covers what function the license type has, how to assign it, and how to track usage.
Index:
The Qlik Sense Analyzer Capacity license type is automatically assigned to users not assigned a Professional or Analyzer license and consumes time during an active session with the minimum session length set to 6 minutes.
Overview:
Details:
No setup is required. If no Professional or Analyzer License was assigned, Analyzer Capacity is automatically allocated.
See Enabling dynamic license assignment for details.
The Entitlement Analyzer for Qlik Cloud provides detailed usage data for Analyzer Capacity, but a tenant admin can gain an overview through the Management Console at any time:
The bundled License Monitoring app provides usage data for Analyzer Capacity, but an administrator can gain an overview through the Qlik Sense Management Console at any time:
Analyzer capacity license and monitoring (Client Managed)
Qlik Licensing Service Reference Guide
Assigning user allocation (Qlik Cloud)
Analyzer capacity license (Qlik Cloud)
Top 5 things to know about modern Qlik Licensing
When performing an ALTER TABLE ADD COLUMN on a DB2 z/OS application table, the newly added column is not captured. Even though DATA CAPTURE CHANGES is SET at the application table level, the column is not coming through to the target.
There is a simple solution to this situation. Ask the DB2 DBA to set :
ALTER TABLE SYSIBM.SYSTABLES DATA CAPTURE CHANGES on this system table.
The cause is a mere oversight of turning on this setting on the SYSIBM.SYSTABLES
Installing and upgrading the R4Z product in z/OS | Qlik Replicate Help
Qlik Replicate and corresponding R4Z - Any Version
DB2 z/OS - Any Version
Global expressions are not propagated to all tables.
Defining a soft delete transformation can be done on each individual table as needed. However, if you want to do it for all tables in the task you will want to use a Global Transformation.
Issue
The issue manifested when defining a Global Expression to do a soft delete.
The field is supposed to be automatically added to all tables in the task. The field was not added to all tables. It was random results as some tables had the field and others did not.
When reviewing the process of defining the expression we noticed there are two screens which would allow you to enter the expression.
When we used both the Transformation Scope / Advanced Options screen and the Transformation Action / Value screen, not all tables got the field.
Example: Transformation Scope, with Advanced Options expanded:
Resolution
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.
Transformation - Operation Indicator - Archive User - Soft Delete
Using Engine API, creating "Hidden Bookmarks" will require Professional User license. Analyzer user, can not create "Hidden Bookmarks".
User with "Analyzer license", will have "Access denied" when creating "Hidden Bookmarks" using Engine API explorer
{
"handle": 1,
"method": "CreateBookmarkEx",
"params": {
"qProp": {
"qInfo": {
"qId": "",
"qType": "hiddenbookmark"
},
"qMetaDef": {}
},
"qObjectIdsToPatch": [
""
]
}
}
Getting this error:
{
"jsonrpc": "2.0",
"id": 3,
"error": {
"code": 5,
"parameter": "Access denied",
"message": "Access denied"
},
"isHandled": true
}
Bug QB-17807 reported to R&D and closed as WAD (working as designed) with the following explanation.
---------------
This is by design. A professional user can create all types of object whereas an analyzer user cannot.
---------------
Information provided on this defect is given as is at the time of documenting. For up to date information, please review the most recent Release Notes, or contact support with the ID XX-QB-17807 for reference.
Product Defect ID: QB-17807
In this article, we detail the 12 steps necessary to successfully configure Qlik Sense Enterprise on Windows after an Active Directory Domain name change or moving Qlik Sense to a new domain.
Depending on how you have configured your platform, not all the steps might be applicable. Before updating any hostname in Qlik Sense, make sure that the original value is using the old domain name. In some case, you may have configured “localhost” or the server name without any reference to the domain so there is no need in these cases to perform any update.
In this scenario we are updating a three-node environment running Qlik Sense February 2021:
The domain has been changed from DOMAIN.local to DOMAIN2.local
The servers mentioned below are already part of the new domain name DOMAIN2.local and their Fully Qualified Domain Name (FQDN) is already updated as followed:
All Qlik Sense services have been stopped on every node.
The first step is to update the postgres.conf file to listen on the correct hostname
Before doing any further changes, it is important to take a backup of your Qlik Sense Platform
Now we update the node names in the database with the new Fully Qualified Domain Name.
UPDATE public."Users"
SET "UserDirectory" = 'DOMAIN2'
WHERE "UserDirectory" = 'DOMAIN';
SELECT * FROM public."Users"
cd "C:\Program Files\Qlik\Sense\NLAppSearch\install"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
cd "C:\Program Files\Qlik\Sense\AppDistributionService"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
cd "C:\Program Files\Qlik\Sense\HybridDeploymentService"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
cd "C:\Program Files\Qlik\Sense\Licenses"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
cd "C:\Program Files\Qlik\Sense\NotifierService\install"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
cd "C:\Program Files\Qlik\Sense\MobilityRegistrarService\install"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
cd "C:\Program Files\Qlik\Sense\PrecedentsService\install"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
cd "C:\Program Files\Qlik\Sense\DataPrepService\install"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
If you are using the Qlik Logging Service;
cd "C:\Program Files\Qlik\Sense\Logging"
Qlik.Logging.Service.exe validate
cd "C:\Program Files\Qlik\Sense\Logging"
Qlik.Logging.Service.exe update -h QlikServer3.domain2.local
"C:\Program Files\Qlik\Sense\Repository\Repository.exe" -bootstrap -iscentral -restorehostname
If you are syncing your users with a User Directory Connector you will need to change the LDAP path to point to the new domain.
You will need to update the monitoring apps and their associated data connection to use the new Fully Qualified Domain Name
It is possible that you have created rules based on the User Directory. As you have changed the domain name, the user directory has also changed in Qlik Sense so you will need to update those to reflect that.
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 Qlik Community is a great resource where all Qlikkies can connect, collaborate and share with their peers, Qlik support engineers, Qlik product management, and Qlik experts!
Since multiple forums are available for each product, community users can post discussions in the most relevant area. Both new and experienced Qlik product users help others learn new tips, share information and provide solutions by replying to discussions. Qlik product managers, Qlik support engineers, Qlik product and services experts as well as Qlik community administrators are moderating all of the forums and blogs. Look for the headset icon to identify Qlik Support responses and the star to designate other Qlik employee responses.
What types of questions should be asked in the Qlik Community?
Search first before posting. Chances are someone else has already posted your question and answer. If the search does not result in an answer to your question, continue with posting on the Qlik Community. For step by step instructions on posting a question, check out this post. Any kind of question can be asked on the Qlik Community!
The Community is an excellent resource for asking how-to, scripting, app development and best practice questions. Some examples of questions include but are not limited to:
Note: Qlik Community pages, Qlik Help documents, and Qlik public knowledge articles are all regularly indexed by the major search services like Google. Be sure to append the product name when searching to retrieve specific results regarding Qlik (ex: Qlik, Qlik Sense, QlikView, NPrinting, etc). Qlik Community results as well as results from Qlik.com, Qlik Help and Qlik Support Portal display.
What information should I include when posting to the Qlik Community?
The more information the better! Depending on the question, more details may be required to get the conversation flowing. Try to provide as much detail as possible and don't be surprised if peers or other product experts may ask for more information. A solid post should include:
Once the question has been posted, make sure to set up notifications so you do not miss when others respond to and like your post. If a response is received that answers the question or solves the issue, be sure to mark the answer as correct by clicking 'Accept as Solution'. This will mark the post as solved and other Qlikkies will gravitate towards this post as it as a possible solution for their issue. Multiple responses can be accepted as a solution so make sure to select all that apply.
How can I participate in this great Community?
It's easy! Create a Qlik Community login and start surfing the forums. Add your thoughts and ideas to any post, let others know you've experienced the same behavior, or like any resolution that has helped you answer a question. Be kind, encouraging and offer any insight you can! Don't be afraid to post a question as others probably have the same one. For more information on using the Qlik Community, start here! Once you get started, navigate to our popular blogs and subscribe. Join a group. There so much you can learn and share when you are connected to the Qlik Community.
Thank you for being apart of this wonderful Community! Happy Qlikking!
Starting at Qlik Sense Enterprise on Windows May 2021, the bundled PostgreSQL has been upgraded to version 12.5.
However, PostgreSQL 12.5 will only be deployed during a fresh installation of Qlik Sense Enterprise on Windows May 2021. This means that, if you are upgrading to Qlik Sense Enterprise on Windows May 2021, PostgreSQL will remain on 9.6.
For many organizations, running on the latest supported PostgreSQL version is a security requirement. To achieve this:
Content:
The information in this article is provided as-is and to be used at your own 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.
This process requires a full reinstallation of the product. Despite the fact that a backup is being taken as part of the process, it is highly recommended to have a second backup plan in place such as a Virtual Machine snapshot and/or a Server Backup.
It is highly recommended to test this process in a test environment to get familiar with it.
The first step is to upgrade your environment to Qlik Sense Enterprise on Windows May 2021 following the steps and recommendations provided on this link.
Once the upgrade is done make sure your Qlik Sense site is completely operational.
At this point, you have an operational Qlik Sense site running on Qlik Sense Enterprise on Windows May 2021, however, the bundled PostgreSQL is still on version 9.6.
The next step will be to backup your entire Qlik Sense site following these instructions (including the certificates) . The backup is essential as it will need to be restored later on.
You will now need to uninstall Qlik Sense from the central node following these instructions.
During the uninstall:
Now that Qlik Sense Enterprise on Windows May 2021 is uninstalled on the central node, you will reinstall it as a result will deploy a bundled PostgreSQL 12.5. Instructions available here.
Do not check the box Start theQlik Senseservices when the setup is complete at the end of the installer.
You now have a clean Qlik Sense Enterprise on Windows May 2021 deployed on your central node with PostgreSQL 12.5. You now need to restore your environment to retrieve all your configurations and apps.
Please follow the Restoring a Qlik Sense site (including the certificates).
Note: While restoring the database backup you will most likely receive the following error which can be ignored. This error is caused by the version discrepancies between the pg_dump that made the dump file and the pg_restore that's restoring it - in example files coming from PostgreSQL version 9.6 vs files coming from PostgreSQL version 12.5. QSR backup taken and restored with the same version of PostgreSQL will not produce that error.
pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 3; 2615 2200 SCHEMA public postgres
pg_restore: error: could not execute query: ERROR: schema "public" already exists
Command was: CREATE SCHEMA public;
pg_restore: warning: errors ignored on restore: 1
Once the environment is restored, you should be able to start your central node and rim nodes successfully.
Qlik Sense Enterprise on Windows May 2021 and later
Within the available connectors in Qlik Application Automation are Microsoft Onedrive & Microsoft Sharepoint . This article intends to describe some potential use cases that can be performed through the use of these connectors and provide an easy to use template to do so. Most examples are built using the Onedrive connector, however the same use cases can be performed for shared drives using the Sharepoint connector.
Authentication for the connector happens with oAuth2. We are making use of the following scopes for the Onedrive connector:
These scopes should be accessible for all users in a default Office 365 tenant. If you are having troubles attempting to authorize Qlik Application Automation to obtain these scopes consult your Office 365 administrator.
Using Automations in Qlik Cloud it is possible to monitor changes to a user's personal Onedrive or to a Sharepoint shared drive. When changes to a personal or shared drive happen, automatic actions can be performed, such as automatically obtaining data from an uploaded excel spreadsheet and updating a Qlik Sense app.
Onedrive makes use of a delta token to view changes that have happened since that token. As we do not have a data store within Automations, we are bound to use a separate store for the delta tokens. Options could be an excel file / text file stored on Onedrive, an app on Qlik Sense or any other place where data is persisted.
An example automation to monitor changes might look like the following. The automation is also added as JSON to the article to import into a Qlik Cloud tenant.
The Microsoft Onedrive and Microsoft Sharepoint connectors in Qlik Application Automation provide blocks to Move and Rename items on drives. These can be used for example in conjunction with other connectors to perform these actions whenever … happens
An example could be to move all files from an incoming folder to an archive folder after a Qlik Sense reload is complete.
A simple example automation is added as an attachment to this article. In the automation editor this might look like the following:
The block Create Sharing Link can create a shareable URL that can be send over email to a user.
It offers the user the choice whether the URL works for the organization of the user or anonymous. The scope can be set to view, edit or embed and it is possible to provide a password as well as an expiration time for the shareable link.
The following automation would obtain data from a table in Qlik Sense, copy the rows to an Excel file hosted on Onedrive, create a shareable link and share this link to a user by email:
Sharing permissions can be done with the Send Sharing Invitation. This block sends an invitation to an email recipient including a message, subject, reading or writing permissions and the choice if an invitation has to be sent out and whether a user has to be signed in. A password can also be provided, but only if the user is using a personal Onedrive account.
Furthermore it is possible to list sharing permissions, updating these permissions and removing permission to access a file on a user's Onedrive.
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.
In a default Qlik Sense map, the Base map property may disappear.
This property is accessed through:
Images of Default, Pale, Satellite, Projection, and None may all be missing, and the text heading of Select a map type is also gone.
Verify that you have access to maps.qlikcloud.com.
If the user running the app does not have access to maps.qlikcloud.com, then the base map disappears from the chart and also the Base Map setting in properties disappears. This can happen if the user is a guest on the network and does not have rights to get to the site, or some similar situation. When the user gets access to this site or when the next user accesses the app, the base map should reappear in the map chart and the base map properties should also reappear.
To verify if you can reach maps.qlikcloud.com using (for example) Chrome Developer Tools and reviewing the Network tab for errors.
If you have internet access to maps.qlikcloud.com, verify in the the Developer Tool/Har Log if your base map is attempting to fetch from ga.qlikcloud.com instead of maps.qlikcloud.com.
This is likely caused by Qlik GeoAnalytics having been used previously only to be replaced by the native map. If so, we will manually replace the ga reference with maps in the mapconf.json file.
For more information, see: How to change the map url in built-in map chart to a local GeoAnalytics map server