Edited: 5th of December 2025, added'What action do I need to take' Hello Qlik Alerting Admins, With the release of Qlik Alerting November 2025, the capability to Force HTTP onlywill be fully removed. Why is Force HTTPbeingremoved? The change is motivated by two key reasons: It aligns Qlik Alerting with modern web security practices The configuration, while previously documented, was not functional for some time due to the upgrade-insecure-requests Content Security Policy What action do I need to take? With the deprecation of HTTP config, administrators need to take additional action upon installing the new release. SeeQlik Alerting - Qlik Sense extension | help.qlik.comfor details, specifically step 5: ForSession cookie isolation, selectCookie sharing. This setting allows cookie sharing withQlik Alerting, which is required for user validation. If you have any questions, we're happy to assist. Contact us using chat or reply in this thread. Thank you for choosing Qlik,Qlik Support ...View More

Hello Qlik Talend Cloud and Qlik Stitch admins, Oracle has announced that starting with the NetSuite 2026.1 release, SOAP web services will no longer be supported. You can read the official announcement inSOAP Web Services endpoint release and support policy changes (community.oracle.com). To ensure a smooth transition and prevent any disruption to your data workflows, Qlik is actively developing a new NetSuite connector that leverages the REST API forQlik Talend CloudandQlik Stitch. As we move closer to the release, Qlik will keep you informed of: The targeted launch date of the new REST connector A recommended migration plan to help you prepare Details on the deprecation timeline for our existing SOAP-based connector We’re committed to making this transition seamless and will provide all necessary guidance to support your migration. Thank you for choosing Qlik,Qlik Support ...View More

Hello Qlik Users, In mid-July 2025, a vulnerability was disclosed in the NPM library form-data (GitHub Security Advisory). Qlik became aware of this issue through its standard Secure Development Lifecycle (SDL) processes. Following an internal review, Qlik R&D and Security teams identified that potentially vulnerable versions of the form-data library were included in some installations of Qlik Sense Enterprise for Windows. However, due to the specific way Qlik utilizes this library, the conditions required for exploitation are not met. Although the vulnerability was determined to be non-exploitable within Qlik Sense, customers who prefer to upgrade to a version that includes the patched form-data library can do so by installing one of the following releases: May 2025 Patch 6 November 2024 Patch 18 May 2024 Patch 24 Note: An earlier version of this information was mistakenly published indicating that this CVE was directly related to Qlik Sense for Windows. Thank you for choosing Qlik,Qlik Global 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. SEE THE RECORDING HERE ...View More

As HubSpot plans tosunset the v1 contact lists APIonSeptember 30,2025, any API requests using this version forcontacts or listsendpoints will begin to fail after that date. To ensure continuity, Qlik has released a new version,v4,of the connector. The changes in questions are: Schema change, primary key, replication key change forcontactsstream Schema change forcontact_listsstream What action do I need to take? Upgrade to the new version. There are two ways to upgrade. Upgrade and change the schema name If you do not mind changing the schema name, you can do so by simply creating a newHubSpot integration and deleting the old one. This is the recommended method. Creating a new integration with a different schema name means you will also benefit from a free historical re-sync of your data. Upgrade using the same destination schema If you prefer to reuse the same destination schema name: Pause the existing integration from their Stitch account. Wait for any records that arebeing preparedfor loading to be loaded. Take note of the tables and fields tracked for replication, as well as the replication methods defined for these tables. Delete the existing integration from your Stitch account. Drop the schema from your destination data warehouse(or rename it if you'd like to continue working from this data as Stitch completes a new historical replication). Contact Qlik Stitch Support to coordinate a manual row-usage exemption for this connection. Configure a new integration with the same name, and Stitch will create this schema in your destination during the loading process. If you have any questions, we're happy to assist. Contact us using chat or ask similar queries in theQlik Stitch forum.   Thank you for choosing Qlik,Qlik Support ...View More

Salesforce recently identified a security incident involving the Drift app (published by Salesloft). For additional details, see Security Advisory: Unusual Activity in a Third Party Connected App | status.salesforce.com. Are Qlik customers affected by the security vulnerability? Qlik does not use the Salesloft Drift application. Although Qlik uses the Salesloft platform, Salesloft has stated there is no evidence of any unusual or malicious activity with the Salesloft platform. Is Qlik monitoring the situation? Yes. We are monitoring the situation closely, where the privacy and security of your data are our highest priority. To stay up to date, review the Salesforce Informational Message ID 20000217: Security Advisory: Unusual Activity in a Third Party Connected App | status.salesforce.com. 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. Our most recent Techspert Talks session wasQlik Cloud Admin 201. 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: Troubleshooting entitlement allocation Exploring Capacity Consumption Leveraging Qlik APIs for User Management Watch the recording! ...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. Our Qlik expertsheld a Qlik Cloud Migration live Q&A with Qlik webinar, answering all your questions about migration from on-prem to Qlik Cloud and using the tools that are available to make the process easier. WATCH RECORDING HERE ...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. The Techspert Talks from August look at Migrating to Qlik Cloud Analytics. 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 covered: Demonstration of the Qlik Cloud Analytics Migration tool Advantages of Qlik Cloud SaaS Readiness Click on this link watch ...View More

Hello Qlik Automate administrators and users, Based on feedback, Qlik has changed the wayerrors are handledin theQlik Reportingconnector forQlik Automate. The change was rolled out onAugust 12th,2025. The following blocks will be replaced to facilitate the changes: Get Chart Image Get Pixel Perfect Report Get Tabular Report The functional change of the new blocks centers on error handling. While the old blocks output a simplefailedstring in case of an error, we wanted to update this output to include the full error object, including the status code and reason. Additionally, in certain situations, the old blocks would have a successful run even though the output is an error; we updated this behavior so the new blocks will error out in any situation involving an error. What does this mean for me? The old blocks were renamed, flagging them as deprecated. Example: Get Chart Image (deprecated) The new blocks retain the old names and are referenced in the description of the old blocks. The action needed by Qlik Automate administrators and users is to switch from the (deprecated)blocks to the new ones. If you have any questions, we're happy to assist. Reply to this blog post or take similar queries to theQlik Application Automation forum.   Thank you for choosing Qlik,Qlik Support ...View More