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.
An update is being deployed to Qlik Cloud tenants starting May 28th (today), offering improved governance of the Qlik Analytics mobile app. See Setting permissions for the Qlik Analytics mobile app.
A new version of the Qlik Analytics mobile app is now available for download (in app stores). In addition, Tenant Administrators can now manage user access using three scopes:
In addition to access controls, these scopes strengthen the Microsoft Intune integration through a new server-side control for MAM deployment, replacing the previously user-controlled MAM toggle.
The update takes effect once users update to the latest version of the mobile app. For most existing users, there will be no impact, as the default scope is set to Allowed, a control point not available in the previous release.
The following two things need to be taken into consideration:
Some users may experience authentication issues after updating to the new version of the mobile app if this configuration is not completed by the Tenant Administrator.
Reference the configuration specifications for more information:
Thank you for choosing Qlik,
Qlik Support
Qlik is introducing changes to how custom themes in Qlik Analytics applications are handled, which may impact your CSS-styled themes if they include unsupported CSS modifications. This also applies to other means of modifying the CSS, such as the sheet input box, the Multi KPI CSS input, or any other 3rd party extension that allows CSS input.
These changes will impact both Qlik Cloud Analytics and Qlik Sense Enterprise on Windows.
For more information about custom themes, see Uploading and managing themes.
These changes improve how theming works in Qlik Analytics applications, which will enable us to deliver better-looking dashboards and generally enhanced theming.
We’re restructuring theme settings:
And we are adding new themes:
We’ve compiled a list of supported styling options for you that can already replace the need for custom CSS. See Obsolete CSS modifications.
Additionally, see the table below for an overview of the new theme properties that you can use in your theme instead of CSS. You will first need to enable the /feature/CLIENT_TLV_1804_LESS_CARDS flag to see them in effect in the application.
| Theme Option | Path in theme JSON | Example |
| Sheet background |
sheet.backgroundColor |
|
| Sheet margin |
sheet.margin |
|
| Object paddings |
object.padding |
|
| Borders |
|
|
|
object.borderColor |
|
|
|
|
|
|
| Shadows |
object.shadow.boxShadow |
|
|
object.shadow.boxShadowColor |
|
To give you more context: Document Object Model (DOM) selectors in custom CSS are not a supported pattern. While they can be helpful for customizing the look and feel of applications, the DOM is subject to change at any time. To provide your feedback, raise tickets on the Qlik Ideation portal when you need custom CSS customization. This helps prioritize supported customization options to add to the platform.
Do not use top-level selectors such as qv-client or qv-card. These selectors are planned for removal in future versions. See CSS best practices for Sense themes for more information.
Qlik Cloud will see the changes on or after June 1st, 2026, while Qlik Sense Enterprise on Windows will be aligned in the November 2026 release.
While we do not expect your themes to be affected, we recommend testing them at the earliest. See the How can I verify if my themes are affected? section.
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
Dear Qlik Customers,
In April 2026, SAP published a series of updates that will restrict your ability to extract certain SAP data using Qlik products. We are writing to explain what is changing, what it means for your Qlik integration, what you can do next, and how Qlik is responding.
SAP has recently updated SAP Note 3255746 and its API Policy, which together prevent customers from using the ODP-RFC interface to perform bulk data extractions to non-SAP systems. Here is what you need to know.
The CDC connectivity via ODP will be at most risk by the implementation of the June 9th SAP security update, as it will be blocked. The main products affected are:
Other impacted products that also offer ODP functionality are:
The following Qlik Products do not use the ODP-RFC interface and therefore will not be impacted by the June SAP Security update:
You should be in control of your business-critical data, wherever it creates value. Without interoperable architectures, SAP customers like you face higher costs, performance issues, and less freedom to choose, including loss of flexibility in implementing AI.
Qlik already supports alternatives to ODP and is actively developing additional migration paths and solutions to preserve your flexibility through this transition and beyond. We will continue to work on viable alternatives to our ODP endpoints and help you navigate this change on your terms, not SAP's. To learn more about how Qlik can support your specific environment, please reach out to your Qlik representative.
This communication reflects Qlik's current interpretation of SAP's restrictions, which are outside our control and subject to change. Customers should consult SAP's official communications and seek independent guidance on operational and legal impact. Roadmap statements are forward-looking and not commitments; disruptions arising from SAP's decisions do not constitute a defect in Qlik's products or services.
It was back in 2015 when I first published the original Qlik Sense Search Cheat Sheet. Since then, and thanks to lots of individual contributors here in the Community, the Search Cheat Sheet has suffered several transformations to make it more complete and truthful.
@afurtado wrote me an email a few weeks ago because he was interested in getting the document localized for the Brazilian folks out there. In addition to thank him for his contribution and sending him the file I decided that it was about the time to get the Search Cheat Sheet an update.
Today I want to introduce a new version of the document. I added the compound search section to it (@jayanttibhe thanks for the tip), and I redesigned and rationalized the position of each element for better comprehension.
As an extra, I made the document multilanguage ready. So, if someone wants to translate the Cheat Sheet to other language (currently available in English, Spanish and Portuguese) please let me know in the comments section and I'll gladly tell you how to help us.
Hope you like it, and please share it.
Arturo
Updates:
Feb 28: French version thanks to @arychener
Feb 25: Italian added thanks to @AntonioCostantino . Russian translation updated
Feb 13, 2020: Cheat sheet includes now the ^ Wildcard to be consistent with Qlik Help. Russian language added thanks to the contribution of @martynova
Jan 29, 2020: German language added thanks to the contribution of @g_mitschke
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 was introduced to Qlik Sense Enterprise on Windows with our May 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
As a follow-up to my previous blog post titled Finance Report with Waterfall Chart, I wanted to share an awesome demo that showcases financial reporting visualizations including a profit & loss statement with a waterfall chart. Qlik's Dennis Jaskowiak and Ekaterina Kovalenko, and partner Dawid Marciniak from HighCoordination, created the Financial Analysis demo based off of Jedox data, incorporating many enhancements to the straight table and pivot table. In addition to the waterfall chart, they use inline SVG to create lollipop charts and bar charts in financial statements.
Here is a look at some of the sheets:
The Dashboard provides a high-level overview of profit and loss, cash flow and liquidity. On this sheet, view the use of inline SVG bar charts and lollipop charts.
The P&L sheet provides a more detailed look at profit and loss.
The Cost Center sheet uses the pivot table to show sales costs.
Find a detailed look of cash flow on the Cash Flow sheet.
This is just some of the sheets you will find in the Financial Analysis demo. If you are looking for appealing ways to visual your financial data while keeping it concise and clean, download the Financial Analysis demo (QVF) here.
Thanks,
Jennell
Migrating a Talend Studio project to the cloud is no small undertaking, but we are here to help.
Brought to you by Savraj Rakkar, Benoit Barranco, and Sébastien Leduc.
The Qlik Talend Cloud Migration Toolkit (QTCMT) is a structured migration solution built for teams running Talend on-premises who are looking to move to Qlik Talend Cloud and upgrade their project code to Talend 8. Whether the destination is the cloud or an on-premises environment, the Qlik Talend Cloud Migration Toolkit provides a clear, automated path to get there.
The Qlik Talend Cloud Migration Toolkit also extends beyond Talend Administration Center (TAC), offering an inventory view of Qlik Enterprise Manager (QEM) and Stitch environments so teams can see their full data integration footprint in one place.
Moving to Qlik Talend Cloud means less time managing servers, upgrades, and infrastructure, and more time focused on actual work. New features ship monthly, so the platform improves continuously without any effort from the team. Data stays current across connected systems in real time, and the platform scales as needs grow. Teams also benefit from unlimited users and execution engines, backed by a generous initial capacity band.
The best first step is installing the Qlik Talend Cloud Migration Toolkit through the Qlik Help Migration Center and connecting it to an existing Talend Administration Center, Qlik Enterprise Manager, or Stitch environment to get an immediate picture of what is there. Full installation steps are available in the Qlik Talend Cloud Migration Toolkit documentation.
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
Qlik's O365 Add-in offering for report developers has expanded with two new add-ins to enable Word document and PowerPoint presentation analytic reports.
Report developers can now:
Qlik add-ins for Microsoft Office are installed using a manifest file. If you are using an existing manifest, you will need to download and deploy an updated file to access the new add-ins. See the deployment guide Deploying and installing Qlik add-ins for Microsoft Office.
The manifest covers all three productivity tool Add-ins. They cannot be deployed individually.
Qlik’s integration testing of Microsoft PowerPoint APIs shows that the O365 Add-in for PowerPoint can be unstable or slow at times. Our investigation with Microsoft reveals this to be a known challenge; some APIs on web vs desktop can result in different behaviors.
If your report developers have difficulty with the online PowerPoint Add-in, contact Qlik Support to open a case with us.
While we investigate the integration with Microsoft to determine if a solution is possible, consider developing your reports with the desktop version of PowerPoint.
Qlik NPrinting May 2026 Initial Release added support for exporting compatible Word and PowerPoint report templates in QDOCX and QPPTX formats for import into Qlik Cloud Reporting.
Please note that only single-connection templates can be exported.
See the Release Notes for details.
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
Qlik Automate's ServiceNow connector is moving from username and password authentication to OAuth 2.0. This change aligns with security best practices and ServiceNow's own recommendations for third-party integrations, eliminating the need to store credentials in plain text and providing more granular, revocable access control.
The change will go into effect on the 23rd of June, 2026.
Existing connections that use username and password authentication will need to be re-authenticated using OAuth 2.0. Complete the re-authentication steps as outlined in this blog post on the 23rd of June to prevent possible service interruptions.
ServiceNow provides guidance on each stage of the OAuth 2.0 setup. See the following for details:
To migrate your Qlik Automate connector, first prepare ServiceNow by configuring OAuth 2.0, then re-authenticate Qlik Automate on the 23rd of June.
Before you begin, make sure you have Admin access to your ServiceNow instance and Admin or Owner access to your Qlik Cloud tenant and the relevant Qlik Automate automation.
The OAuth 2.0 plugin must be available in your ServiceNow instance.
When prompted for a Redirect URL, use the callback URL provided by Qlik Automate during the connection setup. This URL must exactly match what is registered in ServiceNow.
This step can only be carried out after the change on the 23rd of June, 2026.
If you encounter issues during the migration, please contact Qlik Support or visit the Qlik Community for assistance. When raising a support case, include your ServiceNow instance domain and the error message you are seeing.
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.
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
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
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.
The Techspert Talks session from May looked 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: