Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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 Learning blog offers information about the latest updates to our courses and programs, as well as insights from the Qlik Learning team.
This past week we released an exciting new AI capability – Qlik conversational analytics in Microsoft Teams. With the new Qlik app for Teams, you can easily chat with Insight Advisor, Qlik's intelligent AI assistant, to explore data using natural language directly within Teams. Users can now ask questions through individual or group chat and Qlik will respond with AI-generated data visualizations and insights, using data from across your Qlik apps. Because it's Microsoft Teams, you can collaborate with others in real-time, collectively making decisions using the insights generated by Qlik. And with the Teams mobile app, you have access to Qlik Analytics on-the-go, for insights at the point of decision.
Edit 17th September 2024: Added Oracle-to-Oracle bidirectional tasks issue
Edit 9th November 2024: Replaced expired links
A set of problems were identified in the Qlik Replicate 2024.5 release and actively addressed.
If you are planning to upgrade or have already done so and are seeing unexpected behavior, please review the highlighted knowledge articles for details:
After an upgrade to Qlik Replicate 2024.5, capturing changes (CDC) for a Table defined on a DB2i Source leads to conversion errors with the NUMERIC Datatypes with precision and scale greater than zero.
To mitigate, upgrade to 2024.5 SP03 (GA). Download it here (expires: 1/31/2025).
Read more here.
As a part of a Qlik Replicate upgrade to 2024.5, SAP HANA Source Endpoints using Version 1 configuration are converted to Version 3 CTS Mode.
To mitigate, upgrade to 2024.5 SP03 (GA). Download it here (expires: 1/31/2025).
Read more about the available workaround here.
With Store Changes (see Change Processing) turned on for CDC tasks, Qlik Replicate tasks may crash or stop unexpectedly with the new feature use_manipulation_pk_for_applyenabled.
To mitigate, upgrade to 2024.5 SP03 (GA). Download it here (expires: 1/31/2025).
Read more about the available workaround here.
Qlik Replicate tasks using Oracle as a Source Endpoint fail after installing the Oracle July 2024 patch.
To mitigate, upgrade to 2024.5 SP03 (GA). Download it here (expires: 1/31/2025).
Read more about the issue here.
Read more about the issue here.
Don't hesitate to contact us if you have any questions or concerns about the upgrade. We will monitor this blog post for your queries.
Thank you for choosing Qlik,
Qlik Support

Able to immediately interrogate Qlik Answers Assistants directly through WhatsApp. No browser or direct Qlik access needed!

Huge impact in customer service scenarios where it is not always possible to get a laptop out and interact with Qlik Answers natively. Great example is a field engineer that needs to request how to repair a particular model.

WhatsApp is a great option where mobility is an important part of the role. Also a preferred tool for those who are not "dashboard savvy" and don't want to have to log in and access systems to gain important insights on their unstructured data.

Inclusive access to Qlik Answers through secured Qlik APIs. Instant notification and convenience using WhatsApp.
Today’s corporate environment is global. QlikView application developers are required to support many regions and many languages. So how does a QlikView application developer handle multiple languages? Well, that depends on how the data is captured and the overall goal of the application developer. Let’s look at two scenarios.
Scenario 1: The developer only needs to translate the labels and textboxes within the application and not the actual data. 
=Only({<Index={12}>} [$(=vDataLanguage)])
for all textbox and object captions that need to be translated.
Scenario 2: The data from which the QlikView application developer is developing is recorded in English but he/she needs to have some of the actual data translated into other languages.

