BeginningJanuary 2027, theQlik Cloudand Direct Access Gateway(DAG)ODBC Connectors willno longer support connections secured with TLS 1.0 or TLS 1.1. To maintain uninterrupted connectivity, customers should upgrade their environments to use TLS 1.2 or later in advance. For the relevant announcement and dates regarding Qlik Sense Enterprise on Windows, see ODBC Connector for Qlik Sense Enterprise on Windows: Upcoming End of Support for TLS 1.0 and TLS 1.1 in 2026. Why will this change take effect? InQlik Cloud, the change takes effect immediately on the 20th of January, 2027. Direct Access Gateway will include the change with its upcoming1.8.4 release, meaning it will not be affected until an upgrade is performed. Refer to the release notesandWhat's New upon release for details. Why is this happening? TLS 1.0 and TLS 1.1 are legacy encryption protocols that are no longer considered secure and have been deprecated across the industry for several years. Removing support for these older protocols in the ODBC connector aligns Qlik's connectivity stack with current security standards and reduces exposure to known vulnerabilities in outdated TLS implementations. Who is affected? This change affects the ODBC connector in Qlik Cloud and Direct Access Gateway only. Customers using Qlik Sense Enterprise on Windows should instead refer to the separate announcement covering that change. Any data source connection made through the ODBC connector in Qlik Cloud or Direct Access Gateway that relies on TLS 1.0 or TLS 1.1 will be affected once support is removed, regardless of whether the TLS version is enforced by the data source itself, a network intermediary, or the client driver configuration. What does this mean for me? If your data source, ODBC driver, or the underlying operating system is currently configured to negotiate connections using only TLS 1.0 or TLS 1.1, those connections will fail once this change takes effect. Reload tasks, extensions, and any other workflows using affected ODBC connections will no longer be able to connect to the data source. This will impact you onJanuary 20, 2027 for Qlik Cloud, or following your Direct Access Gateway update to release 1.8.4. What should I do? Review and upgrade your environment so that all ODBC connections negotiate TLS 1.2 or greater before January 20, 2027 (Qlik Cloud) or before upgrading to Direct Access Gateway release 1.8.4. If you are not already using TLS 1.2 or later, recreate the connection with the updated TLS configuration. Questions? If you have questions or need assistance planning your upgrade, our forums are open to you, and Support is only a chat away. Thank you for choosing Qlik,Qlik Support ...View More

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, October 15 Qlik will host another Techspert Talks session and this time we are looking at AI Best Practices with Qlik Cloud. 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: Data preparation for AI Understanding prompts Tips for improving performance 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!! ...View More

Qlik is updating the S3 connector (V1). As part of this update, the Creation_Date column in the ListBuckets table is being renamed to CreationDate. SeeAmazon S3 | Qlik Web Storage Provider Connectorsfor general information about the connector and its availability. This is a breaking change: any load script or data model that references the old Creation_Date column name against the ListBuckets table will fail on reload once the change takes effect. What products are affected and when? Qlik Cloud will receive the change between the 12th and 16th of October We have reviewed usage across our tenants and have not identified any customers currently using this column. No impact is expected. Qlik Sense Enterprise on Windows (client-managed) will see the change implemented in the upcoming November 2026 release Qlik Web Connectors(Qlik Web Connectors | help.qlik.com) will see the change implemented in the upcoming November 2026 release What action do I need to take? If a reload of the ListBuckets table fails after this update, update your load script to reference CreationDate instead of Creation_Date. This is the only change required to restore functionality. No other columns or tables in the S3 connector (V1) are affected. Simply update the column name in your script and reload again. A note for Qlik Cloud users: As rollout timing can vary, there is no action you can take in advance since the change cannot be pre-empted or scheduled around. What happens if I don't act? If your script references Creation_Datein theListBucketstable, that reload will fail once the change takes effect or after you upgradeQlik Sense Enterprise on Windows and/or the Web Connector package. 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 ...View More

