February 22, 2024: What’s New in Qlik Cloud?

Simplified access to CDS Views and HANA Views

Access to Extractors, without the use of standalone network service

Usable with a SAP Runtime license

Does not require any separate Qlik SAP Connector license

No need for an SAP transport installation, particularly useful with an SAP managed cloud system

Up to 25% faster performance vs. Qlik’s existing SAP connectors

Basic Authorization

Amazon Lambda

Amazon Redshift

Amazon S3

Azure OpenAI

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.

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