=$(vIndustry).
That’s it! Easy, right? Well, it is a bit time consuming if you are trying to translate data in fields but translating text and labels is really not that difficult. I created a technical overview that walks you through the two scenarios mentioned in this blog as well as a third scenario which can be found here. This resource includes a How-To, sample data files and 2 QVWs.
Good luck with the translations! Lycka till med översättningarna! 翻訳で頑張ってください!
Edited August 30th, 15:55 CET: Added clarification on older Qlik Sense Enterprise on Windows versions
Edited August 31st, 13:10 CET: Added clarification on possible workarounds (none exist) as well as information regarding what authentication methods (all) are affected and that HTTP and HTTPS are impacted
Edited November 21st, 8:40 CET: Added clarification to apply the latest patches
Hello Qlik Users,
Two security issues in Qlik Sense Enterprise for Windows have been identified and patches made available. Details can be found in Security Bulletin Critical Security fixes for Qlik Sense Enterprise for Windows (CVE-2023-41266, CVE-2023-41265).
This announcement from August 2023 and the mentioned releases only cover CVE-2023-41266 and CVE-2023-41265. Apply the most recent patches as documented in Critical Security fixes for Qlik Sense Enterprise for Windows (CVE-2023-48365) (September 2023), which resolve CVE-2023-48365 as well.
Today, we have released five service releases across the latest versions of Qlik Sense to patch the reported issues. All versions of Qlik Sense Enterprise for Windows prior to and including these releases are impacted:
All prior versions of Qlik Sense Enterprise on Windows are affected, including releases such as May 2022, February 2022, and earlier. While no patches are currently listed for these versions, Qlik is actively investigating the possibility of patching older releases.
No workarounds can be provided. Customers should upgrade Qlik Sense Enterprise for Windows to a version containing fixes for these issues. August 2023 IR released today already contains the fix.
This issue only impacts Qlik Sense Enterprise for Windows. Other Qlik products including Qlik Cloud and QlikView are NOT impacted.
All Qlik software can be downloaded from our official Qlik Download page (customer login required). Follow best practices when upgrading Qlik Sense.
The information in this post and Security Bulletin Critical Security fixes for Qlik Sense Enterprise for Windows (CVE-2023-41266, CVE-2023-41265) are disclosed in accordance with our published Security and Vulnerability Policy.
What can be done to mitigate the issue?
No mitigation can be provided. An upgrade should be performed at the earliest. As per Qlik's best practices, the proxy should not be exposed to the public internet, which reduces the attack surface significantly.
What authentication methods are affected?
All authentication methods are affected.
Are environments with HTTP disabled impacted?
Environments will be affected regardless if HTTP or HTTPS are in use. These vulnerabilities affect the HTTP protocol overall, meaning even if HTTP is disabled, the environment remains vulnerable.
These attacks don’t rely on intercepting any communication, and therefore, are indifferent whether the HTTP communication is encrypted or not.
Kind regards, and thank you for choosing Qlik,
Qlik Global Support
In recent times, there have been hackathons being organised by colleges on various topics and technologies. Clearly, there is a big interest from students and professors to organize such events. One of the key reason is that the academic community feels that this is a great way to learn and engage the student community.
According to digit.in, there are several benefits of a hackathon and they are as follows:
1. Learning a new technical skill
2. Creating a sense of accomplishment
3. Enhancing your soft skills
4. Beefing up your resume
5. Networking
6. Paving the path for a start up
7. Getting inspired
8. Giving back to the community
9. Winning a prize
10. Having fun
One of Qlik's academic partners, ICT Academy's CEO, Mr V Srikanth, mentioned in a recent article in The Times of India, that Learning based on Hackathon is the way forward.
The Qlik Academic Program has collaborated for three hackathons ( datathons) this year with Anurag Engineering College, Hyderabad, Kristu Jayanti College, Bangalore and the third one coming up with VJIT Hyderabad. There has been a good amount of participation in all these events. Students are more engaged, they are able to present their outcomes and get feedback on their creations from experts.
Overall, this is a win win for everyone and in some cases, prospective employers are able to gauge the skills of students from an event and offer opportunities. This way, hackathons have many benefits and are clearly a great way to engage students and make them industry ready.
For information on the Qlik Academic Program and to find out the resources including training and certifications for students and professors, please visit: qlik.com/academicprogram
In this blog post, I will revisit a topic that I blogged about over a decade ago, the use of a silent legend. By default, a legend is created in a visualization when there are multiple dimensions and/or measures. The legend helps the user understand the visualization. Legends are helpful and without them, users may not comprehend the data in a visualization. But what do you do if have many visualizations on a sheet? Do you need a legend for each chart? Let’s look at the various ways a legend can be used and how a silent legend can reduce the clutter and give a sheet a cleaner look.
In the screen shot below, there are four visualizations at the bottom of the sheet with legends.
In this app, the legends are all the same because the visualizations are using the same asset class dimension. A master item is used for the asset class dimension. This allows the colors for each dimension to be set in one place for consistency throughout the app.
In this example, the legend does not need to be displayed for each visualization because it is redundant. Let’s see how this sheet will look if only one of the legends are kept on the sheet. A legend can easily be removed by toggling off Show Legend in the properties of the chart.
Here is what the sheet looks like with just one legend.
The sheet looks better with one legend versus four legends. This use of one legend for four charts, has decluttered the sheet and reduced repetitiveness. If a developer wants a legend to be displayed without expanding the chart, they need to ensure the visualization is large enough. Without the legends in the three stacked bar charts, less space is needed for the charts, thus they can be made smaller, if desired, to take up less space on the sheet. Since all the visualizations at the bottom of the sheet are using the same legend, the legend was placed with the first visualization, assuming a user is reading top to bottom, left to right.
Now, the beauty of a silent legend is that all visualization legends can be removed from a sheet. In the screenshot below, the four headings at the top of the sheet are colored based on the asset class they represent. So, Equity is green, Fixed Income is dark blue and so on.
This is an example of silent legend. The legend is implied by the asset class headings. This option looks even better and cleaner than the sheet with one legend.
The use of a silent legend is possible in this app because there are only four values for asset class. I have seen this work nicely with up to six values. Anything more may become too cumbersome and may require a legend to be used. Also, if the four visualizations at the bottom of the sheet used different dimensions, then multiple legends should be used. Legends are important and they should not be removed to add space if the chart is unreadable without it. What good is a pretty chart if you do not understand it.
Thanks,
Jennell