The Oracle Essbase for Qlik Sense Enterprise on Windows (client-managed) connector will reach end of life and is therefore no longer recommended for use. When will the connector reach end of life? The Essbase Connector will reach end of life beginning with the Qlik Sense Enterprise on WindowsMay 2027 release and will no longer be included in the installation package. Earlier Qlik Sense Enterprise on Windows releases that still include the Oracle Essbase connector are unaffected by this change and continue to be supported according to their normal lifecycle. What does that mean for me? Applications and data connections using the Oracle Essbase connector will stop working once an environment is upgraded to the Qlik Sense Enterprise on Windows May 2027 release. As a workaround, Qlik Sense Enterprise on Windows supports connecting to systems that offer a REST API using the Qlik generic REST connector. Essbase exposes a REST interface that can be used as an alternative way to bring the same data into your applications. We're happy to assist with any follow-up questions. Reply to this blog post or take your queries to our Support Chat. Thank you for choosing Qlik,Qlik Support ...View More

Internet Explorer (IE) was retired by Microsoft in 2022 and no longer receives security updates. In line with this, Qlik will stop shipping the QlikView IE plugin starting with the QlikView September 2027 release. What this means for you: This announcement only impacts QlikView. No other Qlik products are affected If you remain on your current QlikView installation (such as the QlikView September 2026 release or earlier) and do not upgrade, nothing changes for you; the plugin remains operational Once you upgrade to the QlikView September 2027 release or any later releases, the QlikView IE plugin will no longer be included in your installation package, nor will any support be provided to enable older versions of the plugin While you may choose not to move to the QlikView September 2027 upgrade and remain on an older version, your eligibility for maintenance and support may be impacted. Qlik supports versions for 24 months from the initial release date in accordance with its release management policy. How can you access QlikView without the IE Plugin: The standard QlikView Web Clientworks in any modern web browser and requires no plugin. If you're already using the Web Client, which most customers are, this change has no impact on you. QlikView Desktop provides a direct connection to QlikView Server and will continue to work as normal. What you need to do: You are encouraged to stay on a supported version and explore one of the options below, if you are impacted: Check whether any of your users still rely on the IE plugin, rather than the Web Client or Desktop options. If so, move them to the Web Client (recommended for most cases) or set up a direct QlikView Desktop-to-Server connection before upgrading to the QlikView September 2027 release or later. Contact your account team or Qlik Support if you need help identifying affected usage or planning the move. Thank you for choosing Qlik,Qlik Support ...View More

The Region Mover, available with the Qlik Talend Cloud Migration Toolkit (QTCMT), enables users to migrate a Talend Cloud (TC) or Qlik Talend Cloud (QTC) tenant to another Qlik Talend Cloud tenant while either remaining on Talend 7 or upgrading to Talend 8. Before starting a migration, users can view the source tenant inventory directly in the Qlik Talend Cloud Migration Toolkit. This provides visibility into the currently existing assets and those available for migration. The migration is organized into three steps: Administrative assets: Users, groups, projects, and user/group authorizations Talend projects: Package and push artifacts, upgrade code to Talend 8, generate CVE reports, and upload artifacts to Nexus 3 or JFrog Artifactory Runtime assets: Tasks, task artifacts, task parameters, task triggers, and plans For questions or assistance, please contact Qlik Support. Why Use Region Mover? There are several scenarios where customers may need to move assets to a different region, including: A current region is no longer supported A move from Talend Cloud to Qlik Talend Cloud is required A newly available region was not previously an option and is now available Assets need to be consolidated from one tenant into an existing tenant Region Moverenables faster migration, migrating assets to a new tenant more than 20x faster than performing the same migration manually, and significantlysimplifies each migration step while giving you full control over exactly which assets get migrated. Migration options include: Selecting specific assets for migration Choosing whether tasks should start automatically or remain paused by default Upgrading existing Talend 7 artifacts to Talend 8 using the included sandbox environment Prerequisites and how to get started For all requirements, setup instructions, and details, seeRegion Mover | Qlik Talend Cloud Migration Toolkit Documentation Qlik Talend Cloud Migration ToolkitR2026-08 or later is required Download Download the latest release from the Migration Center page on Qlik Help. Thank you for choosing Qlik,Qlik Support ...View More

