Table of Contents
What's New
Learn about new features and improvements in Qlik Cloud.
Resolved Defects
The following Release Notes cover resolved defects for Qlik Cloud. Solved issues and limitations for Qlik Cloud Services are also listed.
QB-18819
|
Using the qualify and unqualify statement when having a "*" in combination with letters creates irregular behavior in the qualification of fields in the lineage graph generation.
|
Using the qualify and unqualify statement when having a "*" in combination with letters creates irregular behavior in the qualification of fields in the lineage graph generation. This appeared through the source of the edge linking to the default node 0. This is now fixed.
|
QB-19665
|
Qlik Engine: Impact analysis fails with "Internal Error"
|
Fixed a problem where lineage was not rendered due to a mismatch between the table and the field level in the lineage graph out from the Qlik Engine. This occurred when multiple stores to the same file are done with different sources. The issue was solved by using the last iteration of the stored nodes. With this, lineage graph generation confusion is reduced and there is no mismatch between levels.
|
QB-22841
|
Reporting: Sheet title font setting ignored
|
When exporting a sheet as a PDF, the title was not rendered correctly. This issue has now been solved and sheet title settings are observed.
|
QB-22062
|
Qlik Cloud: Wrong script version is used during data loading
|
The wrong version of the script was sometimes used If an app is reloaded shortly after the script is updated via API. This has been fixed by checking the server script version before loading the data in the Data Load Editor. If the script on the server is newer, the user will be notified and asked if they want to refresh and use the newest script.
|
QB-22658
|
Qlik Sense Reporting: Cannot display Chinese characters in sheet title of subscribed report
|
Chinese characters were not rendered properly in the sheet title of PDF report subscriptions. This fix adds the correct font in the title HTML fragment. Note: for the fix to work, the CollationLocale property in the app data load script should be set accordingly. In this case, 'zh-cn'.
|
QB-22781
|
Qlik Engine: DROP TABLE not freeing memory
|
Fixed a problem where the DROP TABLE command was not freeing memory by updating the request's memory usage information when the command is executed.
|
QB-21217
|
Direct Access gateway: Resolved debug failure in Data Load Editor (DLE)
|
When debugging the code in the Data Load Editor (DLE) with the Limit Results option enabled, the debug would fail with the following error: Connector error: Invalid load request (DirectAccess-1006)
|
QB-21238
|
Qlik Data Gateway - Direct Access: Vague error message when naming a Gateway
|
The Gateway name validation error message has been updated to be more accurate. It now states the specific characters that cannot be used in a name.
|
About Qlik
Qlik’s vision is a data-literate world, where everyone can use data and analytics to improve decision-making and solve their most challenging problems. A private SaaS company, Qlik offers an Active Intelligence platform, delivering end-to-end, real-time data integration and analytics cloud solutions to close the gaps between data, insights and action. By transforming data into Active Intelligence, businesses can drive better decisions, improve revenue and profitability, and optimize customer relationships. Qlik does business in more than 100 countries and serves over 50,000 customers around the world.
qlik.com