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.
A table recipe is an easy, no-code way to prepare a data set for an app, data flow, script or ML experiment. It is a great way for new users to prepare their data and get started building an app without having to write the script to transform the data. It can also be used by experienced users for quick data prep. Table recipe is available in Qlik Cloud Analytics from the Analytics activity center > Prepare data. You can also access it from the + Create menu option or + Create New button in the catalog. To begin using it, open table recipe, give it a name and select the space you would like to create it in. Once that is done, you will be prompted to select the data set. Note - the table recipe processes one data set at a time.
Once a data file is selected, you can view the fields to confirm it is the correct data set and then you can load it into table recipe. Once it is loaded, you will see a pop up indicating the number of rows and columns in the dataset. Note that all the rows may not be loaded into the table recipe editor, but the recipe will be applied to the entire data set when it is run. Below is a look at the table recipe. On the left is the functions panel that includes several functions that can be used to prepare the data. Functions are grouped as general, columns, strings, dates, numbers and math. On the right is where the steps in our recipe will be added.
Let’s begin with a simple step like deleting a column. I have a Fax column that I do not need so to delete the column; I can click on the column menu (three vertical dots) and select Delete column.
The step will appear on the right in the table recipe, and I can click Apply to remove the Fax column.
Next, let’s split a column into two new columns. I have a Contact Name field with the contact’s full name. I would like to split the name into two fields – one for first name and one for last name. To do this, I will select the Split column function from the list of string functions on the left. Then I can update the details and apply the step. I will change the separator to a space since that is what separates the first and last name in the ContactName column.
Once I apply that step, I can see the two new fields it generated.
I will open the column menu and select Rename column to change the names of the new columns. Once I apply those steps, the columns and the recipe look like the image below. Keep in mind that the table recipe has steps that flow in a specific order. If those steps were to change, you may not get the expected results. For example, if I moved the rename column step above the split column step it would not work because the column I am renaming does not exist yet.
It is also easy to reorder the columns with the table recipe. The Reorder column function is found in the function group named Columns. Simply, select the column you would like to move and click on the Reorder column function. To move the Address column to the left of the City column, I will select the City column from the Anchor column drop down and then click Apply.
We are also able to apply filters to the data if we want to focus on specific rows. In this example, Country has two different values for the United States – USA and US. I would like to change the US values to USA.
After applying the filter, I can see that I have 6 rows with US as the Country. I can use the string Search and replace function to replace US with USA.
This step included my filter, so it only applied it to the rows I have filtered on.
Let’s perform one more step that I use all the time when loading data. We will extract date parts from the OrderDate field. This will allow us to create other date fields such as month and year fields. If I select the OrderDate field and then select the date function Extract date parts, I am presented with all the possible date part fields I can add as a column to my data set. I simply can toggle on any new fields I would like to add.
Once this step is applied, I can see the 4 new date fields I added.
When all the steps have been added to the table recipe, the next steps are to set the target and run the recipe. Setting the target is nothing more than giving the target file a name and file type (qvd, parquet, txt or csv) and selecting the space to create it in.
What is nice about the table recipe is the steps are applied and stored in a new file, separate from the original data set, so you do not have to worry about incorrectly modifying the data set. Once the target is set, the Incomplete recipe message at the top of the page will change to Valid recipe and the Run recipe button will be enabled. Once the recipe is run, you can view your new data set and use it accordingly. The target data set will be stored in the desired space and can be accessed anytime via the catalog.
Notice how all these steps we are creating are very easy and intuitive to build. You do not have to be an expert to perform these steps, and the editor is very user friendly and has a clean flow. What is also nice is that you can see that each step is working as expected when you apply it. Take this product tour to get a feel for the table recipe and then try it for yourself. To learn more, check out Qlik Help.
Thanks,
Jennell
Hey guys join @Jennell_Yorkman and I for a quick community resource update as we highlight some of the latest ideas, enhancements, and best practices being shared across the Qlik Design Blog and Qlik Community.
From dashboard design and developer capabilities to visualization techniques and platform improvements, this session is a fast-paced roundup of useful content and community-driven insights to help you get more out of Qlik. Whether you’re building apps, designing dashboards, or exploring new capabilities, this is a great way to stay connected with what’s happening across the Qlik ecosystem.
Edited May 4th, 2026: Added mitigation article, published on the 4th of May.
Beginning on April 14, 2026, multiple QlikView customers experienced outages and intermittent disruptions within their QlikView environments. These incidents coincided with the deployment of Microsoft’s April 2026 security patches to Domain Controllers, which affected QlikView Server Service (QVS) communications over port 4747.
The Microsoft patches introduced changes targeting Kerberos authentication and RC4 encryption. See Addendum for a list of patches. As a result, QlikView environments where RC4 remained enabled (such as at the domain account or Windows server level) became unstable or non-functional.
The impact on QlikView may include, but is not limited to:
We've published an article to help address the issue. See QlikView server communication interruptions following Microsoft Windows RC4 cipher suite deprecation.
Information in the article is based on Microsoft's remediation steps and has been adjusted and expanded to include QlikView-specific instructions. For the original, see Detect and remediate RC4 usage in Kerberos | learn.microfot.com.
RC4 support was deprecated starting with the May 2024 release of QlikView. The root cause in these cases stems from legacy configurations where RC4 remained enabled in the environment, rather than a defect in QlikView itself. No code changes are planned at this time, though improvements to diagnostic logging are under consideration.
Microsoft Patches:
If you have any questions, we're happy to assist. Reply to this blog post or take your queries to our Support Chat.
Thank you for choosing Qlik,
Qlik Support
Update March 4th, 2026: added link to How to get Talend Management Console task schedules and pause and resume during a maintenance window using the API article
Updated April 24th, 2026: added impact on APIs (all down) and additional clarification on why tasks must be stopped and the impact on remote engines
Updated May 7th, 2026: added additional information on how to address Remote Engine impact
Updated May 12th, 2026: the anticipated impact for the remaining maintenance window has increased from 30 minutes to 90 minutes
Talend Cloud and Talend Management Console will undergo scheduled maintenance in March, April, and May. This infrastructure modernization is a key step in unifying the Talend ecosystem with Qlik.
The alignment paves the way for a more seamless experience across both platforms. Over the coming months, you will gain access to integrated features that bridge data integration and analytics, enabling unified governance and a streamlined management experience across your entire data lifecycle.
The maintenance windows will occur per region, during off-peak hours, and are expected to have a maximum of 90 minutes of effective downtime.
A full outage of Talend Cloud and Talend Management Console for a duration of up to 90 minutes within a preplanned 4-hour window.
The following applications will not be accessible:
All APIs for Talend Cloud will not be available during the outage. APIs impacted:
In detail:
Looking for information on how to identify, pause, and resume your tasks? See How to get Talend Management Console task schedules and pause and resume during a maintenance window using the API.
In some instances, Remote Engines might require a restart if marked as unavailable in the Talend Management Console or if tasks cannot be executed as expected.
If restarting the Remote Engine does not resolve the complication, follow the pairing instructions in Pairing Remote Engines using a dedicated web service to reset the key and re-pair the Remote Engine.
If your Remote Engine Gen2 is unavailable or cannot execute tasks, then:
Each region will undergo maintenance for 4 hours during off-peak hours, with a maximum of 90 minutes of effective downtime.
| Region | Maintenance Start | Maintenance End |
| Talend Cloud - AWS - Asia Pacific (Sydney) au.cloud.talend.com |
UTC: 25/03/26 - 11:00 |
UTC: 25/03/26 - 15:00 |
| Talend Cloud - AWS - Asia Pacific (Tokyo) ap.cloud.talend.com |
UTC: 20/04/26 - 13:00 |
UTC: 20/04/26 - 17:00 |
| Talend Cloud - AWS - US East (N. Virginia) us.cloud.talend.com |
UTC: 27/04/26 - 6:00 |
UTC: 27/04/26 - 10:00 |
| Talend Cloud - AWS - Europe (Frankfurt) eu.cloud.talend.com |
UTC: 26/05/26 - 19:00 |
UTC: 26/05/26 - 23:00 |
To identify which region your tenant is affected by, cross-reference Accessing Talend Cloud applications.
To track further updates during the scheduled Qlik Cloud Maintenance, please visit our Qlik Cloud Status page. This blog post will be updated with additional information where necessary.
Thank you for choosing Qlik,
Qlik Support
Hello Qlik Cloud users and admins,
We’ve enhanced the Qlik Cloud Status page subscription experience to give you more control over the notifications you receive.
Previously, subscribing meant you received incident and maintenance notifications for all Qlik Cloud regions. With the updated Statuspage experience, you can now choose specific Qlik Cloud regions you want to follow.
This helps reduce unnecessary notifications in your inbox and puts the focus on the Qlik Cloud deployment regions you have active tenants in.
To subscribe:
To update your preferences:
For a full guide, see Qlik Cloud and Qlik Talend Cloud Status.
Thank you for choosing Qlik,
Qlik Support
Smarter Data, More Flexible Analytics, Better User Experiences
We’re excited to introduce the May 2026 release of Qlik Sense Enterprise on Windows (client-managed). This release delivers meaningful enhancements across data scripting, visualization flexibility, and user experience helping your teams move faster from data to insight while improving performance, governance, and usability.
Below is a breakdown of what’s new, why it matters, and how your teams can benefit.
Snowflake is rolling out stronger authentication requirements as part of their platform security initiative. Starting May 2026, new connections using only username and password will no longer be accepted, and all existing password-only connections will stop working between August and October 2026.
For the full rollout schedule, see Snowflake's authentication enforcement timeline.
If your Qlik Sense Cloud Analytics, Qlik Sense Enterprise on Windows, or QlikView environment connects to Snowflake, you will need to update those connections to use either key-pair authentication or OAuth before this change takes effect.
This applies to any Qlik Cloud Analytics, Qlik Sense Enterprise on Windows, and QlikView connection to Snowflake, where the authentication method is set to Username and Password only. Connections that already use key-pair authentication or OAuth do not need to change.
To check your connections, review the Data connections and look for any Snowflake connections using username and password authentication.
There are two supported authentication methods you can migrate to.
Key-pair authentication uses an RSA private/public key pair assigned to the Snowflake user account. It is the most straightforward migration path and does not require an identity provider. This option is recommended for most customers.
For setup steps, see Snowflake key-pair authentication documentation and the Qlik Snowflake connector guide.
OAuth integrates with your existing identity provider (such as Okta or Azure AD) and is well-suited for organisations that want centralised access control and token-based authentication. It requires an OAuth security integration to be configured in Snowflake.
See the Qlik Snowflake connector guide and Snowflake OAuth documentation.
OAuth support for Snowflake will be introduced to Qlik Sense Enterprise on Windows with our Q2 2026 release.
If you have any questions, we are, as always, happy to assist. Reply to this blog post or take your queries to our Support Chat.
Thank you for choosing Qlik,
Qlik Support
Hi everyone,
Want to stay a step ahead of important Qlik support issues? Then sign up for our monthly webinar series where you can get first-hand insights from Qlik experts.
Next Thursday, May 28 Qlik will host another Techspert Talks session and this time we are looking at Monitoring Qlik Cloud Capacity.
But wait, what is it exactly?
Techspert Talks is a free webinar held on a monthly basis, where you can hear directly from Qlik Techsperts on topics that are relevant to Customers and Partners today.
In this session we will cover:
Choose the webinar time that's best for you
The webinar is hosted using ON24 in English and will last 30 minutes plus time for Q&A.
Hope to see you there!!
Hello Qlik Users,
As announced previously (see Qlik Automate execution token changes), execution tokens will become header parameters on February 1st, 2026.
When triggering a triggered automation through the trigger URL (see the endpoint below), the execution token must be sent as a header parameter. Currently, it is possible to send the execution token as a query parameter. Starting February 1st, 2026, sending execution tokens as header parameters will be enforced.
api/v1/automations/{id}/actions/execute
Any Button objects using the built-in Run Automation feature are not affected by this change.
Don't hesitate to reach out if you have any questions or address our experts directly in the Qlik Automate forum.
Thank you for choosing Qlik,
Qlik Support
来たる 6/10(水)、「AI Reality Tour Tokyo 2026」を開催いたします。
本イベントでは、Qlik のエキスパートによる基調講演、Qlik ユーザーの先進的な事例、Qlik 技術部門による最新の製品情報、Qlik のパートナー企業による最新のソリューションや展示ブースなど、AI がもたらす価値と現実とのギャップを解消し、AI を実現・加速・適応する最先端のソリューションをご紹介します。
お申し込みの締め切りは、6月 2日(火)17:00 までです。お早めにお申し込みください。
【開催概要】
日時:2026年 6月 10日(水)13:00 - 18:30(受付開始 12:00)
懇親会 18:30 - 19:30
会場:有明セントラルタワーホール&カンファレンス
東京都江東区有明3-7-18 有明セントラルタワー3F・4F
参加費:無料
お問い合わせ:Marketingjp@qlik.com までお問い合わせください。

Well-known from Power BI, decomposition trees aren't available in Qlik natively. This extension fills that gap — letting users drill down across multiple dimensions in any order, with AI Splits automatically surfacing the highest and lowest impact factors on any measure.

A hands-on feature walkthrough: AI Splits, flex dimension ordering, multiple measures, conditional coloring, negative value handling, three bar scaling modes, zooming, and paging. Everything configured and ready to inspect in edit mode.

Qlik developers and BI consultants looking to add root cause analysis and ad hoc exploration to their Sense apps.

Built with AnyChart's Decomposition Tree extension for Qlik Sense / Qlik Cloud, based on fictional business data.
This year, in April, we inaugurated two new Centers of Excellence ( CoE) under the Qlik Academic Program, in the Silicon Valley of India, i.e Bangalore. The new CoEs mark a new beginning for training and skilling students in Qlik technologies along with other activities like datathons.
Reva University is one of the leading Universities in the State of Karnataka and is ranked among the top universities in the region. The School of Computer Science and Engineering took the lead in this initiative and has established the CoE. Strategic Partner of the Qlik Academic Program, ICT Academy established the connection with Reva and ensured that arrangements were made as per the requirements of the CoE.
The second CoE was established in Sai Vidya Institute of Technology ( SVIT) which is a well known institution for engineering students. Many students have earned their degree qualification from here. The Department of Computer Science Engineering have been coordinating to establish the CoE. Many initiatives are planned by SVIT to take this engagement ahead.
The previous CoEs are functioning successfully in VJIT Hyderabad, Anurag University Hyderabad and Kristu Jayanti University Bangalore. Many students have got trained and qualified from the CoEs here. Along with this, they have hosted various events including datathons successfully.
We hope to establish more CoEs this year and create a physical space for students to get trained under the Qlik Academic Program.
To learn more about the academic program, please visit: qlik.com/academicprogram
The following two Qlik Talend Administration Center security issues have been identified and subsequently resolved. Patches are already available.
A broken access control issue has been identified in Qlik Talend Administration Center, which allows a user with View permission to modify the Qlik Talend Studio update URL.
Affected Software
See Security fix for Qlik Talend Administration Center URL access control vulnerability (CVE-2026-9057) for details.
A stored cross-site scripting security issue in the Qlik Talend Administration Center has been identified.
Affected Software
See Security fix for Qlik Talend Administration Center cross-site scripting vulnerability (CVE-2026-9056) for details.
Upgrade at the earliest. The following table lists the patch versions addressing the vulnerabilities.
Always update to the latest version. Before you upgrade, check if a more recent release is available.
| Product | Patch | Release Date |
| Qlik Talend Administration Center URL access control vulnerability |
QTAC-1471 | November 21, 2025 |
| Qlik Talend Administration Center cross-site scripting vulnerability |
QTAC-1883 | January 23, 2026 |
Thank you for choosing Qlik,
Qlik Support
Qlik introduced a change in how automation permissions are handled for the Analytics Admin role.
The change is already live as of the 11th of May, 2026.
Analytics Admins can now claim ownership of another user's automation. After claiming ownership, they can make necessary changes to it and enable the automation. However, they can no longer transfer ownership to another user.
As an Analytics admin, to claim ownership of an automation:
This behavior change only applies to Analytics Admins. Tenant admins can still transfer ownership to any user with the appropriate access rights in the tenant.
If you have any questions, we're happy to assist. Reply to this blog post or take your queries to our Support Chat.
Thank you for choosing Qlik,
Qlik Support

We have been able to corroborate the model's accuracy using real data from the first ULEZ expansion, so we are confident it will predict the second expansion effects effectively.

This app and the ML experiment behind it has served as an internal demonstration of Qlik's machine learning capabilities, making its adoption easier.

Our internal data science team. It serves as a proof of concept for Qlik Predict.

An effective use case of machine learning in its prediction mode.
Most enterprise AI projects don’t fail because the model is wrong. They fail because the data isn’t ready. Data engineering leaders are now being asked to support a new wave of generative and agentic workloads that demand fresher data, broader source coverage, tighter governance, and richer context than traditional BI ever required — and to deliver it without growing the team.
Qlik Talend Cloud Data Integration was built to close that gap. It provides a single, governed pipeline from operational sources to an open lakehouse — and on to the vector indexes, feature stores, and APIs that your AI systems actually consume. Combined with Qlik Open Lakehouse on Apache Iceberg, it turns your AI inputs into reusable AI data products: named, versioned, governed assets that any RAG application or agent can consume off the shelf.
This post walks through the reference architecture, the pipeline that produces those data products, and a worked example that takes raw CRM and product data all the way to a working RAG copilot and an agentic workflow — both running off the same Iceberg foundation.