Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
This space offers a variety of blogs, all written by Qlik employees. Product and non product related.
By reading the Product Innovation blog, you will learn about what's new across all of the products in our growing Qlik product portfolio.
The Support Updates blog delivers important and useful Qlik Support information about end-of-product support, new service releases, and general support topics.
This blog was created for professors and students using Qlik within academia.
Hear it from your Community Managers! The Community News blog provides updates about the Qlik Community Platform and other news and important announcements.
The Qlik Digest is your essential monthly low-down of the need-to-know product updates, events, and resources from Qlik.
The Qlik Education blog provides information about the latest updates of our courses and programs with the Qlik Education team.
Our Instant Sense Application allows any data set to be uploaded and analysed. Even relatively simple datasets, like this one, can yield interesting discoveries. Perhaps the most striking thing is the large gap between the top seven players and the rest of the pack. The other thing is how the very top female players beat the top male players on many different measures.
As sports are divided into male and female competitions the data are often displayed and considered separately. By loading the data from two different sources and blending them a combined view can be given. Colouring the data by the competition dimension makes the achievements of the female players stand out.
The important thing when bringing data and analytics to people is to bring them data that they can engage with. Sometimes the simplest of data sources can be best at telling a story and drawing people in. Once those users have got used to navigating a simple dataset on a topic that interests them they will be ready to engage with the business data that can give them the edge.
Our Instant Sense Application is free to download and use and can be used over any dataset. It's a great way to provide a proof of concept and to quickly discover which measures are worth tracking. It ships with a number of scripts that are generally useful, such as Qlik Session Monitors and QVD Profiling, as well as scripts to load from online sources like this one.
Update 21st of March 16:00 CET: published CVE number
Update 27th of March 10:45 CET: added FAQ
Hello Qlik Users,
A security issue in QlikView has been identified and patches have been made available. Details can be found in the Security Bulletin High Severity Security fix for QlikView (CVE-2024-29863).
Today, 20th of March 2024, we have released two service releases across the latest versions of QlikView to patch the reported issue. All versions of QlikView prior to and including the releases below are impacted:
As no workarounds can be provided, Customers should upgrade QlikView to one of the following versions that contain the fix:
This issue only impacts QlikView. Other Qlik data analytics products including Qlik Cloud and Qlik Sense Enterprise on Windows are not impacted.
The Security Notice label is used to notify customers about security patches and upgrades that require a customer’s action. Please subscribe to the ‘Security Notice’ label to be notified of future updates.
Q: Is the vulnerability present in the QlikView Plugin or other QlikView products?
A: The vulnerability is related to the MSI files on disk.
Q: Will deleting the MSI files mitigate the issue?
A: Qlik does not consider removing the MSI files a complete workaround. A server user can restore them.
To our Talend 8 Customers,
To enhance both your security and Talend experience, Java 17 will be the only supported Java version for future updates to Talend Studio and the following supported applications.
Note: this upgrade does not impact execution of your artifacts that continue to support Java 8 or 11.
Previous versions of Java will no longer be supported by the above application when electing to upgrade to R2024-05. We are giving you this advanced notice to ensure you can plan this upgrade and take time to review your current Java environment. Java 17 support was first introduced with the R2023-10 release.
By giving this advanced notification, we are delighted to be able to reach a point of maturity where we can fully support best practices with dependencies and third-party libraries and be proactive in addressing CVEs to deliver constant improvement to the Talend Studio platform.
Compatibility Documentation:
For further questions please contact Qlik Talend Support and subscribe to the Support Blog for future updates.
Thank you for choosing Qlik,
Qlik Talend Customer Success
Hello Qlik Users,
Beginning on April 22nd 2024, Qlik Cloud will change how the font sizes for titles, subtitles, and footnotes are displayed. The change will carry over to Qlik Sense Enterprise on Windows with its May 2024 release.
Font sizes for titles, subtitles, and footnotes are controlled by either:
The conversion factor Qlik uses at present is incorrect, caused by a defect introduced by a previous change in a base font type.
What does this mean?
Currently, we convert using 13 as a base when we should be using 14. This results in the font size being slightly larger than the one set by the user.
The current scaling ratio is 1/13 * 14 =~ 1.077.
As an example:
The default theme Horizon, currently set to a 16-pixel default size, is in reality using 17.23 pixels.
Since we use other technologies to embed charts, we don’t want to replicate this error across all interfaces just to get matching title sizes. This means that we’ll now fix this defect, and start using the correct font size.
The fix is planned for Qlik Cloud on April 22nd 2024.
Qlik Sense Enterprise on Windows will receive the fix in its May 2024 release.
After the fix is deployed, the text in titles, subtitles and footnotes will appear smaller (about 93% of the current size), reverting to the intended size set by the user or the theme developer.
Since this will free up a small amount of space inside each object area, charts and graphics will become slightly bigger.
In rare scenarios, the resulting expansion might result in a different look for charts, where certain features (like labels or legends) appear, move or disappear due to the reaching of specific visual breakpoints.
No action is required for Qlik Cloud users. This change will automatically be applied to all the dashboards at the time of deployment. Qlik Sense Enterprise on Windows users will need to see their platform being upgraded to May 2024.
Can I preview the changes?
A preview is not possible before the deployment on April 22nd.
We're available for questions if needed! As always, thank you for choosing Qlik,
Qlik Support
We are happy to share with you the new Entitlement Analyzer for Qlik Sense Enterprise SaaS! This application will enable you to answer questions like:
The Entitlement Analyzer app provides insights on:
The Entitlement Analyzer uses a new API Endpoint to fetch all the required data and will store the history in QVD files to enable even better Analytics over time.
A few things to note:
The app as well as the configuration guide are available via GitHub, linked below.
Any issues, questions, and enhancement requests should be opened on the Issues page within the app’s GitHub repository.
Be sure to subscribe to the Qlik Support Updates Blog by clicking the green Subscribe button to stay up to date with the latest Qlik Support announcements. Please give this post a like if you found it helpful!
Kind regards,
Qlik Platform Architects
Additional Resources:
Our other monitoring apps for Qlik Cloud can be found below.
Hi everyone,
For various and valid reasons, you might need to migrate your entire Qlik Sense environment, or part of it, somewhere else.
In this post, I’ll cover the most common scenario: a complete migration of a single or multi-node Qlik Sense system, with the bundled PostgreSQL database (Qlik Sense Repository Database service) in a new environment.
So, how do we do that?
Let’s start with a little bit of context: Say that we are running a 3 nodes Qlik Sense environment (Central node / Proxy-Engine node / Scheduler node).
On the central node, I also have the Qlik shared folder and the bundled Qlik Sense Repository Database installed.
This environment has been running well for years but I now need to move it to a brand new hardware ensuring better performance. It’s not possible to reinstall everything from scratch because the system has been heavily used and customized already. Redoing all of that to replicate the environment is too difficult and time-consuming.
I start off with going through a checklist to verify if the new system I’m migrating to is up to it:
And then I move right over to…
The first step to migrate your environment in this scenario is to back it up.
To do that, I would recommend following the steps documented on help.qlik.com (make sure to select your Qlik Sense version top left of the screen).
Once the backup is done you should have:
Then we can go ahead and…
The next steps are to deploy and restore your central node. In this scenario, we will also assume that the new central node will have a different name than the original one (just to make things a bit more complicated 😊).
Let’s start by installing Qlik Sense on the central node. That’s as straightforward as any other fresh install.
You can follow our documentation. Before clicking on Install simply uncheck the box “Start the Qlik Sense services when the setup is complete.”
The version of Qlik Sense you are going to install MUST be the same as the one the backup is taken on.
Now that Qlik Sense is deployed you can restore the backup you have taken earlier into your new Qlik Sense central node following Restoring a Qlik Sense site.
Since the central node server name has also changed, you need to run a Bootstrap command to update Qlik Sense with the new server name. Instruction provided in Restoring a Qlik Sense site to a machine with a different hostname.
The central node is now almost ready to start.
If you have changed the Qlik Share location, then the UNC path has also changed and needs to be updated.
To do that:
At this point make sure you can access the Qlik Sense QMC and Hub on the central node. Eventually, check that you can load applications (using the central node engine of course). You can also check in the QMC > Service Cluster that the changes you previously made have been correctly applied.
Troubleshooting tips: If after starting the Qlik Sense services, you cannot access the QMC and/or Hub please check the following knowledge article How to troubleshoot issue to access QMC and HUB
You’ve made it here?! Then congratulation you have passed the most difficult part.
If you had already running and configured rim nodes in your environment that you now need to migrate as well, you might not want to remove them from Qlik Sense to add the new ones since you will lose pretty much all the configuration you have done so far on these rim nodes.
By applying the following few steps I will show you how to connect to your “new” rim node(s) and keep the configuration of the “old” one(s).
Let’s start by installing Qlik Sense on each rim node like it was a new one.
The process is pretty much the same as installing a central node except that instead of choosing “Create Cluster”, you need to select “Join Cluster”
Detailed instruction can be found on help.qlik.com: Installing Qlik Sense in a multi-node site
Once Qlik Sense is installed on your future rim node(s) and the services are started, we will need to connect to the “new” Qlik Sense Repository Database and change the hostname of the “old” rim node(s) to the “new” one so that the central node can communicate with it.
To do that install PGAdmin4 and connect to the Qlik Sense Repository Database. Detailed instruction in Installing and Configuring PGAdmin 4 to access the PostgreSQL database used by Qlik Sense or NPrinting knowledge article.
Once connected navigate to Databases > QSR > Schemas > public > Tables
You need to edit the LocalConfigs and ServerNodeConfigurations table and change the Hostname of your rim node(s) from the old one to the new corresponding one (Don’t forget to Save the change)
LocalConfigs table
ServerNodeConfigurations table
Once this is done, you will need to restart all the services on the central node.
When you have access back, login to the QMC and go to Nodes. Your rim node(s) should display the following status, “The certificate has not been installed”
From this point, you can simply select the node, click on Redistribute and follow the instruction to deploy the certificates on your rim node. After a moment the status should change and you should see the services being up and running.
Do the same thing on the remaining rim node(s).
Troubleshooting tips: If the rim node status is not showing “The certificate has not been installed” it means that either the central node cannot reach the rim node or the rim node is not ready to receive new certificates.
Check that the port 4444 is opened between the central and rim node and make sure the rim node is listening on port 4444 (netstat -aon in command prompt).
Still no luck? You can completely uninstall Qlik Sense on the rim node and reinstall it.
At this point, your environment is completely migrated and most of the stuff should work.
There is one thing to consider in this scenario. Since the Qlik Sense certificates between the old environment and the new one are not the same, it is likely that data connections with passwords will fail. This is because passwords are saved in the repository database with encryption. That encryption is based on a hash from the certs. When the Qlik Sense self-signed cert is rebuilt, this hash is no longer valid, and so the saved data connection passwords will fail. You will need to re-enter the passwords in each data connection and save. This can be done in the QMC -> Data Connections.
See knowledge article: Repository System Log Shows Error "Not possible to decrypt encrypted string in database"
Do not forget to turn off your old Qlik Sense Environment. As per your license agreement, you can only use one license per active Qlik Sense environment. Reach out to your account manager for more details.
Finally, don’t forget to apply best practices in your new environment:
What if you could prepare data (join, transform, STORE, etc.) using Qlik script - WITHOUT creating a standalone app - without sheets? Would you like that? Well, would you? Well now you can - introducing our new script object and script editor - with data preview and more! Watch this #qlik #SaaSin60 to learn more!
We have now added the ability to create Qlik scripts directly from the hub, ana managed in the catalog - using a new and improved script editor. Users can now build and deploy Qlik scripts upstream of analytics apps, which can be executed and result in output files in formats such as QVD and PARQUET that can be stored in the hub and used for analytics and AutoML applications. The script editor also now includes a data preview feature, allowing users to get better insight when developing scripts. This provides our customers with an improved workflow for preparing data, while setting the stage for future enhancements to analytics data prep capabilities.
As noted in Qlik’s 2024 industry trends – Hybrid AI Bridges the Maturity Gap, it’s critical to take a portfolio approach to AI – one that leverages both generative and predictive AI to solve a full breadth of problems. According to the Boston Consulting Group, generative AI is only expected to achieve ~30% share of the overall AI market by 2024. So in two year's time traditional machine learning will still represent the majority of the AI market. And there’s a reason for this – because traditional ML delivers highly actionable, accurate predictions for specific use-cases that can drive improved outcomes across your business and tremendous value.
For those of us who want to go beyond the out-of-the-box capabilities of Qlik Sense and want to leverage the full potential of the platform to create complex visualizations or satisfy custom development needs, understanding the Engine API is fundamental to taking advantage of what Qlik Sense hides under the hood.
The Qlik Engine API is a websocket protocol that uses JSON RPC 2.0 to communicate between the Qlik Associative Engine and clients. It works independently of any platform and programming language as long as it supports WebSockets and can parse JSON.
A great place to get your feet wet with trying out the Engine API is through Qixplorer (You might remember this as the Engine API Explorer on Qlik Managed). The tool that you can access at https://qixplorer.qlik.dev features a newly reimagined user interface and additional updates for a better experience.
Right off the bat, you can see that the format is divided into 4 main sections:
Other settings include a Light/Dark mode toggle at the top left, as well as a Layout toggle that lets you switch between the Original Layout (side by side request and response sections) or, my favorite, the Chat Layout.
The first thing you would need to create a new connection to your Qlik Cloud tenant is a Web Integration ID. You can grab that by going to your tenant’s Management Console, under Web, Create a new integration and add https://qixplorer.qlik.dev as an origin.
Once you have the generated ID in hand, create a new connection on Qixplorer as shown below:
The next step is to choose the app you want to connect to from the second dropdown.
Once you select that, you will see that a first request and response have been made automatically. That’s the “OpenDoc” method, it is responsible for opening an app. More about it here.
Notice that a few items are now highlighted on the Left panel that you can start using - including the Doc and Global classes that can be expanded to reveal all the methods you can execute. You can also use the pre-defined Macros to list sheets, dimensions etc...
⚠️Before we continue, keep in mind that when using Qixplorer, you are performing changes directly on your apps, so when executing API methods to update or delete within Qixplorer, it will affect the objects in your apps.
From the Macros dropdown, click on “ListSheets”.
Notice that the Request section at the bottom has our generated JSON with the methods needed to list sheets.
Click on Execute and view the JSON returned in the Response section.
P.S: notice that two separate requests have been made by our Macro: CreateSessionObject and GetLayout.
Let’s create an App in our tenant directly from Qixplorer.
First, select the “CreateApp” method from the Global dropdown.
Notice that the right panel has been populated with the inline documentation for our method. This makes it really convenient to view the definition and parameters at a glance.
Within the Request section that now contains the editable JSON, enter a name for the app we’re creating in the “qAppName” property.
Our request and response look like this:
{
"handle": -1,
"method": "CreateApp",
"params": {
"qLocale": "",
"qLocalizedScriptMainSection": "",
"qAppName": "test-qixplorer"
}
}
You can check your tenant to view the newly created app:
Let’s retrieve the calculated data from a Table object in our app.
First, we need to get the object. Under ”Doc”, scroll down to GetObject and change the “qId” property to our Table's object id.
Now that we got the object, you can go to ”GenericObject”, then “Select Object” and click on table.
Next, scroll down to the “GetHyperCubeData” method under “GenericObject” and modify the JSON as follows to set the qHeight (number of rows to retrieve) and qWidth (number of columns)
{
"handle": 2,
"method": "GetHyperCubeData",
"params": {
"qPages": [
{
"qHeight": 1000,
"qWidth": 5,
"qTop": 0,
"qLeft": 0
}
],
"qPath": "/qHyperCubeDef"
}
}
Click on execute and examine the response:
The Engine API is without a doubt very powerful as it exposes methods that can be used to tap directly into the associative engine and manipulate complex data structures. Having a tool like Qixplorer is a great way to try out the API and learn more about all the methods available in a single place.
Let me know in the comments how you use Qixplorer on you end!
Beginning with the May 2024 release, Qlik Sense Enterprise Client-Managed will release two major releases a year (May and November).
This adjustment aligns our release cycle with the preferred cadence of our customers, enhancing communication around our major releases. Qlik continues to add new functionality to Qlik Sense Client-Managed versions following their initial release to the cloud. As always, we will continue to deliver patches as needed under our Release Management Policy.
We look forward to helping you optimize your release experience. Be sure to follow the release notes area in Qlik Community and review our updated policy.