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

Hello Qlik Automate users and admins, A series of changes have been identified across various GitLab APIs due to the deprecation of specific fields. For more information, seeREST API deprecations(docs.gitlab.com). As of the release of this post, GitLab has no official release date for API v5, and development has not yet started as of version 18.0. What will be changed? merged_by:In the Merge Request API, the merged_by field has been deprecated and replaced with merge_user. The following block response will be affected: List merge request Get merge request List updated merge request incrementally List new merge request incrementally merge_status:The merge_status field in the Merge Request API is deprecated and replaced with detailed_merge_status. The following block response will be affected: List merge request Get merge request Create merge request List updated merge request incrementally List new merge request incrementally default_branch_protection: The default_branch_protection field will be replaced with the default_branch_protection_defaults field. For more information, see default_branch_protection API field (docs.gitlab.com). The following block response will be affected: List groups Additional details on Response Changes Below you will find examples of responses with the deprecated (red) and new (green) fields. merged_by & merge_status fields [{"id": 1,"iid": 1,"project_id": 3,"title": "test1","description": "fixed login page css paddings","state": "merged","imported": false,"imported_from": "none","merged_by": {"id": --,"name": "--","username": "--","state": "active","avatar_url": "https://gitlab.example.com/--","web_url": "https://gitlab.com/--"},"merge_user": {"id": --,"name": "--","username": "--","state": "active","avatar_url": "https://gitlab.example.com/--","web_url": "https://gitlab.com/--"},"merged_at": "2018-09-07T11:16:17.520Z","merge_after": "2018-09-07T11:16:00.000Z","merge_when_pipeline_succeeds": true,"merge_status": "can_be_merged","detailed_merge_status": "not_open"}] default_branch_protection {"id": 96,"web_url": "https://gitlab.example.com/--","name": "test-1","path": "test-1","description": "","math_rendering_limits_enabled": true,"lock_math_rendering_limits_enabled": false,"default_branch": null,"default_branch_protection": 2,"default_branch_protection_defaults": {"allowed_to_push": [{"access_level": 40}],"allow_force_push": false,"allowed_to_merge": [{"access_level": 40}],"developer_can_initial_push": false},"avatar_url": null} What action do I need to take? All the above blocks referencing these deprecated fields in the other block should be updated with the new fields. If you have any questions, we're happy to assist. Reply to this blog post or take similar queries to the Qlik Application Automation forum.   Thank you for choosing Qlik, Qlik Support ...View More

Hello Qlik Users, The newStraight Tablewas moved into the new native section of charts from the visualization bundle. The new Straight Table offers many improvements from the old table, and we encourage everyone to start using the new table instead of the old one. We've put together an article that aims to answer any frequently asked questions around this switch, beginning with: The old table will not be removed anytime soon. It will continue to work until further notice. We encourage you to subscribe to theQlik Support BlogandWhat's Newin Qlik Cloudto stay ahead of updates. The old table will not be updated further. Use the new table to benefit from future improvements. We monitor your feedback and will improve the functionality of the new table. To read up on new features, as well as how to replace the old table, head over to The new Straight Table and old Table (retired) in Qlik Analytics. Questions? We're only a comment or a chat away. Thank you for choosing Qlik,Qlik Support ...View More

Don't miss our latest 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

Hello Qlik Talend admins, Qlik is updating the Qlik Talend Nexus repository. The changes will be rolled out in a phased approach. The first phase will be deployed onJuly 16th,2025, from 1 AM to 4 AM GMT. The second phase will be rolled out later this year, with information on when and the expected impact to be published closer to the date. No estimated time is available yet. What is the expected impact? The impact is minimal. Qlik Talend Studio: Versions 7.2 to 8.0: No impact Versions 6.0.0 to 7.1.1: JAR files may no longer automatically download from Nexus Qlik Talend Administration Center No impact For more information on how to handle missing JAR files, see Update to Qlik Talend Nexus repository: downloading and installing missing JARs. 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

Hello Qlik Automate admins and users, TheRun Conversational Task block in the Hugging Face connector has been deprecated and removed from Qlik Automate. Why was the block removed? The block was removed due to Model Unavailability. The API used no longer supports any available models for execution under the conversational task. How does this affect me? You will no longer see the Run Conversational Task block in the Hugging Face connector. What action is needed from me? Check Your Existing Workflows. Review any workflows and automations that include the Run Conversational Task block and remove the block from the automation to prevent an execution error.   If you have any questions, we're happy to assist. Reply to this blog post or take similar queries to the Qlik Application Automation forum.   Thank you for choosing Qlik, Qlik Support ...View More

The old versions 1.4.x and 1.5.x of Qlik Data Gateway - Direct Access will be officially End of Life by December 31st, 2025. Version 1.4 was released in June and July 2023 and reached End of Support on February 19, 2024. Version 1.5 was released in September 2023 and reached End of Support on June 12, 2024. How will this affect me? Both versions will stop working after reaching End of Life. We recommend you plan to upgrade to the latest available version of the currently supported 1.7.x as soon as possible. How do I upgrade? For the upgrade procedure, please refer to Upgrading Qlik Data Gateway - Direct Accesson Qlik's online help. This page also lists all the significant changes for each version. The upgrade to 1.7.x from 1.4 or 1.5 has been thoroughly tested, and the process is expected to be smooth. However, please follow the steps carefully and always take a backup before upgrading. It is also worth noting that .NET 8.x is required (from v1.6.6) and will be automatically installed during the upgrade. What else do I need to keep in mind? There are several configuration settings added in later versions of the Direct Access gateway that may be applicable for your deployment. Therefore, please review all details in the online help on Configuring and troubleshooting Qlik Data Gateway - Direct Access. Note that most Direct Access gateway settings can be configured in the Qlik Cloud Administration activity center (from v1.7.2). Always upgrade to the latest version! Version 1.6, which was initially released in December 2023, reached end-of-support on June 14, 2025, and is tentatively set for End-of-Life by end of June 2026. We will share an update later this year with the exact End-of-Life date for this version. Please note that you are always better off upgrading to the latest version available, especially as cloud-side fixes, which get deployed almost every week, most often does not apply to older gateway versions. If you have questions or need additional assistance, our forums are always 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. The Techspert Talks session from July looked at Data Pipelines and Transformations. 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 covered: Creating pipelines in Qlik Talend Cloud Data Integration Demonstrating transformation possibilities Preparing data for analytics Click on this link to see the presentation ...View More

Updated: Release Date added (26th June 2025) and note added regarding the error users will encounter if they update before the redirect URI is configured. Updated: Android Release Date added (16th July 2025) Hello Qlik admins, This post is intended for customers who use the Qlik Sense Client-Managed mobile app with Microsoft Intune policy management practices as described in Azure app registration for Qlik Sense Client-Managed Mobile. Qlik anticipates the release of the Qlik Sense Client-Managed Mobile app version 1.31.1 for iOS on June 26th. With this release comes an update to the integrated Microsoft Intune version to 20.5.0, which will also update the Microsoft authentication protocol in use. What action do I need to take? Many devices will automatically update the mobile app build in the background. To prepare for the update and to continue utilizing Microsoft Intune/Entra policy management of the Qlik Sense Client-Managed Mobile app, pre-configure the new redirect URI msauth.com.qlik.qliksense.mobile://auth in your Azure portal. If a client is updated and the redirect URI has not been configured, the end user will see the errorFailed to authenticate using OAuth.SeeQlik Sense Client Managed mobile app on iOS: Failed to authenticate using OAuthfor details. Log in to theAzure Portal, go toApp registrationsand viewAll applications Locate and open the Qlik Sense Mobile app registration In Manage,open theAuthenticationmenu, then scroll toMobile and desktop application Redirect URIs Click Add URI and addmsauth.com.qlik.qliksense.mobile://auth Click Save,refresh the page, and verify the new Redirect URI is recorded underiOS / macOSRedirectURIs Qlik supports only the current mobile app version in the app store. The end user migration to the new app is at the discretion of the customer; however, it is recommended all users upgrade immediately. It is possible for users to continue Intune governance control with old and new mobile app versions. Note that removing the old redirect URI (qliksense-intune://com.qlik.qliksense.mobile) for the mobile app versions before 1.31.1 will result in the old app no longer retrieving a policy from the Intune/Entra tenant. How do I set up the mobile client with Microsoft Azure and Intune? For instructions on how to set up the Qlik Sense Client-Managed Mobile client with Microsoft Azure and Intune, see Add an Azure app registration for Qlik Sense Client-Managed Mobile | help.qlik.com. These instructions will be updated on the initial release of Qlik Client Managed mobile version 1.31.1. What about the Android app? The Android version of the Client-Managed Mobile app has been updated on the 16th of July. Thank you for choosing Qlik,Qlik Support ...View More

Qlik Cloud Analytics launchedenhanced self-servicescheduling capabilities on April 14th, 2025. Details about the new self-service scheduling functionality can be found in Scheduling data refreshes with tasks. These new capabilities allow users to create multiple tasks to schedule refreshes of apps, scripts, and data flows. This replaces aself-service scheduling system offering one schedule per analytics asset. In addition, theWhen data is refreshedconfiguration option has been removed. This option enabled users to automatically run reload schedules when dependent datasets generated by Qlik Talend Data Integration projects were updated. Existing reload schedules (now organized as tasks) configured with the When data is refreshed option continue to function as they normally do. However, creating new tasks with this option or configuring it for existing tasks is not currently possible. You can read more about the original implementation of the new self-service scheduling functionality in What's New in Qlik Cloud: Self-Service Scheduling – Task Chaining & Multi-Task Support. Thank you for choosing Qlik,Qlik Support ...View More