Hello Qlik Cloud admins, The event payloads emitted by the Qlik Cloud webhooks service are changing. Qlik is replacing alegacyevent format with a newcloudevent format. Anylegacyevents (such as anything not already cloud event compliant) will be updated to atemporaryhybrid eventcontaining bothlegacyandcloudevent payloads. When will these changes take place? This will starton or after November 3, 2025. At least six months after a formal deprecation notice, the legacy fields will be removed, leaving fully cloud events only. The formal deprecation notice will be provided through the Qlik Developer changelog. What action do I need to take? Consider updating your integrations to use the new fields once added. Where can I learn more? You can read more about the change in Qlik Cloud Webhooks: Migration to new event formats is coming, where we go into detail on: What events are impacted by this migration How events are changing 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

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 30th Qlik will host another Techspert Talks session and this time we are looking at Enhancing Analytics with Qlik Predict. 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: How ML Experiments work Real World Predictive use cases New capabilities 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

Hello Qlik Cloud admins and users, An upcoming update to Qlik Cloud will change the default filenames generated during an ad hoc download of a chart (such as Data, Image, or PDF). Currently, the filename defaults to Qlik Sense - <object name> - <date> Example:downloading from an object titled Investment Mix, the filename is Qlik Sense - Investment Mix - October 1, 2025 After the change has gone into effect, the default is<object name> - <date> Example: downloading the identical file as above will now generate the nameInvestment Mix - October 1, 2025 When will this change be deployed? This change will be deployed in two weeks following this post.The expected release is at or around October 27th, 2025. Why is this change being made? This change is being made to support customers in extending the platform to all enterprise use cases, whether interactive, embedded, or API integrated. Thank you for choosing Qlik,Qlik Support ...View More

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 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

Description of the Issue We have identified a degradation in the event auditing functionality in NPrinting, tracked in QCB-32819. Specifically, audit events are not being tracked after a fresh installation of the following versions: February 2025 SR2 February 2024 SR6 It is important to note that this issue only occurs with new installations of these versions. If the system is upgraded from a previous version, the problem does not manifest. Effects Observed Audit events are not being tracked. The following API endpoints fail with the error: api/v1/audit/logs api/v1/audit/events 500 Internal Server Error : An unhandled exception occurred; check the log for more information. The log file located at %ProgramData%\NPrinting\Logs\nprinting_audit.log shows this error message: Unable to start Audit service. ERROR: System.AggregateException: One or more errors occurred. ---> System.InvalidOperationException: Could not export the testing database. ---> Npgsql.PostgresException: 42501: permission denied for schema public Workaround In addition to performing an upgrade from a previous version instead of a fresh installation, the following steps can be taken to work around the issue: 1. Stop all NPrinting Server services except QlikNPrintingRepoService (otherwise PGAdmin will not find the connection to the DB). 2. Download and install PGAdmin, and connect to the NPrinting Server database. 3. Navigate to the nprinting_audit database and execute the following command: GRANT ALL PRIVILEGES ON SCHEMA public TO nprinting_audit; 4. Run the following command as administrator: net start QlikNPrintingAuditService /setup 5. Start all NPrinting server services. This will allow the audit service to start correctly and resume tracking audit events. ...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