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

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

Hello Qlik Automate admins and users, Previously, it was possible for Analytics Admin to move an existing automation connection to another user’s personal space. This behavior has been deprecated as personal spaces are meant to be private and exclusively managed by the space owner or Tenant Administrators. What does that mean for me? No action is required from your end. When will this change be implemented? The change was implemented today, on August 7th, 2025. If you have any questions, we're happy to assist. Reply to this blog post or take similar queries to theQlik Automate forum.   Thank you for choosing Qlik,Qlik Support ...View More

Hello Stitch Admins, Stitch has released a new version of itsGoogle Ads integration. With this release comes an update toGoogle Ads V2, which utilizes the latest Google Ads API (version 20). The previously used Google Ads API version 18 will be sunset by Google on August 20th, 2025. Once the API is sunset, integrations that interact with it will stop working. What do I need to do? Create a new integration to stay ahead of Google sunsetting version 18. We've put together a general guide to assist you. Using a new schema name If you are creating a new integration and don't plan on reusing the previous schema name, you can go ahead and make a new Google Ads integration. Selecting Google Ads from the integration options will default to the latest version, in this case, V2. The new integration will also benefit from the 7-day free historic sync. Re-using the schema name If you need to use the same schema name for the new integration, you must do the following: Pause the existing integration(s) in your Stitch account. Wait for any records that are being prepared to finish loading (such as waiting for Preparing to reflect 0 rows in the integration summary page). 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 or rename the existing schema from your destination data warehouse. We recommendrenaming the schema to preserve the data and maintain flexibility to adjust downstream workflows. Contact Qlik Support to coordinate a manual row-usage exemption for this integration. Configure a new integration with the same name, and Stitch will create this schema in your destination during the loading process. Frequently Asked Questions Q: Can I copy over my bookmarks to the new integration?A: Bookmarks cannot be covered over. When you create a new integration, every table will perform a full table replication from the start date set in the settings. Once the historic sync is complete, it will move to the selected replication method. There is no mechanism to manually set bookmarks, and individual integrations have no interaction with each other, even in upgrades. Q: What if I need more than 7 days to complete the historic sync?A: Reach out to Qlik Support for a manual exemption. Please explain why you need more time, and we will accommodate accordingly. Q: Will the data structure be the same in the new integration?A: We cannot guarantee the data structure is the same as it is determined by Google Ads API. If you are looking for field or table changes, please reference the Google Ads API comparison guides (Upgrade from v18 to v19 and Upgrade from v19 to v20). If you are missing data, reference Google's documentation to confirm it hasn't moved or been removed. In the event Google says data should exist, but it is not replicated, raise a ticket to Qlik Support to review and investigate. If you have any questions, we're happy to assist. Contact Support, reply to this blog post, or take similar queries to the Stitch forum. And if you want to stay up to date for Stitch-specific Support Updates, don't forget to subscribe!   Thank you for choosing Qlik,Qlik Support ...View More

Hello Qlik admins and developers, Previously, the Dropbox API used only long-lived access tokens. These long-lived access tokens have been deprecated since the fall of 2022, and only short-lived access tokens are created. Long-lived tokens remain usable for existing authentications. The Qlik Dropbox connectors have maintained the use of long-lived access tokens, and it is now time to deprecate these tokens and remove them. We aimto end support for long-lived tokens by October 31, 2025. What action do I need to take? Re-authenticate to avoid interruption. You will not have to take action for connection definitions created in Qlik products released from 2023 and onwards, and which were created or re-authenticated after 2022. This is applicable tothe following scenarios: Qlik Sense: Client Managed and Qlik Cloud Dropbox file location connector Dropbox Metadata connector Qlik Web Connector Standalone Qlik Dropbox Connector If you are using a long-lived access token in a Dropbox connection definition, you must follow the steps below to re-authenticate. This can be done proactively at any time, which will avoid the connections from breaking. What if I do not re-authenticate in time? Your connections will stop working once the long-lived access token expires. You can still re-authenticate in the same way at a later time; your connection will be repaired, and your reloads will work again. Is there some way for me to identify the connections? Unfortunately, there is no indication showing which type of token is used. However, if you are not sure when the connection was created or last re-authenticated, there is no harm in re-authenticating, regardless of whether it is necessary or not. How to re-authenticate in Qlik Sense: Client Managed and Qlik Cloud To re-authenticate the Dropbox connectors in Qlik Sense, update the connection within the Data load editor, then select Authenticate and follow the on-screen process to retrieve a new Authentication Code. Verify and Savethe connection when done. How to re-authenticate the Qlik Web Connector: Standalone Re-authenticate via the CanAuthenticate table by selecting to Clear the current Authentication Token, and then Authenticate to get a new Authentication Token. Save and Runwhen done. Additional recommendations While performing this review of your Dropbox connection definitions, it may also be an opportunity to remove any redundant connection definitions not in use. If you have any questions, we're happy to assist. Reply to this blog post or start a chat with us. Thank you for choosing Qlik,Qlik Support ...View More