January 30, 2024: What’s New in Qlik Cloud?

Copy and paste style

You now have a new menu choice for copying style settings from one chart to another. This quality of life improvement makes it easier to style and work with charts. Especially now when all charts has many more styling settings.

Applying custom styling to a visualization

Tabular Reports – Template change connection

The Qlik add-in for Microsoft Excel has been updated to support an action to change the template connection. The report templates produced from the Qlik add-in are linked via meta data to the Qlik Sense app they were authored against. This capability allows a template author to reconnect a template with a copy of an app or app/tenant combination. This will be useful for report developers authoring against App A and using the template against App B or moving/sharing app/template samples within a development community.

Changing the connected Qlik Sense app

AutoML Access Controls

Qlik Cloud now supports 2 new user roles to allow more control over which users can access AutoML.

• Automl Experiment Contributor – controls who can create and contribute to ML Experiments and deploy ML models.

• Automl Deployment Contributor – controls who can manage ML Deployments and predictions

Further UI controls are in place to allow read-only views of AutoML assets for those with view permissions in a space.

Who can work with Qlik AutoML

Export apps from Managed Spaces

Space Owner and users with the “Can Manage” role, can now export Qlik Cloud apps from Managed Spaces. These apps can only be exported without data.

This possibility allows you to re-establish a parent – child relation of your source and published apps, in case the source app was accidentally deleted.

Exporting apps from managed spaces

Exporting apps from Managed Spaces

Troubleshoot app objects as part of your app performance evaluation

The already existing and embedded capability to run a performance evaluation can now help you focus even better on individual app object results. The overview now separates the result in sections which makes it easy to understand what kind of information you should focus on.

App performance evaluation

Qlik Performance Evaluation Improvements

New Qlik Data Gateway – Direct Access version

Direct Access gateway 1.6.3 includes the following enhancements and bug fixes:

• Data loss prevention

  In previous versions, to prevent potential data loss, Direct Access gateway did not automatically reconnect to the data source during a reload. From this version, Direct Access gateway will now automatically reconnect to the data source as needed. To prevent data loss, the completed reload summary will be verified before reconnecting. If data loss is detected, the reload will fail.

• Timeout for reload sessions

  In rare scenarios, the reload session would stay alive indefinitely. To prevent such occurrences, this version introduces a three-hour timeout for reload sessions.

• Timeout extension for load requests

  Reloads would sometimes fail with the following errors:

  Connector error: The session does not exist (DirectAccess-1509)

  Connector error: The stream session expired for the load data request (DirectAccess-1012)

  To mitigate this issue, an EXTEND_FIRST_REQUEST_TIMEOUT parameter (for extending the load request timeout) was added to the configuration.properties file. The default is “0”. Customers who frequently encounter these errors should try setting the timeout to 5-10 minutes.

• Support for detailed connection error messages

  Added support for viewing detailed connection error messages when using ODBC-based via Direct Access gateway connectors. Customers can now set the ShowErrorDetailMessage parameter in the Advanced connector settings to “true” to see the full error returned by the ODBC driver. The detailed error message will be show in the Data load editor.

  The error message is provided in its entirety by the data source you are using. Qlik does not append any additional information to the error message or edit it in any way.

• Handling multiple reloads with the same reload ID

  From this version, the engine session ID will be used to distinguish between multiple reloads with the same reload ID. This will prevent potential conflicts, resulting in reloads failing with the following error:

  Connector error: data loading error (DirectAccess-4008

To benefit from the enhancements and resolved issues, customers are encouraged to upgrade at the earliest opportunity. For upgrade instructions, see Upgrading the Direct Access gateway installation.