When we introduced enhanced self-service scheduling in April 2025, we removed the When data is refreshed option, which had let reload schedules trigger automatically when a dependent dataset was updated. At the time, we weren't able to carry that capability forward into the new task-based scheduler right away. That capability is now returning. See What's New in Qlik Cloudand Scheduling data refreshes with tasks. In the task editor, under Based on > Event, you can now select When data is refreshed to trigger a task automatically when a data update is detected in an upstream Qlik Talend Data Integration project that loads data into an analytics application. The option is only available if the application is connected to a Qlik Talend Data Integration pipeline. This brings back the event-driven automation the old scheduler offered, now built natively into the new self-service scheduling framework, with full compatibility with the multi-task model. What does this mean for me? If the application has an existing When data is refreshed schedule, this button might instead say Migrate. For applications with these schedules, clicking Migrate or Save will migrate all associated schedules to be individual tasks attached to the application. No other action is required. We're happy to assist with any follow-up questions. Reply to this blog post or take your queries to our Support Chat. Thank you for choosing Qlik,Qlik Support ...View More

Our recently launched Public Previews give you early, hands-on access to what's coming next in Qlik Cloud, before the previewed features are generally available. Try new capabilities, shape their direction with your feedback, and stay ahead of the latest features. Public Previews are enabled by default for most users and are directly accessible from your profile: A tenant admin needs to activate the feature preview program. Read all about it in Introducing feature previews (Innovation Blog). The Highlights Shape the roadmap: Share your feedback directly in the product and inform how Qlik Cloud evolves. Stay up to date:Join Public Previewson Qlik Community, where our product team will advertise the available preview features. You control your experience:Turn your personal preview experience on or off at any time - and as a tenant admin, manage who has access to the previews through a custom role. Ready to know more? Getting started is quick and easy. Here is all you need: Public Previews | Qlik Community Introducing feature previews Managing feature preview for your tenant What's New | Qlik Help Thank you for choosing Qlik,Qlik Support ...View More

Effective in the Qlik Sense Enterprise on Windows November 2026 release, and in the latest patches for May 2025, November 2025, and May 2026, the ODBC connector used by Qlik Sense Enterprise on Windows will no longer support connections secured with TLS 1.0 or TLS 1.1. To maintain uninterrupted connectivity, customers should upgrade their environments to use TLS 1.2 or higher ahead of applying these releases or patches. The changes are expected afterOctober 28th, 2026and will be communicated in the respectiverelease notes. Why is this happening? TLS 1.0 and TLS 1.1 are legacy encryption protocols that are no longer considered secure and have been deprecated across the industry for several years. Removing support for these older protocols in the ODBC connector aligns Qlik's connectivity stack with current security standards and reduces exposure to known vulnerabilities in outdated TLS implementations. Who is affected? This change affects the ODBC connector in Qlik Sense Enterprise on Windows only. At this point, Qlik Sense Desktop and QlikView are not affected by this change. The standalone ODBC Connector (QvOdbcConnectorPackage.exe) remains unaffected for the time being. Any data source connection made through the ODBC connector in Qlik Sense Enterprise on Windows that relies on TLS 1.0 or TLS 1.1 will be affected once support is removed, regardless of whether the TLS version is enforced by the data source itself, a network intermediary, or the client driver configuration. What does this mean for me? If your data source, ODBC driver, or the underlying operating system is currently configured to negotiate connections using only TLS 1.0 or TLS 1.1, those connections will fail once you move to a version of Qlik Sense Enterprise on Windows that removes TLS 1.0 or TLS 1.1 support. Reload tasks, extensions, and any other workflows using affected ODBC connections will no longer be able to connect to the data source. What should I do? Review and upgrade your environment so that all ODBC connections negotiate TLS 1.2 or greaterbeforeyou upgrade Qlik Sense Enterprise on Windows. If you are not already using TLS 1.2 or later, recreate the connection with the updated TLS configuration. Questions? If you have questions or need assistance planning your upgrade, our forums are open to you, and Support is only a chat away. Thank you for choosing Qlik,Qlik Support ...View More

Don't miss our previous Q&A with Qlik! Pull up a chair and chat with our panel of experts to help you get the most out of your Qlik experience. Let our Qlik experts offer creative solutions to your analytics demands and answer your visualization questions. WATCH HERE ...View More