Table of Contents
This is Release notes for a Technical Review and are only available for a limit time. This release note will be archived when February 2023 is released.
Please refer to the What’s new sections of the online help for information about the new and updated features of the Qlik Sense Enterprise on Windows February 2023 release.
Key |
Title |
Description |
QB-10281 |
Visualizations: Chart sharing via link not working applying selections |
Fixed a problem that prevented applying filtered selections when opening an app via the chart-sharing link option. |
QB-10612 |
Qlik Sense Engine: MakeWeekDate function ignores system variables |
Fixed a problem where the script/chart function MakeWeekDate did not correctly respond to the values of the system variables (FirstWeekDay, BrokenWeek, and ReferenceDay). |
QB-14091 |
Qlik Sense Engine: Direct variable reference in expressions could cause incorrect field-on-the-fly generation |
Fixed a problem that allowed expressions with by-name variable reference for fields-on-the-fly, causing data model and result cache corruption, resulting in unpredictable crashes. These expressions are now ineligible for fields-on-the fly and instead, a regular ad hoc calculated dimension will be generated (as for any ineligible expression). Dollar-expansion using variables continues to work as before, as the variable is used to generate the expression, and does not form a part of the expression itself. |
QB-14264 |
Qlik Sense Mobile: Lost connection on iOS |
Fixed a problem where the connection was lost after minimizing the browser window and switching to other applications. |
QB-14302 |
Qlik Sense Engine: Lineage graph does not show full graph |
Lineage did not show files stored using LIB://path in uppercase. This has now been solved and Lineage supports using uppercased LIB://path. |
QB-14344 |
Qlik Sense Mobile: App thumbnail not responding to touch |
Users could not open an app by tapping on the center of the app thumbnail. Instead, users had to tap on the corners of the thumbnail to open the app. This has been fixed, and a tap on the thumbnail will open the app. |
QB-14348 |
Qlik Sense Engine: Mashup application hangs |
Fixed a problem where a mashup application would hang when applying selections. |
QB-14363 |
Qlik Sense: Unencrypted origin trusted by default |
Fixed a problem that allowed unencrypted HTTP origin header in Qlik Sense for HTTPS protocol requests. |
QB-14494 |
Qlik Sense Visualizations: Accidental chart deletion with open variables dialog in Edit sheet |
Fixed a problem where a chart could be accidentally deleted in the background if the variables dialog was open and the delete key was pressed. This was solved by blocking the grid while the variables dialog is open and unblocking once it is closed. |
QB-14649 |
Qlik Sense Engine: Problem with qualifiers in aggregations |
Fixed a problem where aggregation qualifiers (such as total and distinct) were not considering the outer set analysis prescribed by the expression. This has been solved, and all calculations with outer set analysis notation yield correct results. |
QB-14684 |
Visualizations: Combo chart tooltip displays "0" instead of "-" for missing values |
Fixed an issue where the combo chart tooltip in certain cases showed "0" instead of "-" for missing values. |
QB-14877 |
Qlik Sense Visualizations: A table in a Nebula sheet disappears when the page is refreshed |
The selection API from Nebula is sometimes not ready the first time the sn-table renders. A sanity check has been added to ensure the sn-table renders every time. |
QB-14890 |
Qlik Sense Visualizations: Overwrite option for ODAG app not working |
Fixed a problem where the "Overwrite generated apps" for ODAG did not work and triggered the warning message "Maximum number of generated apps reached". The overwrite option now works as expected and a newly generated app overwrites the existing ODAG app without a warning message. |
QB-14951 |
Qlik Sense Visualizations: Incorrect numerical abbreviation in Scatter Plot using "Auto" |
Fixed a problem where using "Auto" in the chart configuration for the x or y axis showed an incorrect format in Scatter Plot charts. |
QB-14960 |
Visualizations: sn-action-button extension now applies encoding to the URL in navigate to website action |
This encoding is safe and does not throw errors. It will properly encode the given URL, including replacing any raw, unpaired surrogate pairs with the Unicode replacement character prior to encoding. |
QB-15055 |
Qlik Sense Scheduler: Triggered tasks not running at expected scheduled time |
Fixed a problem where the scheduler services did not run properly if there were errors in the user-created cron expressions. We solved this by creating more controls and marking any problematic user entry in the scheduler error log file and ignoring that trigger until the user resolves the issue. |
QB-15075 |
Qlik Sense Visualizations: Error of reserved property 'FILTERS' |
Fixed a problem where an extension using the reserved property 'FILTERS' would fail to load. |
QB-15091 |
Qlik Sense Visualizations: Incorrect jQuery-ui version |
Fixed a problem that displayed an incorrect version of jQuery-ui. The correct version is 1.13.1. |
QB-16788 |
Visualizations: Custom tooltip measure in combo chart disappears when replacing the dimension |
Fixed a problem where the custom tooltip measure disappeared when the dimension in the combo chart was replaced. The custom tooltip measure now appears when hovering over the combo chart bars. |
QB-16816 |
Qlik Sense Visualizations: Action button background image not shown |
Fixed a problem where images on action buttons were not displayed correctly. The button now checks and works with multi-noded prefixes. |
QB-16853 |
Qlik Sense: Updated Node.js |
Updated Node.js to address a third-party issue (CVE-2022-43548). For more information, visit https://nodejs.org/en/blog/vulnerability/november-2022-security-releases/. |
QB-16883 |
Qlik Sense Visualizations: Map chart layer not rendering bars |
Fixed a problem where bars on the map representing low figures had a height of less than one pixel and would not be rendered. This has been solved by making the minimum height one pixel. |
QB-16898 |
ODBC Data sources: Timestamp data type fails to load |
Fixed a problem with ODBC data sources where the timestamp data type failed to load in some cases. |
QB-16918 |
Qlik Sense Engine: Lost data rows when importing delimited UTF-16 encoded files |
Fixed a problem that caused embedded NUL (binary 0) characters in delimited UTF-16 encoded files, such as CSV, to be ignored during import, resulting in an incomplete data set. |
QB-16950 |
Qlik Cloud, Qlik Cloud for Government (FedRAMP) and Qlik Sense Visualizations: Possible to delete script variables using API calls |
Fixed a problem where it was possible to delete variables using a WebSocket API call. Script variable can now only be removed by modifying the reload script and reloading the app. |
QB-16952 |
Qlik Cloud, Qlik Cloud for Government (FedRAMP) and Qlik Sense Visualizations: Possible to delete script variables through the client |
Fixed a problem where it was possible to delete variables through the variables table in the client. There is now no option to delete if a script created the variable. |
QB-16981 |
Qlik Sense: Default rule for Custom Banner Messages does not generate on upgrade |
Fixed a problem in the initial release of November 2022 (14.97) that caused the default security rule for Custom Banner Messages to only be generated during a fresh install. This has been solved and the security rules are now also generated during upgrades. |
QB-17006 |
Qlik Sense Visualizations: Dependent variable not modified in preview |
Fixed a problem where a dependent variable was not immediately changing after the variable it depended on was modified. |
QB-17018 |
Qlik Sense Engine: "Too many columns" error when loading qvx files |
Loading qvx files via webfile would sometimes fail due to a "too may columns" error. This was solved by changing how the metadata for qvx files is processed during the read. |
QB-17039 |
Qlik Sense: Signed License Key (SLK) error |
Fixed a problem that was caused by a lower than min date field in a License table in the November 2022 release, causing validation issues when trying to apply a new license. |
QB-17196 |
Qlik Cloud, Qlik Cloud for Government (FedRAMP) and Qlik Sense Visualizations: Possible to delete script variables through the client |
Fixed a problem where it was possible to delete variables through the variables table in the client. There is now no option to delete if a script created the variable. |
QB-17347 |
Qlik Sense Hub: Apps not shown under Favorites when using non-English language |
Fixed an issue where apps did not appear under Favorites unless you navigated back and forth. The issue occurred when using a non-English language in the Hub. The Favorites section is now refreshed for all languages when all app streams are loaded. |
QB-17421 |
Visualizations: Error message when trying to edit a variable |
Fixed a problem that prevented editing variables through the user interface. |
QB-17424 |
Qlik Sense Visualizations: Color by dimension shows grey coloring |
Fixed a problem where data points expanded by a SET expression were shown in grey when using color by dimension in a chart. |
QB-17480 |
Qlik Sense Analytics: Debug current statement is missing |
On Qlik Sense Enterprise for Windows, the debug statement was partly hidden or missing from the Data Load Editor. This has now been fixed. |
The following issues and limitations were identified at release time. The list is not comprehensive but lists all known major issues and limitations.
For information about the requirements for Qlik Sense, see System requirements for Qlik Sense in the online help.
https://community.qlik.com/t5/Downloads/tkb-p/Downloads
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.
Table of Contents
The following release notes cover the versions of Qlik Sense released in August 2021. Solved issues and limitations for Qlik Sense Enterprise on Cloud Services are also listed.
Please refer to the What’s new sections of the online help for information about the new and updated features of the Qlik Sense Enterprise on Windows August 2021 release:
What's new in Qlik Sense August 2021
What's new in Qlik Sense August 2021 (Developers)
August 2021 Patch 5
Upgrade from August 2021 Patch 4 or earlier to August 2021 Patch 5 or later
Following upgrade steps need to be followed when upgrading from August 2021 Patch 4 or earlier to August Patch 5 or later (see table below for detailed upgrade matrix)
Source track |
Destination track |
Upgrade steps |
May 2021 or previous |
August 2021 |
NO |
May 2021 or previous |
August 2021 patch 4 or earlier patch |
NO |
May 2021 or previous |
August 2021 patch 5 or later patch |
YES |
May 2021 or previous |
November 2021 GA or later track |
NO |
August 2021
Widget support is deprecated
Widget support is deprecated and removed in August 2021 release. More information can found in Qlik Community and Help page
August 2021 Patch 13
Key | Title | Description |
QB-10692 | Qlik Engine: Risk of corrupting the state of thread locks due to stalling engine | Resolved an issue where the engine was stalling when checking for changes to Settings.ini. |
QB-10051 | Qlik Sense Hub: Improper error handling for "api/hub/v1/apps/stream/" request | Fixed a problem that resulted in unnecessarily verbose error messages. |
QB-9797 | Task status is not updated for apps | Fixed an issue where the task status in 'App: associated items' was not updated. |
QB-9713 | Qlik Sense: Pivot table sometimes displays incorrect background color | Fixed an issue where the pivot table would sometimes display incorrect background color when scrolling up or down. |
August 2021 Patch 12
Key | Release Notes Title | Release Notes Description |
QB-8050 | Scheduler: Operations Monitor app does not show new reloads | Fixed a bug that altered the structure of the scheduler service logs, making them incompatible with the data load model of the Operations Monitor app. To inspect reload activity from the affected period, use the Reloads Monitor app. |
QB-9795 | Information disclosure of internal FQDN and ports | In cases where a URL was not found, a 404 HTTP error was returned along with the details of the internal URL to be used. This issue has been fixed by removing the internal URL details from the returned payload and providing a generic "Content not found." message. |
August 2021 Patch 11
Key | Release Notes Title | Release Notes Description |
QB-10171 | Reload script is executed successfully but app save fails |
Added a retry mechanism where a locked transaction file would cause Engine to fail when saving the app.
|
QB-10174 | Issue with notification setup when several websockets have opened the same app | When several websockets open the same app event, registration of notifications like publish and unpublish is set up and torn down appropriately. |
IM-131 | Add retry of CopyFileCollection when performing DoSave |
Improvement for environmental issue when DoSave might fail.
|
August 2021 Patch 10
Key | Release Notes Title | Release Notes Description |
QB-9570 | Qlik Sense: Improve error messages for script save failures | The following improvements have been done: - The timestamp for saved changes is more visible. - A dialog makes it clear if the script saving failed. |
QB-9485 | Incorrect layout of Multi KPI objects in Qlik Sense | Fixed the layout of the objects in the KPI. |
QB-7782 | Host header not validated when Qlik Sense hostname is added in 'Host allow list' in virtual proxy settings | Improved the HTTP Host header validation method for permitted domains as per 'Host allow list' performed by Qlik Virtual Proxy. |
August 2021 Patch 9
Key | Release Notes Title | Release Notes Description |
QB-8873 | Forms Authentication with FQDN creates new user | When a user authenticated to Qlik Sense with Forms Authentication and FQDN as user directory, it was recognized as a different user, compared to when using a simple domain name. This has been fixed by using user impersonation, which prevents the creation of a new user. |
QB-6867 | Resolved timing issue that could lead to user enumeration | When using Windows NTLM as the authentication provider, the error response time for a invalid username was measurably different to that of a valid username. This could be used to allow somebody with access to the system to determine whether a given username was valid. The response times are now the same. |
QB-9228 | App is not showing in Insight Advisor chat | For apps with large data models, scraping calls might take a long time to complete. Fixed the issue by making the scraping timeout of the nl-app-search HTTP request configurable. The default value for the timeout (two minutes) can now be increased by setting the scraping-request-timeout parameter in the service configuration. |
QB-8218 | Smart search doesn't work when used in session apps | Resolved an issue where smart search did not work in session apps or in a mashup. |
QB-8992 | Use safe ciphers by default | Fixed an issue with unsafe ciphers. The unsafe ciphers have been removed and a list list of supported predefined ciphers is used. If you want to use the unsafe ciphers, you need to provide a list of them as mentioned in this knowledge article: https://help.qlik.com/en-US/nprinting/May2021/Content/NPrinting/DeployingQVNprinting/TLS-cipher-suites.htm, under the `--cipher-suites` param |
QB-7903 | ODAG indication green light not consistent | In case of having multiple ODAG links in an app there could be times when the constraints check (green light indicator) would use an expression from a different ODAG link. It will now use the correct expression. |
QB-7225 | Insight Advisor Chat was not working with database security | Insight Advisor Chat was not working with SSL/TLS Postgres Connection configuration. |
August 2021 Patch 8
Key | Release Notes Title | Release Notes Description |
QB-8695 | Teradata SSO username format is now configurable | Now users can make the Teradata SSO username format configurable by editing the SSOUsernameFormat property in QvOdbcConnectorPackage.exe.config file. For UPN format, edit the property to: <add key="SSOUsernameFormat" value="upn" /> For samaccountname, format property should look like this: <add key="SSOUsernameFormat" value="samaccount" /> |
QB-8541 | Multi KPI chart style is changed unintentionally | Multi KPI chart is now reverted to the original style. |
August 2021 Patch 7
Key | Release Notes Title | Release Notes Description |
QB-8387 | Sessions shared between browsers do not sync selections when using SAML authentication | SAML authentication flow was corrected to make sure that "samluser" object matches the referential "BaseUser". |
QB-8261 | Assignments with UNKNOWN domain name pushed to the local Licenses service | Removing existing or adding new assignments for Qlik Cloud-specific users would not sync with the local Licenses service. This resulted in discrepancy in active assignments between Qlik Sense Repository and Licenses services, which could result in an inability to assign new users. |
August 2021 Patch 6
Key | Release Notes Title | Release Notes Description |
QB-8198 | Amazon Athena connector improvement | When using the Amazon Athena connector, the Data preview dialog now uses row limits with generated queries. This improves load times. |
QB-7722 | Unreliable auto-save behavior after reload | Qlik Sense will automatically save edits on session close and at a regular interval. Auto-save could be unreliable when a user session against an app had changed between open modes "with data" versus "without data". This happened if an end user would open an app without data and then reload the app from the Data load editor, but it could also happen as a result of scheduled reloads with impersonation. The problem could affect all users of the app, but in a multi-node system, problems would only occur on the node where the reload took place. |
August 2021 Patch 5
Key | Release Notes Title | Release Notes Description |
QB-7988 | SSPI added for when WebFileUseWinAPI is turned off | SSPI is added in WebFileUseWinAPI=0 mode, making it possible to use current Windows credentials with web file connectors in that mode. |
QB-7987 | Fix of #myapps and #mytasks custom filters | Default #My apps or #My tasks filters would not work as QMC did not rely on fetching "user.id" from the repository service. Fix ensures that it always fetches "user.id". |
QB-7208 QB-7705 |
Qlik Sense used a version of log4net with known vulnerabilities. | Log4net has been updated from version 2.0.8 to 2.0.12 in affected components. It has not been updated for Qlik Sense Logging Service due to its ongoing deprecation. |
QB-7169 | Table inside a container sometimes does not show values | Table inside a container sometimes does not show values. |
QB-7167 | Filterpane in mashup showed no scroll bar | Using filterpanes in mashups with a large number of fields incorrectly showed the … button instead of scrolling. |
QB-6992 | Loss of application changes after app had been opened without data and reloaded in Data load editor | Loss of application edits was possible when a user session against an app had changed between open modes "with data" versus "without data". This happened if an end user would open an app without data and then reload the app from the Data load editor. |
QB-6619 | Loss of application changes was possible when auto save operations took time | Engine auto-saves all user edits continuously, but also when a session is closed. Sometimes, there can be delays in the auto-save operation because of overall load either on the Qlik software or on database and file systems. A software error made it possible for an intermittent delay in the auto-save operation on session close to affect a newly opened session for the same user on the same app in such a way that the newly opened session would never be auto-saved. This situation could occur on a web browser refresh or any kind of network issue that led to rapid closure and re-establishment of the websocket connection from Qlik Sense client to Engine. |
QB-6400 | Selections are not displayed in the selection bar | Under a certain racing condition the selection state layout did not represent the latest selection properties. The correct selection was however always applied. |
SHEND-614 | Enable configuration of server timeout for duplicating large applications | Duplicating large application in the Hub intermittently would throw an "App could not be duplicated." error and result in two copies of the app. This was caused by a hard-coded server request timeout after which retry attempt was automatically triggered. This is now fixed by exposing the timeout value for configuration. If not defined, defaults to 10 minutes (600000 milliseconds). Configured via C:\Program Files\Qlik\Sense\ServiceDispatcher\services.conf file: [globals] servReqTimeOut=600000 (...) [broker.parameters] --server-req-timeout=${servReqTimeOut} (...) [hub.parameters] --server-req-timeout=${servReqTimeOut} (...) |
QDCB-1094 | qdc-catalog-service connect to correct proxy port when proxy port is set | qdc-catalog-service will connect to correct proxy port when proxy port set to a different instead of the default port 443. |
August 2021 Patch 4
Key | Release Notes Title | Release Notes Description |
QB-7474 | Performance improvement to ConvertToLocalTime function | Significant performance and stability improvements to the ConvertToLocalTime function. |
QB-7366 | Exploration menu not working | Exploration menu was not working in charts inside a container after upgrade to August 2021. |
QB-7336 | Fix for the default tls version for nl-app-search | The default version of TLS used in previous releases was 1.1 which could be changed using a parameter. This fix sets the default version version of TLS in nl-app-search to 1.2 |
QB-6962 | Remove deleted master items from qvf file | Master items (dimension and measure) were deleted from an app and the app was published and replaced. When the published app (QVF file) was copied from the persistent folder and imported, the QVF file still contained the master items that were supposed to be deleted. |
QB-6901 | Fast selections in a child in a container cannot be made | The container object is not in selections but its child object is. This did not allow to make all the multiple selections that are performed if they are made fast enough. |
QB-6612 | Dimension expressions could mix up field names differing only by whitespaces | When generating fields-on-the-fly for dimension expression, a canonized form of the expression is used. The canonization could strip whitespaces out from invalid expressions in such a way that the expression became valid due to an unquoted (invalid) field reference in the canonized form matched an unintended field. The canonization will now recognize this and leave a canonical whitespace in. |
QB-6471 | Map point layer images failing in mashups on network | This bug fixes an issue where a GeoMapChart with Point Layer images would fail to load Point Layer images when used in a mashup over a network. |
QB-6329 | Bar chart color | Fix coloring when the mini chart scroll position starts at the end. |
QB-6320 | Not possible to restore an application with Qlik Sense May 2021 | If an app is missing version number when it is opened, we add the latest engine version number to it. |
SHEND-663 | Updated NodeJS version | This patch for Qlik Sense updates the version of NodeJS to address several security vulnerabilities announced by the NodeJS project. |
August 2021 Patch 3
Key | Release Notes Title | Release Notes Description |
QB-6958 | Apps are now presented in all supported languages. | Fixed a problem where an app is presented in English even though the device is using a supported non-English language. |
QB-6615 | Fix printing service start/stop error when certificates are missing | If the required Qlik client and server certificates were missing, the printing service would hang when stopping. This release fixes these start and stop service issues when the certificates are missing. |
QB-6297 | DatePicker object stopped working after upgrade to April 2020 and later | The sort order indicator has been changed in engine props which led the sortOrder to be incorrectly defined and thus the selection is not done. |
August 2021 Patch 2
Key | Release Notes Title | Release Notes Description |
QB-6518 | Stepped version of libxml2 to 2.9.12 | Stepped version of libxml2 to ver 2.9.12 (contains important security fixes). |
QB-6290 | Update logged ProxySessionID if the proxy attaches with a new ID | The engine session always logged with the initial ProxySessionID, provided by the proxy when the session was created. This ID could become irrelevant or confusing if successive proxy sessions attached to and detached from long-lived engine sessions, e.g. through TTL. The engine now updates the associated ProxySessionID if a new one is provided upon session attach. The update is recorded in the engine log. |
QB-5514 | Qlik Sense: Variable changes and additions are not kept during import and replace of app | User variables and additions was not replaced when an app is imported and replaced. |
August 2021 Patch 1
Key | Release Notes Title | Release Notes Description |
SHEND-567 | Improvements to Search feature in the Hub |
With a large number of applications in the Hub, the performance of the Search feature could be significantly impaired. This functionality has now been improved but for this release it is by default disabled. It can be enabled by adding a corresponding capability flag in C:\Program Files\Qlik\Sense\CapabilityService\capabilities.json file, in example: {"contentHash":"2ae4a99c9f17ab76e1eeb27bc4211874"," originalClassName":"FeatureToggle","flag":"HUB_OPTIMIZED_SEARCH", "enabled":true}
|
QB-6559 | Preventing selections when updating a calculated field | Since calculated dimensions are not equivalent to fields, selections wont work the same. When making selections in a field, rows are never removed, while that might be the case for calculated dimensions. To ensure that the a row still exists before selecting it, the listbox will now wait until it is updated from previous selections. Word cloud |
QB-6521 | Word cloud chart size | Ignore rendering word cloud chart when its size is very small. |
QB-6399 | Fix - Insight Advisor Chat is not working when having a Postgres password with special character (?) | Fixed the issue where Insight Advisor Chat is not working when having a Postgres password with a special character (?) |
QB-6333 | Flex box issue in Safari | A workaround to avoid a third party issue. |
QB-6048 | Set analysis with money format | Set analysis on money formatted numbers should not require the comparison string to be money formatted. |
QB-6047 | Webfile in WinApi mode stream-lined for https access | Https certificates are accepted similarly to non-WinAPI mode, additionally with settings ini WebFileAllowInsecureCert added to cover rare cases. |
QB-5860 | Operation was cancelled error when using Qlik data analytics connection (SSE) | Do not raise GRPC status code CANCELLED as a separate error condition if the ongoing request is already cancelled. |
QB-5706 | Unexpected number formatting of KPIs in Qlik Sense | Changed the rounding method for these types of decimals to make sure that 0.xx5 is always rounded up. |
QB-5705 | Disabling animation for custom formatting | Since the animation adds little value and this is a corner case, we simply disable the animation for this case |
QB-5681 | Axis selections on a container object do not stick | When making axis selections on a container object with false show conditions, the selections do not stick since the layout of the object is reloaded. |
QB-5558 | Fix app are not showing correctly on iPhone | Fix objects height are not showing correctly on iPhone |
QB-5544 | Increase nl-app-search http request timeout | For apps with larger data models, dataprep classification calls can take a long time to complete. Increase the timeout of nl-app-search http requests to 2 minutes to avoid errors when longer calls succeed. |
QB-5436 | Improved handling of empty attribute dimensions in Sense pivot tables | Empty attribute dimensions of Qlik Sense pivot table definitions incurred a considerable performance penalty when evaluating the table, particularly in highly expanded states. The cost is necessary and natural with a present (non-empty) attribute dimension, but an empty dimension doesn't require any calculations. Their presence is now detected beforehand and they are handled through a dedicated shortcut without noticeable penalty. The empty dimensions (dimension definitions) can occur for many reasons, e.g. due to templated object definitions, but they have been mistakenly added by certain versions the Sense client. |
August 2021
Key | Release Notes Title | Release Notes Description |
QB-2346 | fix: capabilities Api issue when rendering charts from sessionApps | There was an issue with mashups using the capabilities Api to create a sessionApp and trying to render visualizations based that app. Sometimes the chart did not render. |
QB-2487 | "Fit to page" not working correctly when exporting a story | Fixes so "Fit to page" works correctly for bar- and line-charts when exporting for example a story with embedded sheet. |
QB-2586 | Sort order not saved on bookmarks with layout | The sorting order property on pivot tables was sometimes not saved on a bookmark with save layout. |
QB-3179 | Fixed by upgrading Oracle driver | Upgrade Oracle to 1.4.9.1009 fixed the issue |
QB-3185 | Qlik Sense Repository service not working with TLS 1.2 enforced in AzurePortal | Due to a problem with the embedded Devart Postgres library, the repository service was not able to communicate when TLS 1.2 was forced as minimum protocol in the SSL settings on the Azure hosted Postgres instances. Addressed by using the latest Devart driver in the Qlik Sense composition. |
QB-3428 | Map Object Fix | Fixed a bug where Map Object is not aligned with other chart equivalents |
QB-4039 | Windows 150% scaling causing button object to not scale/render as expected | Fix to keep button inside object boundaries when scaling the window |
QB-4090 | 'Failed to update heartbeat for Repository service status' errors but database values get updated | System_Repository logs were spammed with false errors indicating failure to update node's heartbeat status, though the database values were correctly set. This mechanism was improved and no more errors are logged. |
QB-4220 | Paths from GetInteract corrected | Paths from GetInteract are corrected which causes debugging of scripts with Must_Include to return the correct lib path from engine, which will avoid error in the interaction with the client. Thus debugging of such scripts now function properly. |
QB-4354 | Download data takes a long time in a large app | Some improvement is how app changes are saved has been made on the client side that decreases the Download request time a little bit. |
QB-4391 | Export to PDF – fix flattened objects | Export to PDF – fix flattened objects: set the height to the visible sheet height |
QB-4648 | Angular.js upgrade | Upgrade of Angular.js for all relevant component. |
QB-4678 | The "DeleteBySelection" operation failed' error when trying to delete a stream | Under certain circumstances, when having an application and its duplicate published to the same stream, it was not possible to delete that stream. This is now fixed. |
QB-4699 | Hypercube memory limit error handling when using Aggr | Errors that are due to memory limit being reached when calculating a nested hypercube are returned to the client so that an error message can be displayed to the user. |
QB-4724 | Multi KPI object changes layout after page reload | Multi KPI object changes layout after page reload |
QB-4727 | Add FileTime() value for hosted filed | FileTime without arguments is supported for hosted files, for example for data files in QCS. |
QB-4762 | Date Picker : Not showing correct date for Range Today. | Because of different time zones, the date comparisons failed when checking for Range. Note : With the solution, the Range today works as expected. |
QB-4770 | Keyboard navigation for filter pane selection seems broken in embed sheet preview | Fix to avoid wrong filter panes to open with keyboard in embedded sheet preview |
QB-4840 | Japanese language stops client from loading | Choosing japanese language causes the client to crash. |
QB-4904 | Changing the header font size does not get export to PDF | Header size was not exported to PDF/Image because CSS was overwritten in printing. |
QB-4929 | Making sure the number of data points is limited | The first load of the chart fetched too much data, but the correct amount when reloading it, e.g. switching sheet back and forth. Now both loads are limited to the correct amount of data. Also showing the "Currently showing a limited data set" disclaimer for two dimensions as well. |
QB-4960 | Not being able to export data from dynamic views | The ability to export data from dynamic views has been restored. |
QB-5028 | In 3rd party extensions using qlik.getGlobal(this) was crashing | In 3rd party extensions using `qlik.getGlobal(this)` was crashing due to bad reference to new RPC model - Now fixed, both `qlik.getGlobal()`and `qlik.getGlobal(this)` do fallback to the enigma RPC model. |
QB-5050 | Details description not displayed for a master measure with modifier | Include description of master measure with modifier in details |
QB-5088 | Qlik Sense SaaS: Default bookmark with selection not working when "Save sheet location" is not enabled | Applying default bookmark when opening app for first time |
QB-5103 | ODBC connector packages is able to process binary data | * On a select dialog UI, it disaplays "Binary data" insteand of System.byte[] or actual data; * When reload, is loads binary data: - Using a bulk reader - up to 4 Kb per value , the data format is hexadecimal e.g. 0102AAFFEF - Using a default way of reading data - up to 2 Kb per value, the data format is hexadecimal with dashes, e.g. 01-02-AA-FF-EF |
QB-5120 | Avoid intermediate results causing invalid json from expression | Intermediate results are not returned for some evaluated expression, which previously caused some charts to fail to be displayed. |
QB-5128 | Corrected Merge Load interpretation of null values | Null values interpretation during Merge Load was not fully aligned with the logic of regular Load statement processing. |
QB-5204 | Fix for Insight Advisor Chat data collection opt out issue | Fixed an issue where Insight Advisor Chat may send usage metrics to Qlik servers in cases where this has been deactivated |
QB-5291 | "Error 0x80091007: Hash mismatch for path..." error when installing .NET Framework 4.8 bundled with Qlik Sense installer | When installing or upgrading Qlik Sense on operating systems with versions of .NET Framework lower than 4.8, an automatic update of .NET Framework would fail with "Error 0x80091007: Hash mismatch for path: C:\ProgramData\Package Cache\.unverified\NetFx48Full, expected: 8DD233698D5EB4609B86C2AC917279FE39E0EF4C, actual: 7FA401D92A8FE6896854D22C25405BCA118FD1C0" error. This is now fixed. |
QB-5294 | Script method NoOfRows only works for current section | The script method NoOfRows only work for the current section. Getting NoOfRows from a table in another section returns nothing. |
QB-5299 | Qlik Sense May 2021 fails to install\upgrade due to missing Microsoft Visual C++ 2015-2019 Redistributable (x64) | When installing or upgrading Qlik Sense to May 2021 release on operating systems missing Microsoft Visual C++ 2015-2019 Redistributable (x64), installer would fail during the PostgreSQL version 12.5 install. This is now fixed. |
QB-5347 | Shortening of softpatch sets corrected | Algorithm for shortening softpatch sets has been corrected, affecting e.g. moving columns in certain tables. |
QB-5349 | Fixed issue with map tooltip. | Fixed issue with the map wrongly formatting the tooltip value with decimals. |
QB-5362 | Unauthorized / access denied shown on webfile connector | Defaulted Engine to use Windows API's to perform HTTP calls. Before the fix Engine was defaulted to use Curl and OpenSSL which caused the issue to occur (caused by fixing QB-3122). Defaulting setting to: WebFileUseWinAPI=1 Important note: In case QB-3122 is the issue you are facing, add WebFileUseWinAPI=1 into settings.ini file for Engine. |
QB-5373 | Mashup PDF and Image export not returning all rows for straight table | The export to image and pdf for the straight table did not export all the rows. This was due to the scroll position on the page. Now adjusted for that. |
QB-5404 | Direct API call (Engine): Section access using groups throws access denied when using non-lower case userId | Only affects users who directly makes API call towards Engine (and bypasses Proxy). Fixed casing error on userId and userDirectory when trying to retrieve groups for user from Repository service |
QB-5442 | Fix for insight advisor performance on complex queries/app with large dataset | Optimize the NLP search algorithm to improve the insight advisor performance for complex queries and applications with a large dataset. |
QB-5661 | Fix for issue with number formatting | Issue with number formatting in KPI object fixed. |
QB-5663 | Fix persistent storage path in precedents-service | Use custom storage path if one was provided by the user in the installer. |
SUI-6901 | Update dependency "underscore" to 1.13.x | Client exposed module "underscore" has been updated from 1.5 to version 1.13. This module is available for extensions and mashups so this upgrade might require updates to those. The changes can be found at https://underscorejs.org/. |
SHEND-552 | Simplification of logging configuration for Application Distribution and Hybrid Deployment services | Logging configuration for ADS and HDS via appsettings.json files from respective locations has been simplified to the following format: "Logging": { "LogMinimumLevel": "Information", "FileSizeLimitBytes": 100000000, "RetainedFileCountLimit": 31, "RollingInterval": "Day", "RollOnFileSizeLimit": true, "OneLineException": true }, It is important to remember that any changes to all config files residing under C:\Program Files\Qlik\Sense are always overwritten with the default values upon an upgrade. Should you have any customization in those files and are restoring them after an upgrade from a copy, make sure that the logging section is aligned with the above. |
SHEND-509 | Improve handling of conflicts when updating time-stamps on UDC related entities. | Value of ModfiedDate in the UserDirectorySettings table from QSR database is now set to DateTime.Maxvalue in order to avoid any potential conflicts. |
SHEND-500 | New KeepAlive option to repository DB notification handler. | Due to network instabilities repository service could sometimes loose the connection on the database notification handler. Repository service was unaware that the connection has been lost and therefore did not make any attempts to renew it. In order to avoid this from happening a KeepAlive option has been added to force a connection check at the given intervals. This is controlled via newly introduced key in C:\Program Files\Qlik\Sense\Repository\Repository.exe file and by default set to 60 seconds: <add key="DatabaseChannelReceiverKeepAlive" value="60" /> |
SHEND-495 | Minor updates in connection session settings for Advanced LDAP UDC. | Logic behind the two following Advanced LDAP flags has been slightly improved: nocertverify - skips server certificate validation certdebug - debug level on certificate chain validation errors, if any, for troubleshooting |
The following issues and limitations were identified at release time. The list is not comprehensive; it does however list all known major issues and limitations.
Clients
• Third-party extensions are currently not supported on mobile devices, and the Qlik Trusted Extension Developer program does not accredit extensions for use on mobile devices. Depending on individual device specifications, mobile OS, and size of the Qlik Sense app, items generated using a third-party extension might fail to be visualized properly on a mobile device.
• When consuming Qlik Sense apps using Microsoft Edge browser, touch screen mode is activated by default even when it is run on a non-touch device. Workaround: turn 'touch screen mode' off from the navigation menu.
• When consuming Qlik Sense apps using Microsoft Edge browser on touch/hybrid devices, the long-press action does not work. This limitation prevents from accessing functions such as an object’s context menu, which on touch mode requires a long-press. This is a Microsoft Edge’s issue. Workaround: If using a hybrid device, turn the touch mode off and turn it back on again.
• Export as Anonymous does not work for mashups deployed in a domain that is different from the domain in which Qlik Sense is installed. Export only works for Anonymous if the mashup is deployed in the same domain as Qlik Sense.
• When using the new “Load Extension” syntax in the load script, the Data load editor syntax completion does not work well after the keyword “Extension” when trying to write the call to an SSE function (AAI function). Nevertheless, the script executes correctly.
• Legend does not show dimension values that are after row number 3000.
• Internet Explorer supports a maximum of six web socket connections. Workaround: See https://msdn.microsoft.com/library/ee330736(v=vs.85).aspx
• Exporting a story to PowerPoint limitations:
- Titles are not rescaled as HTML, font settings are not yet exported.
- Storytelling effects are not applied.
- Exported charts may show fixed scroll bars, depending on the export resolution.
• Opening the first application after login takes longer time in in Chrome version 78 or older.
• It is not possible to open the context menu of an orc chart on a touch device.
• When you choose to view data in the context menu in a Dynamic Chart and make a new selection in the app, you need to refresh the browser for the chart to be displayed again.
Dynamic views
• Dynamic views that are deleted from one app are also deleted from every other app that was using the same view. There is no work-around for this issue other than to avoid deleting views that may already be in use by one or more other apps because of having made copies of these apps.
• When creating a new dynamic view in the assets panel, if there are one or more existing dynamic views, the dropdown menu item does not automatically change to show the charts of the newly created dynamic view. The user must click on the dropdown menu to choose the newly created view.
• The data for a dynamic view is automatically refreshed (i.e. re-queried from source) whenever a user enters a sheet containing any charts for that view. The same occurs when entering and then returning from the global selections panel as well as when adding a new chart for the same view. To prevent triggering this automatic refresh behavior, users should refrain from performing these actions on the base app.
• The view of a dynamic chart is cleared and overlaid with a message indicating a view constraint violation condition whenever the user changes the selection state of the base app such that the view's constraints are violated. Users should refrain from altering the selection state of the base app at least until they are finished making use of the data in any one of the dynamic view charts.
• The right-click "Go to source" option on a Snapshot slide for a dynamic chart does not select the actual dynamic chart when changing the view to the base app sheet.
• Chart settings changes made to dynamic view charts using the Exploration menu are lost following refresh operation of the view.
• Dynamic Views currently does not support the Trellis extension.
Managing a Qlik Sense site
• The QMC Custom Property Edit page can currently handle a limited number of custom properties. If you want to edit custom property values in the QMC, we recommend keeping the amount of custom property values to a maximum of 500. If you want to just apply values without modifying them, the QMC can handle up to 10.000 custom property values.
• The Qlik Logging Service handles communication outages with PostgreSQL by retrying three times to establish the connection and displays an error if unsuccessful. Communication outages with PostgreSQL can occur for a number of reasons and are not always recoverable in the limited time window of three tries.
• With the current architecture it is not possible, using security rule on HubSection_* resource, to hide "Open hub" link from the "Navigation" menu when accessing app as an anonymous user. Workaround: Use reverse proxy configured to redirect "Open hub" link to a preferable landing site
• When removing app objects from an application via QMC’s interface, deleted objects are not removed from that application’s binary file stored on the file system.
• Logging utility does not support Postgres 12. The utility uses queries that are not compatible with Postgres 12.
• Unable to hide "Open hub" link for anonymous user by using security rule
With the current architecture it is not possible, using security rule on HubSection_* resource, to hide "Open hub" link from the "Navigation" menu when accessing app as an anonymous user. Suggested workaround is to use reverse proxy configured to redirect "Open hub" to a preferable landing site.
• Task Chain Icon not visible in QMC Workarounds:
1. Once the event trigger is created, sort or filter on any of columns available in the Tasks section.
OR
2. Permanently disable caching in QMC by setting false to the following flag from C:\Program Files\Qlik\Sense\CapabilityService\capabilities.json file and restarting Qlik Sense Service Dispatcher and the browser.
{"contentHash":"2ae4a99c9f17ab76e1eeb27bc4211874","originalClassName":"FeatureToggle","flag":"QmcCacheEnabled","enabled":false}
* Data connection passwords containing special characters are not properly encoded when updated via Qlik Management Console. Description: Data connection passwords containing special characters (such as "=", "%", or ";") are not correctly encoded when updated via the Qlik Management Console (QMC). This causes authentication errors when trying to connect to specific data sources, which could cause reload tasks to fail.
The simplest workaround is to use the data load editor to update the password.
Please note that once the password is updated, the name of the data connection is automatically appended with "(domain_userId)". This can be adjusted later on via the QMC.
Qlik Sense Desktop
• Sorting by expression in a Pivot table may not work as expected.
• Qlik Sense Desktop can play WebM and Ogg, but not MP4 files due to limitations in Chromium.
Connectors
• REST connector: The Next token pagination option does not work when the pagination token has the same value for each page.
• For connectors in the ODBC Connectors Package, only the data types listed as supported in the online help have been verified to work correctly in the Preview and Script editor. However, ODBC Connector Package does not prevent the loading of other data types, so in some cases unsupported data types can be loaded with the load script.
• ODBC connector: If the user name on the Microsoft Windows system running Qlik Sense Desktop contains letters that are not English alphanumeric characters, database connectors in the ODBC Connector Package do not work properly. Workaround: Change the Windows system locale to the match the character set that contains the characters used in the user name. For example, if the System locale on the system running Qlik Sense Desktop is set to English and a user name contains Swedish characters, the System locale setting must be changed to Swedish for the ODBC connector to work properly.
• The Qlik Salesforce Connector does not support PK chunking on sharing objects. PK chunking is supported only on parent objects.
• Apache Phoenix connector does not support non-latin characters in metadata. Connector may return a corrupted data or unpredictable query results if running a query with non-latin characters in metadata: table names, column names, aliases, etc.
Cloud deployments and Multi-Cloud
• When downloading a pivot table in cloud environments (Qlik Sense Enterprise on Cloud Services and Qlik Sense Enterprise on Kubernetes), expanded rows are not included but stay collapsed.
Please refer to the online help for information about the requirements for Qlik Sense:
System requirements for Qlik Sense
Upgrade from August 2021 Patch 4 or earlier to August 2021 Patch 5 or later
Upgrade from August 2021 Patch 4 or earlier to August 2021 Patch 5 or later
Following upgrade steps need to be followed when upgrading from August 2021 Patch 4 or earlier to August Patch 5 or later (see table below for detailed upgrade matrix)
Source track |
Destination track |
Upgrade steps |
May 2021 or previous |
August 2021 |
NO |
May 2021 or previous |
August 2021 patch 4 or earlier patch |
NO |
May 2021 or previous |
August 2021 patch 5 or later patch |
YES |
May 2021 or previous |
November 2021 GA or later track |
NO |
August 2021 Releases
https://community.qlik.com/t5/Downloads/tkb-p/Downloads
About Qlik
Qlik is on a mission to create a data-literate world, where everyone can use data to solve their most challenging problems. Only Qlik’s end-to-end data management and analytics platform brings together all of an organization’s data from any source, enabling people at any skill level to use their curiosity to uncover new insights. Companies use Qlik to see more deeply into customer behavior, reinvent business processes, discover new revenue streams, and balance risk and reward. Qlik does business in more than 100 countries and serves over 48,000 customers around the world.
Table of Contents
The following release notes cover the versions of Qlik Sense released in November 2022.
Please refer to the What’s new sections of the online help for information about the new and updated features of the Qlik Sense Enterprise on Windows November 2022 release:
What's new in Qlik Sense November 2022 (Users)
What's new in Qlik Sense November 2022 (Developers)
What's new in Qlik Sense November 2022 (Administrators)
Refresh license definition in QMC
With a signed license key, you can trigger license definition synchronization using the ‘Refresh license definition’ button. The button is located on the Site license pane under License management in the Qlik Management Console (QMC). The new ‘License definition last updated’ field on the Site license pane shows the last updated timestamp for the license definition.
Google BigQuery connector
The OAuth flow for the user authentication mechanism has been updated. This is due to the deprecation of the OAuth out-of-band (oob) flow by Google. The change requires reauthentication of existing connection definitions. For more information, see https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html#disallowed-oob.
Improvements to the Hub UI
Options in the Hub have been rearranged for a better user experience. You can now find the user profile icon in the upper-right corner of the toolbar. Click this icon to open a global menu with the following options:
Custom banner messages
Support has been added for QMC administrators to publish custom banner messages in the Hub. Use banners to notify your organization about upcoming announcements or important information. Four types of banners are supported: Standard, Information, Warning, and Error. You can configure the desired duration for the banner. The default duration is 10 seconds.
Support to configure HTTP user authentication for proxy settings in ADS/HDS
UserId and Password inclusion is now allowed in proxy configuration of ADS/HDS. For more information, see Configuring a proxy for Qlik ADS and HDS communication with Qlik Sense Enterprise SaaS.
Key | Title | Description |
QB-17347 | Qlik Sense Hub: Apps not shown under Favorites when using non-English language | Fixed an issue where apps did not appear under Favorites unless you navigated back and forth. The issue occurred when using a non-English language in the Hub. The Favorites section is now refreshed for all languages when all app streams are loaded. |
QB-16950 | Qlik Cloud, Qlik Cloud for Government (FedRAMP) and Qlik Sense Visualizations: Possible to delete script variables using API calls | Fixed a problem where it was possible to delete variables using a WebSocket API call. Script variable can now only be removed by modifying the reload script and reloading the app. |
QB-16906 | Qlik Cloud Engine: Reload failures due to memory constraints when triggered outside the Data Load Editor | Fixed a problem where the engine incorrectly reported reloads as failed due to memory constraints. |
QB-15075 | Qlik Sense Visualizations: Error of reserved property 'FILTERS' | Fixed a problem where an extension using the reserved property 'FILTERS' would fail to load. |
QB-10281 | Visualizations: Chart sharing via link not working applying selections | Fixed a problem that prevented applying filtered selections when opening an app via the chart-sharing link option. |
Key | Title | Description |
QB-17039 | Qlik Sense: Signed License Key (SLK) error | Fixed a problem that was caused by a lower than min date field in a License table in the November 2022 release, causing validation issues when trying to apply a new license. |
QB-16918 | Qlik Sense Engine: Lost data rows when importing delimited UTF-16 encoded files | Fixed a problem that caused embedded NUL (binary 0) characters in delimited UTF-16 encoded files, such as CSV, to be ignored during import, resulting in an incomplete data set. |
QB-16816 | Qlik Sense Visualizations: Action button background image not shown | Fixed a problem where images on action buttons were not displayed correctly. The button now checks and works with multi-noded prefixes. |
QB-14684 | Visualizations: Combo chart tooltip displays "0" instead of "-" for missing values | Fixed an issue where the combo chart tooltip in certain cases showed "0" instead of "-" for missing values. |
Key | Title | Description |
QB-16981 | Qlik Sense: Default rule for Custom Banner Messages does not generate on upgrade | Fixed a problem in the initial release of November 2022 (14.97) that caused the default security rule for Custom Banner Messages to only be generated during a fresh install. This has been solved and the security rules are now also generated during upgrades. |
QB-16853 | Qlik Sense: Updated Node.js | Updated Node.js to address a third-party issue (CVE-2022-43548). For more information, visit https://nodejs.org/en/blog/vulnerability/november-2022-security-releases/. |
QB-15055 | Qlik Sense Scheduler: Triggered tasks not running at expected scheduled time | Fixed a problem where the scheduler services did not run properly if there were errors in the user-created cron expressions. We solved this by creating more controls and marking any problematic user entry in the scheduler error log file and ignoring that trigger until the user resolves the issue. |
QB-14951 | Qlik Sense Visualizations: Incorrect numerical abbreviation in Scatter Plot using "Auto" | Fixed a problem where using "Auto" in the chart configuration for the x or y axis showed an incorrect format in Scatter Plot charts. |
QB-14348 | Qlik Sense Engine: Mashup application hangs | Fixed a problem where a mashup application would hang when applying selections. |
QB-14264 | Qlik Sense Mobile: Lost connection on iOS | Fixed a problem where the connection was lost after minimizing the browser window and switching to other applications. |
Key |
Title |
Description |
QB-6397 |
Qlik Engine: Wrong format on pivot table columns when exported to Excel |
Fixed a problem that caused columns with the same name to have the wrong format when the pivot table was exported to Excel. |
QB-8087 |
On-demand reporting fails when filtering on an empty value |
Fixed an issue where qlik-on-demand-reporting extension would fail to generate a report when an empty value was selected. Requires Qlik NPrinting version May 2022 SR2 or later. |
QB-8632 |
Qlik Engine: Recently published sheets can have an "Object not found" error |
Fixed a race condition in object persistence that sometimes resulted in "Object not found" for recently published sheets. |
QB-9058 |
Qlik Sense: Possible to apply same custom property value more than once |
Fixed an issue where it was possible via QMC or API request to apply the same custom property value belonging to the same custom property definition more than once to the same resource. |
QB-9515 |
Qlik Sense Enterprise Connectors: Wrong results via reload with MySQL connector |
Fixed a problem in the loading of text values when the date field is NULL in Bulk Reader mode for the MySQL connector. |
QB-9584 |
Add "My domain" support for Salesforce connector |
You can now use your private subdomain in my.salesforce.com. See https://help.salesforce.com/s/articleView?id=sf.faq_domain_name_what.htm&type=5 |
QB-10425 |
SAML response could be used to obtain new X-Qlik-Session cookie |
Fixed an issue where new X-Qlik-Session cookies were generated upon SAML replay requests. With this fix, used SAML assertion IDs are stored in memory and a replay attack results in the "400 Bad Request" error, accompanied by a warning in Audit_Proxy logs: "SAML replay detected with assertionId: <id>". |
QB-10558 |
Qlik Sense Visualizations: View data for container chart shows incorrect data |
In a container with two charts using different data, the ‘View data’ option showed only the data for the first chart. This issue has been fixed, and the data shown now matches the selected chart. |
QB-10629 |
Scheduler: Reload tasks stuck in 'Triggered' state |
Fixed a problem that caused the Scheduler service to fail to transition to state Active if there was an incorrectly configured Custom trigger. This was solved by catching the exception and logging a warning message in System_Scheduler logs. |
QB-10681 |
Qlik Sense Visualizations: Problem when exporting tables with show condition to Excel |
Fixed a problem where table exports to Excel were corrupt when tables used show condition. This was solved by correctly checking if a column is shown or hidden. |
QB-10763 |
Qlik Oracle connector: Error in XML element function |
Fixed a bug where using the XmlElement function in queries of the ODBC Connector Package Oracle datasource caused an error (ORA-00907: missing right parenthesis). |
QB-10772 |
Visualizations: ODAG report generation fails with error "Failed to create new request link" |
Fixed a problem where non-integer expression values were causing the ODAG report generation to fail. |
QB-10783 |
Custom theme for bullet chart not working |
Fixed an issue with custom themes for bullet charts. |
QB-10810 |
Qlik Sense Visualizations: X-axis labels disappear |
Fixed an issue that caused the X-axis label on charts to disappear when zoomed to 90%. |
QB-10843 |
Visualizations: Cannot apply properties to charts in containers |
Fixed a problem that prevented removing an alternate dimension from the chart. This was caused by a mismatch between the properties. A dialog is now displayed, so changes can be applied. |
QB-10846 |
Visualizations: Container charts show extra spaces on mobile devices |
Fixed a problem where extra white space was visible on mobile devices if the selected chart used less space than allocated for the container object. |
QB-10859 |
Qlik Sense Visualizations: Problem when exporting data with table formatting to Excel |
Fixed a problem that caused exported tables to lose their formatting, including dates, dual values, and RGB color codes. |
QB-10874 |
Qlik Cloud Visualizations: Console errors for the product-info.json file when using mashups |
Fixed a problem related to CORS that caused Console errors when fetching a static file in a cloud mashup. |
QB-10936 |
Qlik Sense License Monitor: Missing data connections |
Fixed a problem where some data connections were missing from the License Monitor. The default data connections have been restored. |
QB-10937 |
Qlik Cloud Enterprise Connectors: DynamoDB restricted access at table level |
Fixed a problem that would cause the connector to fail if the AWS policies restricted access to a table. |
QB-10963 |
Fixed dynamic views to show items |
Dynamic views would show a message "No items". |
QB-10967 |
Qlik Sense Engine: "Invalid visualization" error message shown on some apps |
Fixed a problem where incomplete layout data was being passed from the Qlik Engine, resulting in the error message "Invalid visualization - The visualization was not found on the server" being shown. This occurred even for built-in visualizations. |
QB-10972 |
Could not load data when field was named "not" |
Data fields named "not" can now be loaded by quoting them with brackets ([]) or double quotes (""). |
QB-11033 |
Qlik Sense Visualizations: Text wrap on table objects not working |
Fixed a problem where table rows were displaying all text in cells, causing unnecessarily large tables. This was resolved by restoring the default row height limit of three rows of text. |
QB-11144 |
Qlik Sense QMC: Duplicate status values |
Fixed an issue where the Status filter list would show duplicate values for 'Queued' and 'Started' statuses. |
QB-11232 |
Qlik Sense Visualizations: Drill down dimension selection on a dimension value label |
Fixed an issue with the drill down dimension selection that appeared on dimension value labels when there was only one dimension value left. |
QB-11236 |
Qlik Cloud Alerting Services: Creating alerts not working when label is missing |
Fixed a problem that prevented creating alerts. The issue was caused by labels not being treated as labels when surrounded by square brackets. |
QB-11239 |
Qlik Sense Hub: Favorites section in the hub does not initially show all |
Fixed a problem that caused the hub to take a long time to fetch apps owned by other users and belonging to different streams. This prevented the Favorites section of the app from showing all apps. |
QB-11248 |
Dropdown filter still showing in storytelling view |
Dropdown filters remained on the page when moving between analysis and storytelling view. This has been fixed and all open popovers are closed before navigating away from the analysis view. |
QB-11294 |
Qlik Cloud Analytics: Select data from source does not work for data sources added to app via Create app from data |
Fixed a problem where the space name was not defined in the new load script when using the ‘Select data from source’ option, which caused an internal error. The ‘Select data from source’ option now works as expected. |
QB-11365 |
Invalid parameter error on custom tooltip |
Fixed invalid parameter error when there are multiple layers containing a custom tooltip. |
QB-11384 |
Qlik Sense Visualizations: Qlik-animator ID changes each time the service is started |
Fixed a problem where the version number in the manifest and package JSON files were mismatching. This caused the Qlik animator service to be considered different and reinstalled every time the service was restarted. |
QB-11555 |
Visualizations: Problem with the selection toolbar menu on mobile browsers |
Fixed a problem that cut off the selection toolbar menu on mobile browsers when in landscape mode. |
QB-11556 |
Incorrect legend position in combo chart |
Fixed an issue with combo chart legend position in certain combinations of resolution and chart size. |
QB-11559 |
Scrollbar size differs between charts on touch devices |
Fixed an issue with the scrollbar size in bar charts and bullet charts on touch devices. |
QB-11580 |
Qlik Sense Visualizations: Combo chart axis always includes 0 |
Fixed a problem where combo charts with stacked bars included 0 on both axes instead of only on the axis with bars on it. |
QB-11591 |
Bar chart missing month label for July |
Fixed a data issue in a bar chart for a two-dimensional group. |
QB-11685 |
GeoAnalytics: Map object stuck in an infinite loading state |
Fixed a problem where a map object with embedded GeoJSON data properties could get stuck in an infinite loading state if line/polygon features were not correctly terminated. This will now result in a JSON parse error. |
QB-11740 |
Qlik Cloud Visualizations: Master item label not updated after editing |
If the master item was duplicated, unlinked, and added as a master item again, editing the label would not be updated on the visualization. This has now been fixed. |
QB-11745 |
SaveToDisk table on General Web Connector does not apply regex filter |
The SaveToDisk table on the General Web Connector has been fixed to properly apply the specified regex filter. |
QB-11759 |
Qlik Cloud Enterprise Connectors: BulkReader cannot process large strings |
Fixed a problem where BulkReader mode had an incorrect max string limit of 4096 characters. |
QB-11803 |
Qlik Data Gateway - Direct Access: Oracle Wallets is not working |
Fixed an issue with Oracle Wallets. |
QB-11818 |
Qlik Sense: Authenticating via OIDC fails ("400 Bad Request") |
Fixed a problem where authentication via OIDC would fail if any of the optional attributes had an empty value when the Disable OIDC optional attributes option was active in virtual proxy settings. |
QB-11843 |
Qlik Sense Visualizations: Combo chart legend is not wrapping correctly |
Fixed a problem where sometimes text in categorical legends did not wrap correctly. |
QB-14086 |
GeoAnalytics: Issue with custom tooltip for chart layer with coordinates |
Fixed an issue where custom tooltips were not displayed on chart layers using coordinates for locations. |
QB-14196 |
Qlik Engine: QVD LOAD with CrossTable prefix crashes |
Fixed a problem that occasionally caused a QVD LOAD with CrossTable prefix to crash. |
QB-14280 |
Qlik Sense on Windows: userId and userDirectory properties case sensitive when allocating license access type |
Attempts to allocate the license access type failed if there were uppercase letters in the userId property or lowercase letters in the userDirectory property. The repository service returned "201 Created" with "null" in response and the allocation was not instantly persisted in the corresponding table in the QSR database. This issue has been resolved. |
QB-14297 |
Qlik Sense Engine: Dutch parser (NL) is not starting when enabling NLU_MUILTI_LINGUAL |
Fixed a problem that prevented the NL-parser from starting when enabling multi-language natural language queries in Qlik Sense Enterprise on Windows. |
QB-14316 |
Custom schedule trigger shows default value instead of the custom value |
Fixed an issue where custom triggers showed the default values until the changes were applied on the corresponding reload task. |
QB-14326 |
On-demand apps: Navigation point properties are not shown |
The navigation point properties are visible now for on-demand apps. |
QB-14353 |
Qlik Sense QMC: Undefined "userId" error in the QMC |
Fixed a problem where administrators would get an undefined "userId" error when loading the QMC. |
QB-14484 |
Qlik Cloud Engine: Non-script variable values are not preserved when app is reloaded |
Fixed a problem where all variable values changed within a session using the API functions SetStringValue, SetNumValue, or SetDualValue would be reset when the app was reloaded in another session. With this release, variables that are not defined in the script will keep any value set in the end-user's session with SetStringValue, SetNumValue, or SetDualValue when the app is reloaded. |
QB-14494 |
Qlik Sense Visualizations: Accidental chart deletion with open variables dialog in Edit sheet |
Fixed a problem where a chart could be accidentally deleted in the background if the variables dialog was open and the delete key was pressed. This was solved by blocking the grid while the variables dialog is open and unblocking once it is closed. |
The following issues and limitations were identified at release time. The list is not comprehensive but lists all known major issues and limitations.
For information about the requirements for Qlik Sense, see System requirements for Qlik Sense in the online help.
https://community.qlik.com/t5/Downloads/tkb-p/Downloads
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.
Table of Contents
The following release notes cover the versions of QlikView released in May 2022.
The function MutualInfo() calculates the mutual information between two fields.
It is now possible to hide tabs in the container object. The object will show the first non-hidden object.
The Mekko chart can now show totals on top of each segment stack.
Support for the QVF file format was introduced already in the May 2021 version. With the May 2022 version the QVF format will be the default file format for new documents. The old QVW file format will still work and will be the default save format for existing QVWs.
If a server has two documents with the same base name but different extensions, the QVW will be inactivated. The meta and shared files will however be used also by the QVF.
There is no cross-compatibility between QlikView QVF files and Qlik Sense QVF files.
The QlikView Server services have been upgraded to .NET 4.8.
Previously, the Doc Admin cache was just in memory and was erased if the QlikView Management Service was restarted. Now the cache is persisted in a database.
Previously, the QlikView Server have had the functionality to send an email alert if any of the tasks would fail on the reload. Now we have added possibility to also include tasks that finished with warnings.
The 'Log collector' tool developed by the Qlik Support has now been integrated into the QlikView Management Console. For a clustered environment, there are some limitations: Only the logs from QlikView Server and QlikView Distribution Service are collected.
The user document, created in a Loop and Reduce process, now contains information about the task name and last execution time. This is found in the document support information.
This release addresses several bugs. See below under “Resolved Issues”.
The system requirements for this release can be found under “System requirements” on the Qlik help web site. https://help.qlik.com/en-US/qlikview/May2022/Content/QV_HelpSites/System-requirements.htm
There are no upgrade notes for this release.
The following issues and limitations were identified at release time. The list is not comprehensive; it does however list all known major issues and limitations.
Qvp links can no longer be used in a browser
In previous versions, it has been possible to use links beginning with ‘qvp://’ to access QlikView files from a browser. This is no longer possible. Such links however still work when used by QlikView Desktop.
CutePDF does not always work in clustered environments
Issue ID: QV-23452
Due to a 3rd party limitation in CutePDF, not supporting UNC paths, it is not possible to print reports when using clustered nodes on Windows 2012.
QlikView May 2022 comes with fixes for the issues listed below.
QlikView Server with IIS upgrade no longer reverts the password for service user settings
Issue ID: QV-20964
Fixed an issue where a QlikView Server 12.60 upgrade could revert the password for service user settings.
Field disappears after replacing a field using Sheet Properties >> Objects tab
Issue ID: QV-21062
Fixed an issue where changing the list box properties/definitions in the object page of Sheet Properties, could cause the listbox on the sheet to disappear.
Incorrect sorting in drop down select list boxes
Issue ID: QV-21252
Solved an issue for drop down select list boxes where the list did not follow the selected sort criteria of the object or the field.
QlikView Ajax Client: Short name for Wednesday corrected for Japanese language
Issue ID: QV-21394
Fixed an issue where the Japanese weekday Wednesday was displayed like 水曜 instead of 水 in the AJAX/Webview Calendar object.
Better handling of column/row sizes in containers (AJAX)
Issue ID: QV-21820
Solved an issue where the Grid Container did not render the right end object properly in AJAX/Webview.
12.50 and 12.40 Selected Field is cleared by reload
Issue ID: QV-21822
Fixed an issue where the selected field was cleared by reload.
Incorrect redirection upon failed login attempt
Issue ID: QV-21851
Introduced protection against phishing attempts to solve an issue where an attacker could maliciously poison the back= parameter.
QV Server not working with IIS and OnDemand AddOn
Issue ID: QV-21879
Newtonsoft.dll removed from webserver/IIS installation to fix an incompatibility between newer versions of QlikView Ajax Client when run in IIS and On-Demand Add-On.
Unexpected objects appear after selecting Copy Object with IE Plugin
Issue ID: QV-22161
Fixed an issue where the sheet objects could be rendered twice with different/wrong zoom factor on screen.
QlikView Ajax Client: Lock icon not displayed
Issue ID: QV-22214
Fixed an issue where a Listbox with selection style "Windows checkboxes" and "Always one selected" checked, did not show a lock icon.
Straight Table column order in server
Issue ID: QV-22262
Straight Table column order in server is now the same as in desktop.
Variable Errormode not working as expected in QlikView 12.50SR4
Issue ID: QV-22297
Fixed an issue where the variable Errormode was not working as expected in QlikView 12.50SR4.
PDF Report of grid-like objects in 12.60 has wrong scale
Issue ID: QV-22303
Fixed an issue where grid-like objects, for example Table Box and Straight Table, could appear to be twice the size larger in PDF format.
QlikView Ajax Client: "Copy cell value to Clipboard" doesn't always work
Issue ID: QV-22351
Solved an issue where "Copy cell value to Clipboard" did not work.
QlikView Desktop : Set correct font size of Input Text Box on selection
Issue ID: QV-22354
Fixed an issue in QlikView Desktop where the active text font size on Input Box selection was almost unreadable.
Sybase ASE ODBC driver failing to reload in 12.50 SR2
Issue ID: QV-22355
Solved an issue where Sybase ASE failed to reload due to passwords with non-alphanumeric characters. The password must to be surrounded with quotation marks.
QlikView Desktop : Export all data correctly from straight table to excel file
Issue ID: QV-22356
Fixed an issue in QlikView Desktop where some of the column data from a straight table was missing from the output when the "Export to Excel" feature had been used.
QlikView Ajax Client cannot be embedded in iframe
Issue ID: QV-22368
Solved an issue where QlikView Ajax Client could not be embedded in an iframe.
Webfile in WinApi mode stream-lined for https access
Issue ID: QV-22390
HTTPS certificates are now accepted similarly to non-WinAPI mode. Also added parameter WebFileAllowInsecureCert to settings.ini.
Scatter chart with values on datapoint could sometimes show wrong values
Issue ID: QV-22391
Fixed an issue where a Scatter chart with values on datapoint sometimes could show wrong values and cause an exception resulting in "Drawing of chart failed" in Windows but causing a crash in Qlik Cloud.
Reports fail to print after upgrading to 12.60 on Windows 2012.
Issue ID: QV-22394
Solved an issue for the Export to PDF action parameter 'PDF Printer Name' and added 'DefaultPDPrinterName' to make it possible to specify the name of a default PDF printer.
Horizontal stacked bar chart static max fix
Issue ID: QV-22397
Fix for horizontal stacked Bar Charts where some elements could fall outside the shown area and cause faulty rendering.
Crash on repeated operations on expression
Issue ID: QV-22400
Fixed an issue where QlikView could crash and show unstable behavior caused by a stack overflow error due to recursive functions.
Columns in excel file while export are grouped together
Issue ID: QV-22407
Solved an issue where the list separator to generate the Excel file did not reflect the system's regional settings, which could lead to columns in the Excel file being grouped together.
Export to Excel changes number format
Issue ID: QV-22413 (Please upgrade to SR2 to resolve this completely)
When using customized number format in expressions, the exported number could have wrong format because some of the special formats could not be convert to Excel formats. These are now exported as TEXT.
Unable to lease license when using Alternate Identity
Issue ID: QV-22449
Solved an issue where a license could not be leased when using Alternate Identity while logged on to QlikView Server with an account not configured with Professional access.
QlikView Ajax Client: Screen freeze when right click on dropdown list in multibox
Issue ID: QV-22450
Fixed an issue where the screen could freeze when interacting with the dropdown list in a Multibox.
QlikView Ajax Client: Container dropdown gets a new appearance after selection
Issue ID: QV-22469
Dropdown content could be invisible if font color in container was set to white.
Reload containing macro fails in command line reload
Issue ID: QV-22487
Command line reload for scripts using macros now works provided the “/nosecurity” switch is used.
QlikView Ajax Client: Page Unresponsive when last column has 0 width
Issue ID: QV-22556
A last column with zero width caused an infinite loop and made page unresponsive.
QVS : Report is not printed in Windows 2012
Issue ID: QV-22567
Fixed an issue where the setting to indicate the default printer in Settings.ini did not reflect what QVS expected.
Report's paper size matches that of configured printer
Issue ID: QV-22576
When a report is generated from the Access Point, its paper size will now be according to printer settings configured in QVS.
QlikView image bundle shows black squares instead of image
Issue ID: QV-22581
Fixed an issue where some images were shown as black squares.
QlikView Desktop : Correct font size of Input Text Box on selection
Issue ID: QV-22631
Solved an issue where the font size of the selected text could be decreased for higher zoom settings. The font of the selected text is now set to the correct size.
TTP Strict Transport Security (HSTS) is a policy mechanism that helps to protect websites against man-inthe-middle attacks such as protocol downgrade attacks and cookie hijacking.
In previous versions, a dialog opens off-screen if it at a prior time was used on a second monitor. This has
now been changed. The dialog is now moved so that at least a part of it is visible on the existing monitor.
There is now the possibility to disable the RC4 encryption and only use AES128. The benefit is stricter
security, however with the limitation that the 'Open In Server' command cannot be used on some Windows
versions due to limitations in these operating systems. This also prevents all use of the QlikView IE Plugin
client on these operating systems.
To disable the RC4 encryption, you need to make changes in the configuration files. See the following support
article: https://community.qlik.com/t5/Official-Support-Articles/Disable-RC4-stream-cipher-in-QlikView-May-2022-12-70-SR1-or/ta-p/1988220
The system requirements for this release can be found under “System requirements” on the Qlik help web site. https://help.qlik.com/en-US/qlikview/May2022/Content/QV_HelpSites/System-requirements.htm
There are no upgrade notes for this release.
The following issues and limitations were identified at release time. The list is not comprehensive; it does however list all known major issues and limitations.
Qvp links can no longer be used in a browser
In previous versions, it has been possible to use links beginning with ‘qvp://’ to access QlikView files from a browser. This is no longer possible. Such links however still work when used by QlikView Desktop.
QlikView May 2022 SR1 comes with fixes for the issues listed below.
QVS crashed intermittently under heavy load and interaction
Issue ID: QV-22417
Multiple additional synchronizations and safeguards have been introduced to safely handle sharing sessions
attaching and detaching. Shared object with linked (replicated) object type changes have been restricted to
safe combinations.
Installation files left in temporary folder
Issue ID: QV-22734
Installers sometimes leave .msi files under C:\windows\Installer\, which could result in a security problem. This
is now fixed, so that administrator rights are needed to access them.
Rows are shifted in the table
Issue ID: QV-22761
Fix is done so the rows are not shifted anymore in the table.
Access Point log out button doesn’t work
Issue ID: QV-22992
Access Point log out issue that occurs when the QVWS is deployed on a separate machine than QVS. The
provided fix has taken the active QVS node from the cluster and read the authentication level to perform
logout.
X-Axis Combo chart expressions text overlapping
Issue ID: QV-22999
Fixed calculation for using staggered texts when the Text on Axis option is used.
Section Access documents used with QSE SaaS are listed on AccessPoint
Issue ID: QV-23071
When Section Access contains "QLIKCLOUD" entry, the document will be listed in AccessPoint also for users
that are not allowed to open the document. This change fixes the issue.
Dimension title shown as ellipsis with Edge and Chrome AJAX
Issue ID: QV-23132
Changes done to avoid ellipsis in Pivot table box header area while scrolling.
License information exposed via public URL
Issue ID: QV-23188
Debug information for the licenses.exe process, including memory address details and stack traces, were
exposed via public URL. This information is now no longer available.
LinEst calls with fixed intercept return incorrect values
Issue ID: QV-23208
The entire LinEst function family had problems when calculating with fixed intercept, and many statistical
outputs were entirely invalid. The calculations have been corrected and now conform with Excel calculations.
QlikView May 2022 Release notes 10
Current selections window Lock/Unlock icon not visible
Issue ID: QV-23381
Icons for Lock/Unlock button was missing in QlikView Ajax client. This is now fixed.
Numeric values in scientific format
Issue ID: QV-23421
The numeric scientific values should be right aligned in the exported excel sheet. This is now fixed.
Unnecessary check boxes shown in list box
Issue ID: QV-23510
QlikView Ajax Client: With "Hide excluded" and state "Excluded" for a row, the row shouldn't have a checkbox.
This is now fixed.
Considering full file path to highlight duplicate QlikView apps
Issue ID: QV-23517
In the case of the same document in two different files – one qvw and one qvf – the qvw should be regarded
as non-active. This was however not the case when upper case was used in one field and lower case in the
other. This has now been fixed.
Not possible to use SLK license for two separate QlikView versions
Issue ID: QV-23558
The QVS is shown as Off Duty when it joins a cluster with a different version using SLK. If the SLK allows it,
the second and subsequent servers should be active, also if the servers don’t run the same version. This has
now been fixed.
Not possible to reload a QVF document containing macros
Issue ID: QV-23577
QlikView 12.70 fails to reload if the document contains a macro. This has now been fixed.
Qlik Sense Licensing: Offline Signed License Definition (SLD) did not work
Issue ID: QB-10670
Fixed an issue where Signed License Definition (SLD) tried to fetch information in offline mode if the delayed
sync had expired.
About Qlik Qlik is on a mission to create a data-literate world, where everyone can use data to solve their most challenging problems. Only Qlik’s end-to-end data management and analytics platform brings together all of an organization’s data from any source, enabling people at any skill level to use their curiosity to uncover new insights. Companies use Qlik to see more deeply into customer behavior, reinvent business processes, discover new revenue streams, and balance risk and reward. Qlik does business in more than 100 countries and serves over 48,000 customers around the world. qlik.com |
© 2022 QlikTech International AB. All rights reserved. Qlik®, Qlik Sense®, QlikView®, QlikTech®, Qlik Cloud®, Qlik DataMarket®, Qlik Analytics Platform®, Qlik NPrinting®, Qlik Connectors®, Qlik GeoAnalytics®, Qlik Core®, Associative Difference®, Lead with Data™, Qlik Data Catalyst™, Qlik Big Data Index™ and the QlikTech logos are trademarks of QlikTech International AB that have been registered in one or more countries. Other marks and logos mentioned herein are trademarks or registered trademarks of their respective owners. BIGDATAWP092618_MD |
Table of Contents
The following release notes cover the Qlik Salesforce Connector for QlikView released in December 2022.
The Qlik online help provides full documentation of the Salesforce Connector Package.
The following updates have been made to the Qlik Salesforce Connector.
There are no issues and limitations identified at the time of release.
The Qlik Salesforce Connector installs from the file QlikSalesforceConnector_setup.exe. See the online help for detailed instructions on how to install the connector.
It is recommended that you make a backup of the system before upgrading.
This Salesforce Connector (version 15.160.0) requires .NET Framework 4.8, and it is compatible with QlikView 12.40 and later.
Please refer to the System requirements for QlikView section of the online help for up-to-date information about system requirements and browser support.
The new Qlik Salesforce Connectors is available from the Qlik Downloads site.
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.
TABLE OF CONTENTS
以下のリリース ノートは、2022 年 11 月にリリースされた Qlik Sense Enterprise on Windows の各種バージョンを対象としています。
Qlik Sense Enterprise on Windows、November 2022 リリースの新機能や更新された機能については、オンライン ヘルプの「新機能」セクションを参照してください。
Qlik Sense November 2022 の新機能 (ユーザー)
Qlik Sense November 2022 の新機能 (開発者)
Qlik Sense August 2022 の新機能 (管理者)
QMC でのライセンス定義の更新
署名済みのライセンス キーがあると、[ライセンス定義の更新] ボタンを使用してライセンス定義の同期をトリガーできます。このボタンは、Qlik 管理コンソール (QMC) の [ライセンス管理] の [サイト ライセンス] パネルにあります。 [サイト ライセンス] パネルの新しい [ライセンス定義の最終更新] 項目には、ライセンス定義が最後に更新された日付と時刻が表示されます。
Google BigQuery コネクタ
ユーザー認証メカニズムの OAuth フローが更新されました。これは、Google による OAuth 帯域外 (oob) フローの廃止に伴うものです。この変更により、既存の接続定義の再認証が必要となります。詳細については、https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html#disallowed-oob を参照してください。
ハブ UI の改善
ハブのオプションが再配置され、より使いやすくなりました。ツール バーの右上に、ユーザー プロファイルのアイコンが表示されるようになりました。このアイコンをクリックすると、次のオプションを含むグローバル メニューが開きます。
カスタム バナー メッセージ
QMC 管理者がハブでカスタム バナー メッセージを公開するためのサポートが追加されました。バナーを使用して、今後の発表や重要な情報を組織に通知します。 標準、情報、警告、エラーの4 種類のバナーがサポートされています。必要に応じて、バナーの期間を設定できます。デフォルトの期間は 10 秒です。
ADS/HDS のプロキシ設定における HTTP ユーザー認証の設定に対応
ADS/HDS のプロキシ設定で、ユーザー IDとパスワードを含めることができるようになりました。詳細については、Qlik Sense Enterprise SaaS を使用した Qlik ADS および HDS 通信のプロキシを構成するを参照してください。
キー |
タイトル |
説明 |
QB-6397 |
Qlik Engine: Excel にエクスポートするときに、ピボット テーブルの列の形式に誤りがある |
ピボット テーブルを Excel にエクスポートするときに、同じ名前の列が誤った形式になる問題を修正しました。 |
QB-8087 |
空の値でフィルタリングすると、オンデマンド レポートが失敗する |
空の値が選択されたときに、qlik-on-demand-reporting 拡張機能がレポートの生成に失敗する問題を修正しました。Qlik NPrinting May 2022 SR2 以降のバージョンが必要です。 |
QB-8632 |
Qlik Engine: 最近公開されたシートで「オブジェクトが見つかりません」というエラーが発生する |
最近公開されたシートで「オブジェクトが見つかりません」という結果になる場合の、オブジェクトの持続性の競合状態を修正しました。 |
QB-9058 |
Qlik Sense: 同じカスタム プロパティ値を複数回適用できる |
QMC または API リクエストを介して、同じカスタム プロパティ定義に属する同じカスタム プロパティ値を、同じリソースに複数回適用できる問題を修正しました。 |
QB-9515 |
Qlik Sense Enterprise コネクタ: MySQL コネクタでのリロードによる結果に誤りがある |
MySQL コネクタの Bulk Reader モードで、日付フィールドが NULL の場合にテキスト値の読み込みで発生していた問題を修正しました。 |
QB-9584 |
Salesforce コネクタ用「私のドメイン」のサポートを追加 |
my.salesforce.com でご自身のプライベート サブドメインが使用できるようになりました。https://help.salesforce.com/s/articleView?id=sf.faq_domain_name_what.htm&type=5 を参照 |
QB-10425 |
新しい X-Qlik-Session クッキーの取得に、SAML 応答を使用可能 |
SAML リプレイ リクエストで新しい X-Qlik-Session クッキーが生成される問題を修正しました。この修正により、使用された SAML アサーション ID がメモリに保存され、リプレイ攻撃によって「400 Bad Request」エラーが発生し、Audit_Proxy ログに「SAML リプレイがアサーション ID: <id> で検出されました」という警告が表示されます。 |
QB-10558 |
Qlik Sense ビジュアライゼーション: コンテナ チャートのデータを表示すると、誤ったデータが表示される |
異なるデータを使用する 2 つのチャートを含むコンテナで [データの表示] オプションを使用すると、最初のチャートのデータのみが表示されていました。この問題は修正され、選択したチャートと一致するデータが表示されるようになりました。 |
QB-10629 |
スケジューラー: タスクのリロードが「トリガー済み」の状態で止まってしまう |
カスタム トリガーが正しく設定されていない場合に、スケジューラー サービスがアクティブの状態に移行できない問題を修正しました。この問題は、例外をキャッチして System_Scheduler ログに警告メッセージを記録することで解決しました。 |
QB-10681 |
Qlik Sense ビジュアライゼーション: 表示条件を含むテーブルを Excel にエクスポートするときに問題が発生する |
テーブルに表示条件が含まれる場合に、Excel へのテーブルのエクスポートが破損する問題を修正しました。この問題は、列の表示または非表示を正しく確認することで解決しました。 |
QB-10763 |
Qlik Oracle コネクタ: XML 要素関数のエラー |
ODBC Connector Package Oracle データソースのクエリで XmlElement 関数を使用すると、エラー (ORA-00907: 右カッコがありません) が発生するバグを修正しました。 |
QB-10772 |
ビジュアライゼーション: 「新しいリクエスト リンクの作成に失敗しました」というエラーで、ODAG レポートの生成に失敗する |
整数以外の数式の値によって、ODAG レポートの生成に失敗する問題を修正しました。 |
QB-10783 |
ブレット チャートのカステム テーマが機能しない |
ブレット チャートのカスタム テーマに関する問題を修正しました。 |
QB-10810 |
Qlik Sense ビジュアライゼーション: X 軸のラベルが消える |
ズーム機能で 90% にすると、チャートの X 軸ラベルが消える問題を修正しました。 |
QB-10843 |
ビジュアライゼーション: コンテナ内のチャートにプロパティを適用できない |
チャートから代替の軸を削除できない問題を修正しました。この問題の原因は、プロパティ間の不一致によるものでした。修正によりダイアログが表示され、変更を適用できるようになりました。 |
QB-10846 |
ビジュアライゼーション: モバイル デバイスでコンテナ チャートに余分なスペースが表示される |
選択したチャートがコンテナ オブジェクトに割り当てられたスペースよりも少ないスペースを使用した場合、モバイル デバイスで余分なスペースが表示される問題を修正しました。 |
QB-10859 |
Qlik Sense ビジュアライゼーション: テーブル形式のデータを Excel にエクスポートするときに問題が発生する |
エクスポートされたテーブルで、日付、デュアル値、RGB カラー コードなどの形式が失われる問題を修正しました。 |
QB-10874 |
Qlik Cloud ビジュアライゼーション: マッシュアップ使用時に product-info.json ファイルでコンソール エラーが発生する |
クラウド マッシュアップで静的ファイルを取得するときに、コンソール エラーの原因となる CORS に関連する問題を修正しました。 |
QB-10936 |
Qlik Sense License Monitor: データ接続が失われる |
License Monitor で一部のデータ接続が失われる問題を修正しました。デフォルトのデータ接続が復元されました。 |
QB-10937 |
Qlik Cloud Enterprise コネクタ: DynamoDB によりテーブル レベルのアクセスが制限される |
AWS ポリシーによりテーブルへのアクセスが制限されている場合に、コネクタが失敗する問題を修正しました。 |
QB-10963 |
アイテムが表示されるようにダイナミック ビューを修正 |
ダイナミック ビューに「アイテムなし」というメッセージが表示されます。 |
QB-10967 |
Qlik Sense Engine: 一部のアプリで「無効なビジュアライゼーションです」のエラー メッセージが表示される |
Qlik Engine から不完全なレイアウト データが渡され、「無効なビジュアライゼーションです - ビジュアライゼーションがサーバーにありませんでした」というエラー メッセージが表示される問題を修正しました。この問題は、組み込みビジュアライゼーションでも発生していました。 |
QB-10972 |
フィールドの名前が「not」の場合、データをロードできない |
「not」という名前のデータ フィールドは、角括弧 ([]) または二重引用符 ("") で囲むことによりロードできるようになりました。 |
QB-11033 |
Qlik Sense ビジュアライゼーション: テーブル オブジェクトのテキスト ラップが機能しない |
テーブルの行がセル内のすべてのテキストを表示し、テーブルが不要に大きくなる問題を修正しました。この問題は、デフォルトの行の高さ制限を 3 行のテキストに戻すことで解決しました。 |
QB-11144 |
Qlik Sense QMC: ステータスの値が重複する |
ステータス フィルター リストで、「キューに登録済み」と「開始済み」ステータスに値が重複して表示される問題を修正しました。 |
QB-11232 |
Qlik Sense ビジュアライゼーション: 軸の値レベルでのドリルダウン軸の選択 |
軸の値が 1 つしか残っていない場合に、軸の値ラベルに表示されるドリルダウン軸の選択の問題を修正しました。 |
QB-11236 |
Qlik Cloud アラート サービス: ラベルがない場合、アラートの作成が機能しない |
アラートが作成されない問題を修正しました。この問題の原因は、角括弧で囲まれたラベルがラベルとして扱われないことでした。 |
QB-11239 |
Qlik Sense Hub: ハブの「お気に入り」セクションに、初期状態ではすべてが表示されない |
他のユーザーが所有し異なるストリームに属するアプリを、ハブが取得するのに時間がかかる問題を修正しました。これにより、アプリの「お気に入り」セクションにすべてのアプリが表示されないようになりました。 |
QB-11248 |
ストーリーテリング ビューに、ドロップダウン フィルターが表示されたままになる |
分析ビューとストーリーテリング ビューの間を移動するときに、ドロップダウン フィルターがページに残っていました。この問題は修正され、開いているすべてのポップオーバーは分析ビューから移動する前に閉じられるようになりました。 |
QB-11294 |
Qlik Cloud 分析: [データからアプリを作成] でアプリに追加されたデータ ソースに対して、[ソースからデータを選択] が機能しない |
[ソースからデータを選択] オプションを使用するときに、新しいロード スクリプトでスペース名が定義されず、内部エラーが発生する問題を修正しました。[ソースからデータを選択] オプションは、正常に機能するようになりました。 |
QB-11365 |
カスタム ツール ヒントでパラメーターが無効というエラーが発生する |
カスタム ツール ヒントを含む複数のレイヤーがある場合、パラメーターが無効になるエラーが修正されました。 |
QB-11384 |
Qlik Sense ビジュアライゼーション: Qlik-animator ID が、サービスを起動するたびに変更される |
マニフェストとパッケージ JSON ファイルのバージョン番号が不一致になる問題を修正しました。問題の修正により、Qlik animator サービスは別のものと見なされ、サービスを再起動するたびに再インストールされるようになりました。 |
QB-11555 |
ビジュアライゼーション: モバイル ブラウザーの選択ツール バー メニューで問題が発生する |
ランドスケープ モードのときに、モバイル ブラウザーの選択ツール バー メニューが切れる問題を修正しました。 |
QB-11556 |
コンボ チャートの凡例の位置が正しくない |
解像度とチャート サイズの特定の組み合わせに応じた、コンボ チャートの凡例の位置に関する問題を修正しました。 |
QB-11559 |
タッチ デバイスのチャートで、スクロール バーのサイズが異なる |
タッチ デバイスでの棒グラフおよびブレット チャートにおける、スクロール バーのサイズに関する問題を修正しました。 |
QB-11580 |
Qlik Sense ビジュアライゼーション: コンボ チャートの軸に常に 0 が含まれる |
積み上げ棒を使用したコンボ チャートで、棒のある軸だけではなく、両方の軸に 0 が含まれる問題を修正しました。 |
QB-11591 |
棒グラフに 7 月のラベルがない |
2 次元グループの棒グラフのデータに関する問題を修正しました。 |
QB-11685 |
GeoAnalytics: マップ オブジェクトが無限ロード状態のままになる |
ライン/ポリゴン機能が正しく終了されていない場合、GeoJSON データ プロパティが埋め込まれたマップ オブジェクトが無限ロード状態のままになる問題を修正しました。この修正により、JSON 解析エラーに対応するようになりました。 |
QB-11740 |
Qlik Cloud ビジュアライゼーション: 編集後にマスター アイテム ラベルが更新されない |
マスター アイテムが複製され、リンクが解除され、マスター アイテムとして再度追加された場合、ラベルを編集してもビジュアライゼーションで更新されませんでした。この問題を修正しました。 |
QB-11745 |
General Web Connector の SaveToDisk テーブルで正規表現フィルターが適用されない |
General Web Connector の SaveToDisk テーブルを修正し、指定された正規表現フィルターが適切に適用されるようになりました。 |
QB-11759 |
Qlik Cloud Enterprise コネクタ: BulkReader で大きな文字列を処理できない |
BulkReader モードで、文字列の最大制限が誤って 4096 文字になっていた問題を修正しました。 |
QB-11803 |
Qlik データ ゲートウェイ - 直接アクセス: Oracle Wallet が動作しない |
Oracle Wallet に関する問題を修正しました。 |
QB-11818 |
Qlik Sense: OIDC 経由の認証に失敗する (「400 Bad Request」) |
仮想プロキシ設定で、[OIDC オプションの属性を無効化] オプションがアクティブになっている場合にオプション属性のいずれかに空の値があると、OIDC 経由の認証に失敗する問題を修正しました。 |
QB-11843 |
Qlik Sense ビジュアライゼーション: コンボ チャートの凡例が正しく折り返されない |
カテゴリの凡例のテキストが一部正しく折り返されない問題を修正しました。 |
QB-14086 |
GeoAnalytics: 座標を使用したチャート レイヤーのカスタム ツール ヒントで問題が発生する |
場所の座標を使用しているチャート レイヤーで、カスタム ツールヒントが表示されない問題を修正しました。 |
QB-14196 |
Qlik Engine: CrossTable プレフィックスを使用した QVD LOAD がクラッシュする |
CrossTable プレフィックスを使用した QVD LOAD が不定期にクラッシュする問題を修正しました。 |
QB-14280 |
Qlik Sense on Windows: ライセンス アクセス タイプの割り当て時に、userId および userDirectory プロパティで大文字と小文字が区別される |
userId プロパティに大文字が含まれている、または userDirectory プロパティに小文字が含まれている場合、ライセンス アクセス タイプの割り当てに失敗していました。リポジトリ サービスは「201 Created」が「null」で返され、QSRデータベースの対応するテーブルに割り当てが即座に保存されませんでした。この問題は解決されました。 |
QB-14297 |
Qlik Sense Engine: NLU_MUILTI_LINGUAL を有効にすると、オランダ語パーサー (NL) が起動しない |
Qlik Sense Enterprise on Windows で多言語の自然言語クエリを有効にすると、NL パーサーが起動しない問題を修正しました。 |
QB-14316 |
カスタム スケジュール トリガーに、カスタム値ではなく既定値が表示される |
対応するリロード タスクに変更が適用されるまで、カスタム トリガーに既定値が表示される問題を修正しました。 |
QB-14326 |
On-Demand アプリ: ナビゲーション ポイントのプロパティが表示されない |
On-Demand アプリでナビゲーション ポイントのプロパティが表示されるようになりました。 |
QB-14353 |
Qlik Sense QMC: QMC で未定義の「userId」エラーが発生する |
管理者が QMC をロード時に未定義の「userId」エラーが発生する問題を修正しました。 |
QB-14484 |
Qlik Cloud Engine: アプリをリロード時にスクリプト以外の変数の値が保持されない |
API 関数 SetStringValue、SetNumValue、SetDualValue を使用してセッション内で変更されたすべての変数値が、別のセッションでアプリをリロードするときにリセットされる問題を修正しました。このリリースでは、スクリプトで定義されていない変数は、SetStringValue、SetNumValue、SetDualValue を使用してエンド ユーザーのセッションで設定された値を、アプリのリロード時に保持します。 |
QB-14494 |
Qlik Sense ビジュアライゼーション: [編集] シートで変数ダイアログを開いているときに、チャートが誤って削除される |
変数ダイアログを開いた状態で削除キーを押すと、バックグラウンドで誤ってチャートが削除される問題を修正しました。この問題は、変数ダイアログが開いている間はグリッドをブロックし、閉じたらブロックを解除することで解決しました。 |
リリースの時点で確認されている問題と制限事項は次のとおりです。この一覧はすべてを網羅するものではありませんが、既知の主要な問題と制限事項はすべて取り上げられています。
回避方法: ナビゲーション メニューでタッチ モードをオフにします。
ダイナミック ビュー
アセット パネルで新しいダイナミック ビューを作成するときに、既存のダイナミック ビューがある場合、ドロップダウン メニュー アイテムは自動的に変更されず、新しく作成されたダイナミック ビューの
コネクタ
Qlik Sense の要件については、オンライン ヘルプの「Qlik Sense のシステム要件」を参照してください。
Qlik について
Qlik は、データを活用して誰もが困難な課題を解決できる、高度なデータリテラシーを備えた社会を実現するという使命を負っています。Qlik ならではの、エンドツーエンドのデータ管理および分析プラットフォームを利用することで、組織はソースを問わずあらゆるデータを統合し、どんなスキル レベルの従業員でも好奇心を発揮して新しい洞察を獲得できるようにすることができます。企業は Qlik を利用することで、顧客の行動をさらに深く理解し、ビジネス プロセスを改革し、新たな収益源を発掘し、リスクと報酬のバランスをとることができます。Qlik は、世界 100 か国以上でビジネスを展開し、48,000 社以上のお客様にご利用いただいています。
qlik.com
Table of Contents
The following release notes cover the versions of Qlik Sense released in August 2022.
Please refer to the What’s new sections of the online help for information about the new and updated features of the Qlik Sense Enterprise on Windows August 2022 release:
What's new in Qlik Sense August 2022 (Users)
What's new in Qlik Sense August 2022 (Developers)
What's new in Qlik Sense August 2022 (Administrators)
August 2022 Patch 2
Google BigQuery connector: Update in the OAuth flow for the User Authentication mechanism, due to the deprecation of OAuth out-of-band (oob) flow by Google. This change requires reauthentication of existing connection definitions.
August 2022 Patch 5
Patch policy for Qlik Sense Desktop has been updated. Please see “Latest release and patch” in download app for the latest Qlik Sense Desktop. All corrective content will be available in the latest patch of Qlik Sense Desktop.
August 2022 Patch 6
Key | Title | Description |
QB-17347 | Qlik Sense Hub: Apps not shown under Favorites when using non-English language | Fixed an issue where apps did not appear under Favorites unless you navigated back and forth. The issue occurred when using a non-English language in the Hub. The Favorites section is now refreshed for all languages when all app streams are loaded. |
QB-16918 | Qlik Sense Engine: Lost data rows when importing delimited UTF-16 encoded files | Fixed a problem that caused embedded NUL (binary 0) characters in delimited UTF-16 encoded files, such as CSV, to be ignored during import, resulting in an incomplete data set. |
QB-16816 | Qlik Sense Visualizations: Action button background image not shown | Fixed a problem where images on action buttons were not displayed correctly. The button now checks and works with multi-noded prefixes. |
QB-9058 | Qlik Sense: Possible to apply same custom property value more than once | Fixed an issue where it was possible via QMC or API request to apply the same custom property value belonging to the same custom property definition more than one to the same resource. |
August 2022 Patch 5
Key | Title | Description |
QB-16853 | Qlik Sense: Updated Node.js | Updated Node.js to address a third-party issue (CVE-2022-43548). For more information, visit https://nodejs.org/en/blog/vulnerability/november-2022-security-releases/. |
QB-15055 | Qlik Sense Scheduler: Triggered tasks not running at expected scheduled time | Fixed a problem where the scheduler services did not run properly if there were errors in the user-created cron expressions. We solved this by creating more controls and marking any problematic user entry in the scheduler error log file and ignoring that trigger until the user resolves the issue. |
QB-14348 | Qlik Sense Engine: Mashup application hangs | Fixed a problem where a mashup application would hang when applying selections. |
QB-14264 | Qlik Sense Mobile: Lost connection on iOS | Fixed a problem where the connection was lost after minimizing the browser window and switching to other applications. |
August 2022 Patch 4
Key | Title | Description |
QB-14958 | Qlik Sense Visualizations: Page Unresponsive when selecting a sheet through the sheet dropdown menu | Fixed a problem that caused pages to become unresponsive and trigger a "Page Unresponsive" error when selecting a sheet through the sheet dropdown menu. |
QB-14951 | Qlik Sense Visualizations: Incorrect numerical abbreviation in Scatter Plot using "Auto" | Fixed a problem where using "Auto" in the chart configuration for the x or y axis showed an incorrect format in Scatter Plot charts. |
QB-14890 | Qlik Sense Visualizations: Overwrite option for ODAG app not working | Fixed a problem where the "Overwrite generated apps" for ODAG did not work and triggered the warning message "Maximum number of generated apps reached". The overwrite option now works as expected and a newly generated app overwrites the existing ODAG app without a warning message. |
QB-14649 | Qlik Cloud Engine: Problem with qualifiers in aggregations | Fixed a problem where aggregation qualifiers (such as total and distinct) were not considering the outer set analysis prescribed by the expression. This has been solved, and all calculations with outer set analysis notation yield correct results. |
August 2022 Patch 3
Key | Title | Description |
QB-11559 | Scrollbar size differs between charts on touch devices | Fixed an issue with the scrollbar size in bar charts and bullet charts on touch devices. |
QB-11555 | Visualizations: Problem with the selection toolbar menu on mobile browsers | Fixed a problem that cut off the selection toolbar menu on mobile browsers when in landscape mode. |
QB-10846 | Visualizations: Container charts show extra spaces on mobile devices | Fixed a problem where extra white space is visible on mobile devices if the selected chart uses less space than allocated for the container object. |
August 2022 Patch 2
Key | Title | Description |
QB-14353 | Qlik Sense QMC: Undefined "userId" error in the QMC | Fixed a problem where administrators would get an undefined "userId" error when loading the QMC. |
QB-14297 | Qlik Sense Engine: Dutch parser (NL) is not starting when enabling NLU_MUILTI_LINGUAL | Fixed a problem that prevented the NL-parser from starting when enabling multi-language natural language queries in Qlik Sense Enterprise on Windows. |
QB-11818 | Qlik Sense: Authenticating via OIDC fails ("400 Bad Request") | Fixed a problem where authentication via OIDC would fail if any of the optional attributes had an empty value when "Disable OIDC optional attributes" option was active in Virtual proxy settings. |
QB-11759 | Qlik Cloud Enterprise Connectors: BulkReader cannot process large strings | Fixed a problem where BulkReader mode had an incorrect max string limit of 4096 characters. |
QB-11232 | Qlik Sense Visualizations: Drill down dimension selection on a dimension value label | Fixed an issue with the drill down dimension selection that appeared on dimension value labels when there was only one dimension value left. |
QB-10967 | Qlik Sense Engine: "Invalid visualization" error message shown on some apps | Fixed a problem where incomplete layout data was being passed from the Qlik Engine, resulting in the error message "Invalid visualization - The visualization was not found on the server" being shown. This occurred even for built-in visualizations. |
QB-10681 | Qlik Sense Visualizations: Problem when exporting tables with show condition to Excel | Fixed a problem where table exports to Excel were corrupt when tables used show condition. This was solved by correctly checking if a column is shown/hidden. |
QB-9515 | Qlik Sense Enterprise Connectors: Wrong results via reload with MySQL connector | Fixed a problem in the loading of text values when date filed is NULL in Bulk Reader mode for MySQL connector. |
QB-8632 | Qlik Engine: Recently published sheets can have an "Object not found" error | Fixed a race condition in object persistence that sometimes resulted in "Object not found" for recently published sheets. |
August 2022 Patch 1
Key | Title | Description |
QB-11350 | Visualizations: Cannot change order of dimensions/measures by drag-and-drop when using table extensions | Fixed a problem that prevented the ordering of dimensions/measures in extensions using an older API ("uses: dimension" and "uses: measures"). |
QB-11033 | Qlik Sense Visualizations: Text wrap on table objects not working | Fixed a problem where table rows were displaying all text in cells, causing unnecessarily large tables. This was resolved by restoring the default row height limit of 3 rows of text. |
QB-10963 | Fixed dynamic views to show items | Fixed dynamic views to show items |
QB-10843 | Visualizations: Cannot apply properties to charts in containers | Fixed a problem that prevented removing an alternate dimension from the chart. This was caused by a mismatch between the properties. A dialog is now displayed, so changes can be applied. |
QB-10810 | Qlik Sense Visualizations: X-axis labels disappear | Fixed an issue that caused the X-axis label on charts to disappear when zoomed to 90%. |
QB-10789 | Data connections: Could not load NCLOB or CLOB data types when connecting to Oracle DB | Fixed an issue where scripts failed to load field type NCLOB or CLOB when connecting to Oracle DB. |
QB-10772 | Visualizations: ODAG report generation fails with error "Failed to create new request link" | Fixed a problem where non-integer expression values were causing the ODAG report generation to fail. |
QB-10763 | Qlik Oracle connector: Error in XML element function | Fixed a bug where using the XmlElement function in queries of the ODBC Connector Package Oracle datasource caused an error (ORA-00907: missing right parenthesis). |
QB-10558 | Qlik Sense Visualizations: View Data for container chart shows incorrect data | In a container with two charts using different data, the View data option showed only the data for the first chart. This issue has been fixed, and the data shown now matches the selected chart. |
August 2022
Key | Title | Description |
QB-7033 | Qlik Sense Enterprise Connectors: MongoDB query filter ‘WHERE’ clause not working as expected | Fixed a problem in which the 'WHERE' clause query filter was failing to load data from MongoDB. The issue was fixed with the latest mongo driver update - 2.3.19.1021. |
QB-8050 | Scheduler: Operations Monitor app does not show new reloads | Fixed a bug that altered the structure of the scheduler service logs, making them incompatible with the data load model of the Operations Monitor app. To inspect reload activity from the affected period, use the Reloads Monitor app. |
QB-8796 | Qlik Sense Licensing: License monitor fails when analyzer capacity time has been exceeded | Corrected the logic used for the evaluation of analyzer capacity license consumption in the License Monitor app. |
QB-9324 | Qlik Sense: Issue when applying selections within a container | Fixed an issue with applying selections within a container after upgrade to Qlik Sense November 2021. |
QB-9325 | GeoAnalytics: Line layer failed to draw lines with lat lon on two dimensions | Fixed an issue where the line layer failed to draw lines when using latitude and longitude with two dimensions. |
QB-9456 | Security issue with jQuery UI 1.12.1 | Upgraded jQuery UI from 1.12.1 to 1.13.1 to avoid a security issue. |
QB-9584 | Add "My domain" support for Salesforce connector | You can now use your private subdomain in my.salesforce.com. See https://help.salesforce.com/s/articleView?id=sf.faq_domain_name_what.htm&type=5 |
QB-9596 | POST "/qrs/license/<Analyzer|Professional>AccessType" method for assigning license access not working as expected | The issue has been fixed and "userId" and "userDirectory" (in addition to the user's "id" in GUID format) are now mandatory fields to be included in the body of the request. If the fields are missing, the repository service will now throw "The repository detected an invalid property of the following type: user with EMPTY userId or userDirectory" error. |
QB-9654 | Master item not working when used in drill-down | Fixed an issue with handling group dimensions with reference to master items. |
QB-9704 | Background color on pivot table is not working consistently | Fixed an issue with uncalculated attributes in pivot tables. |
QB-9713 | Qlik Sense: Pivot table sometimes displays incorrect background color | Fixed an issue where the pivot table would sometimes display incorrect background color when scrolling up or down. |
QB-9748 | Qlik Sense: Cannot scroll back up when scrolling in a straight table | Fixed an issue where it was possible to scroll outside of the table area. This happened when the row height of the last table row was bigger than the height of the table body. |
QB-9759 | Qlik Engine: "Always one selected" disappears after reload | Fixed a bug that causes the "Always one selected" value to be lost upon reload. Contradictions caused the selection state to be reset. |
QB-9772 | Qlik Sense: Excel exports return "undefined" and file can't be opened | The issue was caused by an undefined grand total value. This has been fixed. |
QB-9797 | Task status is not updated for apps | Fixed an issue where the task status in 'App: associated items' was not updated. |
QB-9881 | Qlik Sense table throws errors in mashup | Fixed an issue where console errors were seen when a table was used on a mashup page. |
QB-9908 | Qlik Engine: Buffered QVD removed during reload | Fixed a bug that deleted a buffered QVD during reload. Caused by a faulty file path check. |
QB-9918 | Qlik Sense Visualizations: Charts in containers were triggering an error | Fixed a bug that would trigger an "Invalid Hypercube Object" error when toggling between different chart types in a Container. |
QB-9955 | Tooltip missing for toggle lasso selection icon | Fixed an issue where the tooltip for the toggle lasso selection icon was missing in pie charts. |
QB-9964 | Risk of information disclosure using /api/engine/sessions API | This issue has been fixed by hiding the /sessions endpoint behind a flag. The endpoint is disabled by default and can be enabled by setting the ExposeSessionsEndpoint flag to 1 in engine INI. |
QB-9967 | Information disclosure in response to "/qrs/systemrule/security/audit/export" API | The response to "/qrs/systemrule/security/audit/export" no longer discloses sensitive information. The file location now points to "%Temp Location%". |
QB-10003 | Issue with information disclosure using the "ComputerName()" method | Fixed the issue by blocking Computername and EngineVersion when BlockSystemInfo ini-int is set to 1. |
QB-10013 | Qlik Engine: Bookmarks with saved layouts could cause slow interactions | Fixed a problem that caused bookmarks saved with layouts to increase in size when shown in a list, resulting in the browser not being able to show the list. |
QB-10051 | Qlik Sense Hub: Improper error handling for "api/hub/v1/apps/stream/" request | Fixed a problem that resulted in unnecessarily verbose error messages. |
QB-10171 | Reload script is executed successfully but app save fails | Added a retry mechanism where a locked transaction file would cause Engine to fail when saving the app. Affected areas: - Autosave - API: DoSave - API: DoSaveEx Note that when the saving sometimes takes a bit longer to complete, this could be the retry mechanism waiting for the file to get unlocked for writing (10 ms for each retry). |
QB-10174 | Issue with notification setup when several websockets have opened the same app | When several websockets open the same app event, registration of notifications like publish and unpublish is set up and torn down appropriately. |
QB-10280 | Qlik Engine: Not all published apps open after encryption certificate is changed | Fixed a bug that prevented some published apps from opening after a new encryption certificate was used. When the encryption certificate is now changed, all objects in the app are re-encrypted upon the first save or reload, removing any reference to the old certificate. |
QB-10390 | Filter pane does not show expected items | Fixed an issue with fixed filter panes. When a user was typing as slow speed, the filter pane didn't show correct results. This has now been resolved. |
QB-10416 | Filter pane search highlight doesn't work with ceratain characters | Fixed the highlight when using the filterpane and the entered search value included certain characters, for example, colon ':'. |
QB-10460 | "/qrs/license/requestaccesstype" takes long time to complete with large number of SAML groups | Fixed the issue by improving the parsing mechanism of values included in the "X-Qlik-ExtendedUser" header. |
QB-10481 | The button object doesn't display images in a mashup | Fixed the issue by using the correct URL for the button object in mashup situations. |
QB-10576 | Qlik Cloud Enterprise Connectors: Salesforce connection error "My domain cannot be empty" | Fixed a bug that would throw an error during data reload, stating that "My domain cannot be empty". |
QB-10670 | Qlik Sense Licensing: Offline Signed License Definition (SLD) did not work | Fixed an issue where Signed License Definition (SLD) tried to fetch information in offline mode if the delayed sync had expired. |
QB-10692 | Qlik Engine: Risk of corrupting the state of thread locks due to stalling engine | Resolved an issue where the engine was stalling when checking for changes to Settings.ini. |
QB-10693 | Qlik Sense Hub: Stream overview does not initially load all available streams | Fixed a problem that prevented some streams from initially loading in the hub. |
SHEND-1007 | Update Node.js | Updated Node.js to address third-party issue CVE-2022-32223. For more information, see https://nodejs.org/en/blog/vulnerability/july-2022-security-releases/ |
QB-11144 | Qlik Sense QMC: Duplicate status values | Fixed an issue where 'Status' filter list would show duplicate values for 'Queued' and 'Started' statuses. |
QB-11239 | 'Favorites' section in the hub does not initially show all apps | Fixed a problem that caused the 'Favorites' section in the hub to initially not show all apps. This required users to wait for a few seconds and then browse back and forth to Favorites section for all apps to appear. We solved this problem by adding an auto refresh that loads all apps without having to browse back and forth to Favorites section. Note that a few seconds delay might still be observed for all the apps to appear in the Favorites section. |
The following issues and limitations were identified at release time. The list is not comprehensive; it does however list all known major issues and limitations.
Exporting a story to PowerPoint limitations
ODBC connector: If the user name on the Microsoft Windows system running Qlik Sense Desktop contains letters that are not English alphanumeric characters, database connectors in the ODBC Connector Package do not work properly. Workaround: Change the Windows system locale to match the character set that contains the characters used in the user name. For example, if the system locale on the system running Qlik Sense Desktop is set to English and a user name contains Swedish characters, the System locale setting must be changed to Swedish for the ODBC connector to work properly
The Qlik Salesforce Connector does not support PK chunking on sharing objects. PK chunking is supported only on parent objects.
https://community.qlik.com/t5/Downloads/tkb-p/Downloads
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.
Table of Contents
The following release notes cover the versions of Qlik NPrinting released in May 2022 SR3.
Qlik Sense November 2022 is supported starting from this version.
Jira issue ID: OP-95775
The list of time zones was updated to IANA 2022e.
Jira issue ID: OP-95757
In reports generated from PowerPoint and HTML templates, Qlik Sense columns set as hyperlinks now work correctly.
In HTML templates you must add the tags like %%Link_Column%% directly and they will be automatically recognized as hyperlinks. In existing templates, tags like <a href="%%Link_Column%%">label</a> must be replaced.
Excel templates were not affected, hyperlinks were correctly generated.
Word templates were not affected, hyperlinks were correctly generated. Word templates will have improved performance thanks to this fix.
The value of the Keep Source Format option does not affect the hyperlinks.
The issue is only fixed for Qlik Sense connections.
Jira issue ID: OP-95774
PowerPoint reports generated from templates with native charts with the “Value From Cells” option set did not display the value from cells.
Jira issue ID: OP-95779 OP-95780
In some cases, reports generated from Qlik Sense connections had missing data.
Only Qlik NPrinting May 2022 SR2 was affected by this issue. Older versions work correctly.
QlikView connections were not affected.
Jira issue ID: OP-95784
A component used to send emails had a concurrency issue bug.I In some rare cases, emails were not sent when scheduled.
The following issues and limitations were identified at release time. The list is not comprehensive; it lists all known major issues and limitations. We expect to have these issues fixed in future versions.
The following languages are supported:
Other languages are not officially supported. There may be issues with other languages, particularly those with right-to-left script and non-Roman alphabets.
Qlik Sense custom size sheets are not supported. Custom size will not be maintained on export.
QlikView and Qlik Sense alternate states are not supported.
Jira issue ID: OP-6196
Qlik NPrinting Server, Engine, and Designer can only be installed on C: drives. Any attempt to install them on a different drive will result in task failures.
Jira issue ID: OP-5831
When you add the same object twice, using the Images node in Qlik NPrinting Designer, only the image size property of the first image is respected.
It is possible to select the “Enable” check box in On-Demand for reports using Qlik Sense app data. These reports are visible in the QlikView On-Demand menu of the QlikView On-Demand add-on. But if selected, they will not generate reports, and you will see an error message.
If you experience random crashes when using Qlik NPrinting Designer, open your Windows Display Settings in the Control Panel and verify that Smaller – 100% (default) is selected. When settings of 125% or 150% are selected, Qlik NPrinting Designer may crash.
Jira issue ID: OP-5908
In some cases, when you use Qlik NPrinting On-Demand in Internet Explorer 11 or Edge, the “origin” HTTP header is not generated. This results in the error message “REVEL_CSRF: tokens mismatch”.
The workaround is to install Qlik NPrinting On-Demand on a Microsoft IIS server hosting QlikView Access point or use a different web browser.
Jira issue ID: OP-4940
Qlik NPrinting Designer may be unable to open a report template if there are too many filters associated with a connection in the report's app. The following error message displays: “A task was canceled”.
This typically happens when more than 4000 filters are using fields from a connection. Sometimes, higher numbers can work. For example, 7000 filters have worked in some situations.
The workaround is:
1. Split the Qlik NPrinting app into separate apps.
2. Split the connections (possibly by using multiple connections to the same documents in different apps).
3. Split the filters across apps (so that the filter count per app is lower).
Jira issue ID: OP-4839
Some Qlik NPrinting tasks fail with the error message: “Exceeded maximum number of retries”. This is due to a performance issue in QlikView that appears when it exports large unfiltered files to Excel.
Jira issue ID: OP-5278
In some rare circumstances, pressing the Verify connection button will cause the screen to freeze on the “Initializing…” status and the spinning wheel cursor. This happens when a Qlik NPrinting Engine goes offline and Verify connection is pressed before the Qlik NPrinting Scheduler is aware that it is offline. It can take up to 20 seconds before the Qlik NPrinting Scheduler determines the offline status of a Qlik NPrinting Engine.
Jira issue ID: OP-5914
When you:
The filters associated with each user are not uploaded, or displayed, for performance reasons. Waiting for all filters for thousands of users to import would take a long time. In most cases, importing this information is unnecessary, because filters created for users often contain something like the user IDs. You can change this behavior and make all filters visible by uncommenting the line <!--<add key="include-user-filters" />--> in the webengine.config file.
To make a specific filter visible in the lists, remove its association to all users, or create a new filter with the same fields and values not linked to any user.
Jira issue ID: OP-3986
The rollback that follows a Qlik NPrinting Server or Engine upgrade cancellation may corrupt the related Qlik NPrinting installation. A rollback is triggered by errors or by clicking the cancel button during the upgrade execution. After a corruption caused by a rollback, services may be uninstalled or cannot be started.
To restore a Qlik NPrinting Server to its original status:
You should always create a backup before starting an update. In any case, a backup is automatically created in the folder "%ProgramData%\NPrinting" at the beginning of the upgrade process. To restore a Qlik NPrinting Engine to original status:
Jira issue ID: OP-7560
Add title functionality is not supported on Qlik Sense objects with Assistance mode enabled. The workaround to restore the Add title functionality is to disable Assistance mode for the chart in Qlik Sense. Then reload the metadata of the connection.
Jira issue ID: OP-7568
Qlik Sense objects made in Assistance mode cannot be used as tables, columns, or cells in Qlik NPrinting. To restore them, disable Assistance mode on the chart in Qlik Sense; then reload the metadata of the connection. Furthermore, if a Qlik Sense object made with Assistance mode is exported as a table, column, or cell using Qlik NPrinting APIs, the request will fail.
Jira issue ID: OP-7165
Open Type Fonts (*.otf) are not supported in PixelPerfect templates. Generated reports will use a different font, and not look as expected.
Jira issue ID: OP-7747
The following functionalities are not supported for Qlik Sense tables that have a "Show column if" condition set on one or more of their columns: levels, single column export, and keep source formats.
Jira issue ID: OP-8570
QlikView tables with more than 256 columns cannot be imported into Qlik NPrinting report templates. All Qlik NPrinting versions are affected by this limitation, including QlikView NPrinting 16.
Jira issue ID: OP-8382
Qlik Sense On-Demand reports with selections applied on calculated dimensions will fail. However, you can apply selections on dimensions based on Qlik Sense fields. The workaround is to move the formula to the load script and use the calculated fields to apply selections to your On-Demand reports.
Jira issue ID: OP-8985
Due to the internal way of exporting Qlik Sense histograms, you cannot add them to the Qlik NPrinting Designer Tables node. If you add a Qlik Sense histogram to the Tables node, you will not receive any errors or warning messages, but the exported data will be wrong.
Jira issue ID: OP-8921
QlikEntity reports support Qlik Sense objects with the following limitations:
Jira issue ID: OP-9087
You cannot embed an Excel worksheet in a PowerPoint report template. This will cause a Qlik NPrinting Designer crash. The workarounds are to insert the Excel worksheet without using the Qlik NPrinting Designer:
Jira issue ID: OP-9067
Dynamic views is a new Qlik Sense feature starting from June 2020.
If you connect Qlik NPrinting to a Qlik Sense app that contains a chart used to generate dynamic views, the chart and the containing sheet are excluded from the Qlik NPrinting connection cache and cannot be used in reports.
You can connect Qlik NPrinting to a Qlik Sense app containing dynamic views. However, after a dynamic view refresh, the connection will stop working.
Jira issue ID: OP-9628
Starting from November 2020, RabbitMQ Server (deployed as Qlik NPrinting Messaging Service) has been updated to version 3.8.3. RabbitMQ Server 3.8.3 has a new non-configurable internal limit. Message size cannot be higher than 512MB. Previous limit was 2GB. As consequence, you cannot generate Qlik NPrinting reports bigger than 512MB.
Jira issue ID: OP-9766
Excel worksheet print areas can contain more than one range if the generation of the report does not expand the print area. If it expands, you will see an error: “Invalid Cell Name”. For example, the default setting of the Expand Range option in a Qlik NPrinting table causes the print area to change during report production, and an error is received.
Jira issue ID: OP-9518
Using Cyrillic characters in the Search form of the Qlik NPrinting user interface is case sensitive.
Jira issue ID: OP-9995
The percentage “%” format is not kept in Excel reports when using QlikView 12.50 (12.50.20000) or newer due to a QlikView issue. You can solve this by upgrading to QlikView May 2021 SR2 (12.60.20200) or newer.
Jira issue ID: OP-95599
If you start a Run Verification on a connection to a QlikView document in QVF format, Qlik NPrinting cannot confirm whether the QlikView Desktop version installed locally on each Qlik NPrinting Engine is compatible with QVF file format. The check mark next to "QlikView can open the document" may be green, even if a version of QlikView that does not support QVF is installed. This is because verification only checks file permissions. If the installed QlikView Desktop does not support QVF format, metadata generation will fail.
Jira issue ID: OP-95682
QlikView objects with many different fields with exactly the same label are not supported. Duplicated labels cause an exception during the connection cache generation. To solve this issue, ensure that each field has a unique label.
To upgrade to Qlik NPrinting May 2022 SR3, you must start from one of the following versions:
If you have a version of Qlik NPrinting older than April 2018, you must upgrade to Qlik NPrinting April 2018 before you can upgrade to Qlik NPrinting May 2022 SR3.
If you have a version of Qlik NPrinting older than 17.3, you must first upgrade to Qlik NPrinting 17.3. Then you must upgrade to a version from April 2018 to May 2021 SR4 before you can upgrade to Qlik NPrinting May 2022 SR3.
If you are upgrading from a version older than February 2018, all metadata caches (QlikView and Qlik Sense) will be marked as "not generated". This is due to a breaking change in the format of the metadata cache. All connection caches must be regenerated before you can edit a template or create a new connection.
You must back up your data before you proceed. Data can become damaged if a problem occurs during the upgrade. If data is damaged, a backup is required to restore the repository. See: Backup and restore of a repository.
After backup, you must follow the instructions for upgrading on the help site page Qlik NPrinting upgrade.
If you are upgrading to May 2022 SR3 from September 2018 SR2 or older you must:
• Open port 4997 outbound on Qlik NPrinting Server and inbound on all Qlik NPrinting Engines.
• Reinstall all your Qlik NPrinting Engines and provide a password for certificate exchange.
• Open the Engine manager in the Web Console.
• Open the detail page for each Engine and send the certificate after inserting the same password you used during the engine’s reinstallation.
Qlik NPrinting Engines stay offline until the certificate exchange is performed. Older Engine versions cannot connect to a Qlik NPrinting May 2021 SR5 Server.
Setups are available at https://community.qlik.com/t5/Downloads/tkb-p/Downloads
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.
Table of Contents
The following release notes cover GeoAnalytics Data Package 21.12 (Release name: December 2021).
A complete change log can be found in the readme file included in the release zip file.
As of GeoAnalytics Data Package version 21.05, Admin codes are no longer supported in ip address lookup (will always return NULL).
Previous version of ip address lookup had some support for this.
More about the admin codes in this article:
IP-address-lookup-coordinates-and-admin-code
From GeoAnalytics Data Package 21.05 the satellite map uses a new domain to retrieve the tiles.
It has changed from from services.arcgis.com to ibasemaps-api.arcgis.com, so if you have a restrictive firewall you will need to whitelist this new domain for the satellite map to continue working.
Full instructions about upgrading to this data package can be found in the installation guide pdf, Section 10 (the installation guide can be found in the Attachments section of this document).
See the system requirements for GeoAnalytics Server.
Qlik GeoAnalytics Data Package 21.12 zip file can be found on the download page under the category "Qlik Data Analytics".
The installation guide is available as an attachment for this document.
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.
Table of Contents
The following release notes cover the versions of Qlik Connector for use with SAP NetWeaver, released in v8.0.2.
Note: All components are recompiled for new releases. It is recommended that you always update both the SAP and Windows systems. There is backwards compatibility to the SAP code, so it is possible to install the new release of the connector on Windows without installing the corresponding SAP transports. In that case, however, new functionality and bug fixes that are dependent on changes in the SAP code are not available. New features and bug fixes in Qlik Connector for use with SAP NetWeaver v8.0.2 that are dependent on changes in the SAP code are marked with: (Requires SAP transport update).
See below for the current backwards compatibility of the components of the connector package.
Installation process
The SAP Connectors installation process has been updated, in compliance with SAP regulations. Visit the Qlik Helpsite for further details:
https://help.qlik.com/en-US/connectors/Subsystems/SAP_Connectors_Help/Content/Connectors_SAP/Installation/Installing-the-connectors.htm
Deletion of records in Qlik database tables
If there is a need to perform the deletion at the same time as connector jobs are running, use the transaction /N/QTQVC/DELETE_SAFE (program /QTQVC/DELETE_TABLES_SAFE). The program can be executed anytime without affecting ongoing connector jobs since it does not delete records from the latest week. Read more in the Qlik Helpsite. (Requires SAP transport update).
SQL Connector
Jira issue ID: QB-10032
Description: Vulnerability during a code check of SAP transports - Missing security checks in Function Module ‘/QTQVC/SELECT_WIDE_FIELD’. (Requires SAP transport update).
Backup recommendations
Version 8.0.2 overwrites any previous version of the Qlik Connector for use with SAP NetWeaver.
It is important that you make a backup of the site before upgrading, to be able to recover the site if the upgrade fails.
Backwards compatibility
The following table shows the current backwards compatibility of the components of the connector package.
Connectors |
Windows files |
SAP transport (data extraction) |
SQL |
8.0.2 |
6.1.2 or later |
Bex |
8.0.2 |
7.0.5 or later |
SAP Query |
8.0.2 |
5.80 SR2 or later |
Report |
8.0.2 |
5.80 SR2 or later |
Extractor |
8.0.2 |
5.80 SR2 or later |
BAPI |
8.0.2 |
5.80 SR2 or later |
InfoProvider |
8.0.2 |
6.5.0 or later |
BW |
8.0.2 |
7.0.6 or later |
https://community.qlik.com/t5/Downloads/tkb-p/Downloads
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.
Table of Contents
The following release notes cover the standalone version of Qlik Web Connectors released in June 2022, patch 2 released in October 2022.
The following updates have been made to the Qlik Web Connectors Core and Web UI as well as the connectors listed since Qlik Web Connectors June 2022 Patch 1 Release (2.130.1).
Qlik General Web Connector
TLS 1.3 Support
Qlik AYLIEN Text Analysis Connector
See the separate release notes with details on the updates added in Qlik Web Connectors June 2022 and Qlik Web Connectors June 2022, Patch 1.
IP v6 addresses are not supported when entering an IP v6 address for the purpose of white listing.
Load Balancing is not supported.
Qlik Web Connectors requires .NET Framework 4.8 (previously 4.7.2).
The new Qlik Web Connectors release package is available from the Qlik download site, under the Value Added tab.
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.
Table of Contents
The following release notes cover the versions of Qlik GeoAnalytics Plus released in November 2022. Resolved defects and limitations for Qlik Sense Enterprise on Cloud Services are also listed.
No Changes
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.
Table of Contents
The following release notes cover the versions of Qlik GeoAnalytics for QlikView, QliK Sense released in November 2022. Resolved defects and limitations for Qlik Sense Enterprise on Cloud Services are also listed.
No Changes
Layers throw error when destroyed in some situations
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.
Table of Contents
Learn about new features and improvements in Qlik Replicate.
This section describes the issues that you may encounter when upgrading/migrating to the new version.
Qlik supports four Replicate versions (including this one).
Direct upgrade is supported from the last two versions only (including any service releases for those versions). The last two versions are Replicate November 2021 and Replicate May 2022.
If you are upgrading from Replicate April 2020 (6.6), you need to perform the following upgrades:
If you are upgrading from Replicate 6.x (starting from 6.3), you need to perform the following upgrades:
Note: If you are upgrading from Replicate 5.5, please contact Qlik Support.
After upgrading, customers that are using Replicate's self-signed certificate (i.e. instead of their own certificate) should perform the following procedure:
This will cause Replicate to generate a new self-signed certificate, thereby ensuring that the certificate will be accepted by newer clients (browsers) that select the more secure TLS 1.3 protocol.
Note that if you do not perform the above procedure, the following error will be encountered when connecting to Replicate Console:
SYS,GENERAL_EXCEPTION,The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
When upgrading a Replicate installation with multiple Data folders, only the default Data folder (<Product_Dir>\Data) will be automatically upgraded. The other Data folders need to be updated manually by running the following command:
repuictl.exe -d <data_folder_path> setup install
Replicate November 2022 is compatible with the following related products only:
This section provides information about End of Life versions, End of Support features, and deprecated features.
Support for the following source endpoint versions has been discontinued:
Support for the following target endpoint versions has been discontinued:
The following endpoints are no longer supported:
Qlik Cloud Landing target
The functionality provided by the Qlik Cloud Landing endpoint has been superseded by Data Integration Services. For more information on Data Integration Services, see https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/DataIntegration/Introduction/Data-services.htm
From Replicate May 2023, support for installing Replicate on Red Hat 7.x will be discontinued. The minimum supported version will be Red Hat 8.x.
The Backup folder preprocessing command option has been removed from the Microsoft SQL Server source endpoint. From this version, it can only be accessed using an internal parameter.
This section lists the newly supported database versions and third-party software versions.
The following source endpoint versions are now supported:
The following target endpoint versions are now supported:
Vertica 11.x
Note: First introduced in Replicate May 2022 Service Release 2.
This version introduces support for running Replicate on Windows Server 2022.
Note: First introduced in Replicate May 2022 Service Release 2.
This section lists the known issues for the November 2022 initial release.
Jira issue: RECOB-5913
Salesforce case: 46218
Type: Issue
Component/Process: MariaDB Source
Description: A CREATE DDL change starting with comment line will not be captured.
Jira issue: RECOB-5597
Salesforce case: 37728
Type: Issue
Component/Process: MySQL Source
Description: DDL changes in special formats are sometimes not captured during CDC.
Jira issue: RECOB-6152
Salesforce case: 12867
Type: Issue
Component/Process: Microsoft Azure Databricks Target
Description: The number of replicated records does not always correlate with the number of source records.
Jira issue: RECOB-6181
Salesforce case: 29650
Type: Issue
Component/Process: SAP Extractor Source
Description: The SAP Extractor endpoint sometimes activates an extractor job that is not part of the CDC task.
Jira issue: RECOB-5987
Salesforce case: N/A
Type: Issue
Component/Process: Salesforce Source
Description: Replicating a large umber of tables sometimes causes the task to restart with a recoverable error.
Jira issue: RECOB-5911
Salesforce case: N/A
Type: Issue
Component/Process: Salesforce Source
Description: Data of an ignored event is shown unencrypted when the source_capture logging is set to verbose.
Jira issue: RECOB-5985
Salesforce case: 50008
Type: Issue
Component/Process: MySQL Source
Description: Table exclusion/inclusion logic during CDC is case sensitive.
Jira issue: RECOB-5983
Salesforce case: 52867
Type: Issue
Component/Process: Salesforce (Incremental Load) Source
Description: It is not possible to work with Log Stream using the Bulk API.
Jira issue: RECOB-6038
Salesforce case: 50753, 51685, 50311
Type: Issue
Component/Process: IBM for DB2 LUW Source
Description: When capturing changes from a table that was altered to be compressed (before REORG), Replicate fails to apply the update to the target.
Jira issue: RECOB-6151
Salesforce case: 51369
Type: Issue
Component/Process: SAP HANA Source - Log Based CDC
Description: Captured changes are sometimes not replicated to the target.
Jira issue: RECOB-6222
Salesforce case: 58091
Type: Issue
Component/Process: SAP HANA Source
Description: The SAP HANA partition list contains duplicate partition IDs when a table contains active snapshots.
This section lists the resolved for the November 2022 initial release.
Jira issue: RECOB-5818
Salesforce case: 44292
Type: Issue
Component/Process: SybaseIQ Target
Description: A nullable BOOLEAN data type would be created as a non-nullable BIT.
Jira issue: RECOB-6066
Salesforce case: 44742
Type: Issue
Component/Process: Engine
Description: After upgrade it would not be possible to run tasks if Replicate was installed with non-admin privileges.
Jira issue: RECOB-5804
Salesforce case: 48152
Type: Issue
Component/Process: MySQL Source
Description: Non ASCII enum values would not be captured during CDC.
Jira issue: RECOB-5893
Salesforce case: 41836
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: INSERT operations would sometimes not be captured from Oracle 11.22 Redo Log event.
Jira issue: RECOB-5601
Salesforce case: 42073
Type: Issue
Component/Process: Logging
Description: With some of the cloud-based endpoints, "not found" would be written as an error message instead of a trace.
Jira issue: RECOB-5782
Salesforce case: 46218
Type: Issue
Component/Process: MySQL Source
Description: With some query platforms, CREATE DDL starting with a comment line would not be captured during CDC.
Jira issue: RECOB-5609
Salesforce case: 37728
Type: Issue
Component/Process: MySQL Source
Description: DDL changes in special formats would not be captured during CDC.
Jira issue: RECOB-5937
Salesforce case: 49312
Type:Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: Incorrect INSERT operations would sometimes not be captured from Oracle 11.22 Redo Log.
Jira issue: RECOB-5689
Salesforce case: 27920
Type: Issue
Component/Process: Microsoft SQL Server Source
Description: Long VARCHAR and VARCHAR(max) values would sometimes not be replicated correctly.
Jira issue: RECOB-5918
Salesforce case: N/A
Type: Feature
Component/Process: MongoDB Source
Description: Added support for MongoDB Atlas, including new authentication methods: LDAP and AWS IAM. Also added support for LDAP authentication when using MongoDB Standard.
Jira issue: RECOB-5877
Salesforce case: 49824
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: In rare scenarios, a DELETE operation would be reported as an UPDATE by Replicate Log Reader. This would cause the target UPDATE statement to contain an empty SET CLAUSE.
Jira issue: RECOB-5763
Salesforce case: 42102
Type: Issue
Component/Process: Vertica Target
Description: The task would fail when inserting a duplicate Primary Key, even if the Apply Conflicts task policy Duplicate key when applying INSERT was set to Ignore.
Jira issue: RECOB-5861
Salesforce case: 50352
Type: Issue
Component/Process: Snowflake on AWS with Amazon S3 Staging
Description: The Full Load and CDC task would fail if the target folder had a leading slash.
Jira issue: RECOB-5799
Salesforce case: 45290
Type: Issue
Component/Process: Sorter - Kafka Target
Description: When replicating to Kafka target and the After Full Load completes, stop the task: Before cached changes have been applied task setting was enabled, the cached changes would be applied before the task stopped.
Jira issue: RECOB-5713
Salesforce case: 27920
Type: Issue
Component/Process: Microsoft SQL Server Source
Description: When a wide table contained long VARCHAR columns, in rare scenarios, the VARCHAR column values would be replicated to the wrong record.
Jira issue: RECOB-5810
Salesforce case: 46794
Type: Issue
Component/Process: Google Cloud BigQuery Target
Description: Empty table folders would remain in the data_files folder after Full Load completed.
Jira issue: RECOB-5851
Salesforce case: 41517
Type: Issue
Component/Process: IBM DB2 for z/OS Source
Description: No warning would be issued if the DATA CAPTURE CHANGES attribute was not defined for SYSIBM.SYSTABLES.
Jira issue: RECOB-5832
Salesforce case: 42768
Type: Issue
Component/Process: SAP HANA Source - Log Based Capture
Description: Excessive memory consumption would sometimes occur during the task.
Jira issue: RECOB-5842
Salesforce case: 42804
Type: Issue
Component/Process: Kafka Target
Description: In rare scenarios, the task would end abnormally.
Jira issue: RECOB-5813
Salesforce case: N/A
Type: Internal
Component/Process: Oracle Source - Replicate Log Reader
Description: The task would crash when source_log_dump logger was set to Verbose.
Jira issue: RECOB-5817
Salesforce case: 33656
Type: Issue
Component/Process: SAP HANA Source - Trigger Based Capture
Description: Changes from tables with an OID larger than 2**32 would not be captured,
Jira issue: RECOB-5682
Salesforce case: 44211
Type: Issue
Component/Process: Google Cloud BigQuery Target
Description: When the Create tables clustered by primary key option was enabled in the endpoint settings, the task would fail if one of the primary key columns was a TIME data type,
Jira issue: RECOB-5830
Salesforce case: 48928
Type: Issue
Component/Process: SAP Application (DB)
Description: Change capture from clustered tables (e.g. KONV, BSEG, etc.), would sometimes fail with the following error:
Incorrect PART_NO 1 in the Cluster '<cluster table name>' object part 0, possible changes are ignored
Jira issue: RECOB-5820
Salesforce case: 36056
Type: Issue
Component/Process: IBM DB2 for z/OS Source
Description: IBM DB2 for z/OS would not report the lack of MONITOR2 permissions and would not capture changes.
Jira issue: RECOB-5788, RECOB-5754
Salesforce case: 41538, 43109
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: The task would end abnormally during parsing of an 11.22 Redo Log event.
Jira issue: RECOB-5723
Salesforce case: N/A
Type: Issue
Component/Process: Control Tables
Description: DDLs other than ALTER TABLE would not be inserted into the DDL History Control Table (attrep_ddl_history).
Jira issue: RECOB-5768
Salesforce case: 46705
Type: Enhancement
Component/Process: Microsoft Azure Databricks Target
Description: When using a proxy connection, an option was added to disable the proxy for ADLS Gen2 storage.
Jira issue: RECOB-5752
Salesforce case: 46794
Type: Issue
Component/Process: Google Cloud BigQuery Target
Description: When using Full Load, ZIP files would sometimes be left in the data_file folder.
Jira issue: RECOB-5725
Salesforce case: 37794
Type: Enhancement
Component/Process: SAP HANA Source - Trigger Based
Description: Improved Left Outer Join performance when a TIMESTAMP column is used as a Primary Key.
Jira issue: RECOB-5469
Salesforce case: 38416
Type: Enhancement
Component/Process: Salesforce Source
Description: The subscribe timeout is now configurable using an internal parameter.
Jira issue: RECOB-5561
Salesforce case: 35025
Type: Issue
Component/Process: Amazon Redshift Target
Description: When working in Batch Optimized Apply mode, the task would switch to one-by-one mode instead of retrying when the following error occurred:
This type of IN/NOT IN query is not supported yet
Jira issue: RECOB-5701
Salesforce case: 44292
Type: Issue
Component/Process: CSV Target Endpoints
Description: When loading into a CSV target failed, the Full Load process would sometimes be reported as successful.
Jira issue: RECOB-5686
Salesforce case: N/A
Type: Enhancement
Component/Process: Microsoft Azure ADLS and Google Cloud Storage Targets
Description: Added Parquet file format support.
Jira issue: RECOB-5684
Salesforce case: N/A
Type: Enhancement
Component/Process: Amazon S3 target
Description: Added AWS PrivateLink support.
Jira issue: RECOB-5661
Salesforce case: N/A
Type: Enhancement
Component/Process: SAP HANA Source
Description: Added SSL connectivity support.
Jira issue: RECOB-5660
Salesforce case: N/A
Type: Enhancement
Component/Process: SAP HANA Trigger Based
Description: Added support for SAP HANA tables with no Primary Key, that are used in SAP with the corresponding SAP Primary Key.
Jira issue: RECOB-5680
Salesforce case: N/A
Type: Enhancement
Component/Process: Feature flags with Java SDK and auto generated endpoints
Description: Added partial support for feature flags with Java SDK and auto generated endpoints.
Jira issue: RECOB-5678
Salesforce case: N/A
Type: Enhancement
Component/Process: IBM DB2 for iSeries Source, IBM DB2 for z/OS Source, and IBM DB2 for LUW Source
Description: Added support for SSL connectivity using internal parameters.
Jira issue: RECOB-5659
Salesforce case: N/A
Type: Enhancement
Component/Process: SAP HANA Source
Description: Added support for connecting to a specific tenant database by providing the database name in the endpoint connection settings.
Jira issue: RECOB-5673
Salesforce case: N/A
Type: Enhancement
Component/Process: Microsoft SQL Server (MS-CDC) Source
Description: Added a new Microsoft SQL Server (MS-CDC) on-premise source endpoint.
Jira issue: RECOB-5668
Salesforce case: N/A
Type: Enhancement
Component/Process: Sybase ASE Source
Description: Added an internal parameter for enabling FIPS support.
Jira issue: RECOB-5666
Salesforce case: N/A
Type: Enhancement
Component/Process: Google Cloud SQL for SQL Server Target
Description: Added a new Google Cloud SQL for SQL Server target endpoint.
Jira issue: RECOB-5664
Salesforce case: N/A
Type: Enhancement
Component/Process: Databricks Delta
Description: Added a new Databricks Delta endpoint that supports Amazon, Azure, and Google Cloud Storage.
Jira issue: RECOB-5491
Salesforce case: 36583
Type: Issue
Component/Process: PostgreSQL Source
Description: When a timestamp record had '-infinty' as value, CDC would fail.
Jira issue: RECOB-5544
Salesforce case: 38075
Type: Issue
Component/Process: Teradata Target
Description: The TPT Log table name was being built incorrectly.
Jira issue: RECOB-5588
Salesforce case: 29650
Type: Issue
Component/Process: SAP Extractor Source
Description: The task would invoke an extractor job for a SAP table that was not a part of the task's table list.
Jira issue: RECOB-5623
Salesforce case: 38632
Type: Issue
Component/Process: SAP Hana Log-Based Source
Description: The sorter transaction swap files would accumulate and not be deleted.
Jira issue: RECOB-5568
Salesforce case: 40156
Type: Issue
Component/Process: IBM DB2 for z/OS Source
Description: This is a debug patch for the crash caused by rapid DROP/CREATE table processing.
Jira issue: RECOB-5529
Salesforce case: 34820
Type: Issue
Component/Process: SAP HANA Source Log based
Description: An empty string for both VARCHAR and NVARCHAR columns would sometimes be replicated incorrectly. Additionally, a table would sometimes be replicated incorrectly if its columns were modified.
Jira issue: RECOB-5593
Salesforce case: 41792
Type: Issue
Component/Process: Oracle Source
Description: A source transaction would fail in the Sorter when it contained changes of a captured table and SYS.OBJ$, and was then rolled back.
Jira issue: RECOB-5599
Salesforce case: 38960
Type: Issue
Component/Process: Microsoft SQL Server Source
Description: When "Read the backup log directly from a file" was enabled, the backup log usage would always be prioritized, even if the online logs priority was configured.
Jira issue: RECOB-5621
Salesforce case: 33656
Type: Issue
Component/Process: Metadata Manager
Description: Events from some tables would not be captured when the table ID of the number of captured tables was greater than 2*32.
Jira issue: RECOB-5459
Salesforce case: N/A
Type: Enhancement
Component/Process: SAP Application (DB) Source
Description: Business Objects changes processing was improved.
Jira issue: RECOB-5330
Salesforce case: 12867
Type: Issue
Component/Process: Microsoft Azure Databricks Target
Description: Added logging to troubleshoot a count difference between source and target issue.
Jira issue: RECOB-5307
Salesforce case: 34640
Type: Issue
Component/Process: Sybase ASE source
Description: The FLOAT data type would be replicated incorrectly during both Full Load and CDC.
Jira issue: RECOB-5487
Salesforce case: 00036960
Type: Issue
Component/Process: Salesforce Source
Description: When only the LastModifiedDate field was changed, the change would be ignored.
Jira issue: RECOB-5212
Salesforce case: 24055
Type: Issue
Component/Process: PostgreSQL Source
Description: Amazon RDS for PostgreSQL would not handle network issues properly.
Jira issue: RECOB-5522
Salesforce case: N/A
Type: Issue
Component/Process: Replicate General
Description: Replicate on Linux was built using FIPS mode
Jira issue: RECOB-5527
Salesforce case: 34091
Type: Issue
Component/Process: IBM DB2 for z/OS Source
Description: When a captured table had no CAPTURE DATA CHANGES attribute, the corresponding warning messages would not be issued.
Jira issue: RECOB-5484
Salesforce case: 3898
Type: Issue
Component/Process: Google Cloud Storage
Description: When a task was stopped and then resumed, the CDC files generated before the task was stopped would not be uploaded to Google Cloud.
Jira issue: RECOB-5511
Salesforce case: Jira issue: RECOB-5609
Salesforce case: 37728
Type: Issue
Component/Process:MySQL Source
Description:DDL changes in special formats would not be captured during CDC.
Type: Issue
Component/Process: MySQL (MariaDB)
Description: A new table added to the source would not be replicated in CDC until the task was stopped and resumed.
Jira issue: RECOB-5564
Salesforce case: 38064
Type: Issue
Component/Process: Salesforce Source (Incremental Load)
Description: Timeout errors would sometimes occur during Full Load.
Jira issue: RECOB-5237
Salesforce case: N/A
Type: Issue
Component/Process: BigQuery Target
Description: When Create tables clustered by primary key was enabled in the endpoint's Advanced tab, and Apply changes using SQL MERGE was turned on in the task settings, INSERTs would expose the data in the log.
Jira issue: RECOB-5509
Salesforce case: 21512
Type: Enhancement
Component/Process: Log Stream
Description: When using Log Stream and the Source change position (e.g. SCN or LSN) field is set to 0, the task will resume from the first event of the latest timeline.
Jira issue: RECOB-5176
Salesforce case: 30284
Type: Issue
Component/Process: Microsoft Azure SQL (MS-CDC) source
Description: When the date format in the default language was not MDY, Full Load would fail.
Jira issue: RECOB-5485
Salesforce case: N/A
Type: Issue
Component/Process: Amazon S3 Target
Description: The Region code UI label was incorrectly named Bucket region.
Jira issue: RECOB-5364
Salesforce case: 33794
Type: Issue
Component/Process: Snowflake Azure Target
Description: When the Optimize Inserts option was enabled in Batch Optimized Apply mode and JSONandXMLColumns-SnowflakeTarget was turned on (the default), the task would fail when trying to insert a CLOB column whose length exceeded 65535 characters.
Jira issue: RECOB-5445
Salesforce case: 21090
Type: Issue
Component/Process: SalesForce Source
Description: The task was stop capturing changes every few weeks, with the following error (excerpt)
exception=java.lang.OutOfMemoryError: Java heap space
Jira issue: RECOB-5457
Salesforce case: 34455
Type: Issue
Component/Process: SAP HANA Source
Description: SAP HANA views would not be replicated after upgrading.
Jira issue: RECOB-5540
Salesforce case: 38064
Type: Issue
Component/Process: Salesforce Source (Incremental Load)
Description: A timeout error would sometimes occur when unloading a table.
Jira issue: RECOB-5532
Salesforce case: 34641
Type: Issue
Component/Process: SAP HANA Source
Description: Filtering archiving user names that contained a period would not work.
Jira issue: RECOB-5232
Salesforce case: 4844
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: Replicate Log Reader would crash after parsing a Direct Insert Redo Log Event 19.1.
Jira issue: RECOB-5517
Salesforce case: 37119
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: INSERT operations in a compressed table would be missing when Goldengate was enabled in Oracle.
Jira issue: RECOB-5523
Salesforce case: NA
Type: Feature
Component/Process: SAP Application
Description: Added support for SNC.
Jira issue: RECOB-5072
Salesforce case: NA
Type: Issue
Component/Process: Google BigQuery Target, Security
Description: When Create tables clustered by primary key was enabled in the endpoint's Advanced tab, and Apply changes using SQL MERGE was turned on in the task settings, INSERTs would expose the Primary Key data in the log.
Jira issue: RECOB-5180
Salesforce case: 31399
Type: Issue
Component/Process: SAP Application (DB) Source with a Microsoft SQL Server backend
Description: When trying to capture changes from a Cluster table, the task would sometimes crash with the following error:
Incorrect PART_NO <> in the Cluster '<>' object part <>, possible changes are ignored
Jira issue: RECOB-5439
Salesforce case:
Type: Issue
Component/Process: Salesforce Source (Streaming CDC)
Description: Parsing of a custom time field would fail during Full Load with the following error:
Unable to parse '<time>' as TIME. Will use null instead.
Jira issue: RECOB-5394
Salesforce case:
Type: Issue
Component/Process: Salesforce Source (Incremental Load)
Description: A "Read timed out" error would sometimes occur when working with Bulk API.
Jira issue: RECOB-5501
Salesforce case: 38566
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: When the following settings were enabled in the endpoint's Advanced tab, the redo files would not be deleted automatically.
Jira issue: RECOB-5368
Salesforce case: 27920
Type: Issue
Component/Process: Microsoft SQL Server Source
Description: When a wide SQL Server table contained long VARCHAR columns, in rare scenarios, the VARCHAR column values would be replicated to the wrong record.
Jira issue: RECOB-5352
Salesforce case: 34292
Type: Issue
Component/Process: Salesforce Source (Incremental Load)
Description: Confusing warning messages would be shown in certain scenarios.
Jira issue: RECOB-5269
Salesforce case: 37942
Type: Issue
Component/Process: Salesforce Source (Incremental Load)
Description: Compound field types such as Address would replicated as NULL when using SOAP API.
Jira issue: RECOB-5321
Salesforce case: 34832
Type: Issue
Component/Process: Salesforce Source (Incremental Load)
Description: Remove column DDL cause to recoverable error loop
Jira issue: RECOB-5378
Salesforce case:
Type: Issue
Component/Process: Salesforce Source (Incremental Load)
Description: Unicode characters would not be replicated when using BULK API.
Jira issue: RECOB-5324
Salesforce case: 34585
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: When starting the task from a timestamp, Replicate Log Reader would sometimes capture Dynamic Partition table operations from the wrong Dynamic Partition table.
Jira issue: RECOB-5472
Salesforce case: 37942
Type: Issue
Component/Process: Salesforce Source (Incremental Load)
Description: Full Load would sometimes fails when a task was resumed.
Jira issue: RECOB-5221
Salesforce case: 32297
Type: Issue
Component/Process: MySQL Homogeneous
Description: ALTER TABLE operations would result in an unexpected character set being defined on the target.
Jira issue: RECOB-4881
Salesforce case: 02101374
Type: Issue
Component/Process: Microsoft SQL Server Source (from 2016)
Description: When the Primary Key was DATETIME, LOB lookup would fail, resulting in missing LOB columns.
Jira issue: RECOB-5242
Salesforce case: 33124
Type: Issue
Component/Process: PostgreSQL Source
Description: The task would sometimes crash when a large number of tables were truncated in a single operation.
Jira issue: RECOB-4880
Salesforce case: 24364
Type: Issue
Component/Process: Teradata Source
Description: When using Parallel Load, in a task defined with the Full Load and Apply Changes options, the task would sometimes crash during Full Load.
Jira issue: RECOB-5486
Salesforce case: 37690
Type: Issue
Component/Process: Snowflake
Description: Incorrect default values were assigned to some of the internal parameters.
Jira issue: RECOB-5435
Salesforce case: 36027
Type: Issue
Component/Process: SAP Application (DB)
Description: When a captured cluster table was changed, SAP Client records that were not configured in SAP Application (DB) would be replicated.
Jira issue: RECOB-5448
Salesforce case: NA
Type: Enhancement
Component/Process: Replicate Engine
Description: Updated the Kerberos OpenSSL libraries.
Jira issue: RECOB-5276
Salesforce case: 33320
Type: Issue
Component/Process: Microsoft Databricks Azure
Description: When the Sequence storage format was used and the files were compressed with gzip, empty files would be left in the Databricks partition if the load operation was interrupted.
Jira issue: RECOB-5427
Salesforce case: 37749
Type: Issue
Component/Process: Amazon Redshift Target
Description: It would not be possible to save the endpoint settings without changing the default Bucket region.
Jira issue: RECOB-5327
Salesforce case: 32256
Type: Issue
Component/Process: SAP HANA Trigger Based Capture
Description: When using the Commit-Timestamp internal parameter, latency issues would be encountered when processing changes from non-captured tables.
Jira issue: RECOB-5419
Salesforce case: 33783
Type: Issue
Component/Process: Microsoft SQL Server Source
Description: The LSN on a secondary replica in an AlwaysOn environment could not be located.
Jira issue: RECOB-5372
Salesforce case: 34751
Type: Issue
Component/Process: Installer
Description: The Qlik Replicate installation timeout was increased to 300 seconds.
Jira issue: RECOB-5375
Salesforce case: 31588
Type: Issue
Component/Process: SAP DB
Description: After upgrading to Replicate 2021.11 and resuming a task, the first DDL change would cause the associated table to be suspended.
Jira issue: RECOB-5068
Salesforce case: 30567
Type: Issue
Component/Process: BigQuery TARGET
Description: When Create tables clustered by primary key was enabled in the endpoint's Advanced tab, and Apply changes using SQL MERGE was turned on in the task settings, INSERTs would fail when the Primary Key started or ended with a single quote.
Jira issue: RECOB-5170
Salesforce case: 23555
Type: Issue
Component/Process: Amazon Redshift
Description: Replicate would not attempt to reconnect to Amazon Redshift if the connection was lost.
Jira issue: RECOB-5380
Salesforce case: 25486
Type: Issue
Component/Process: Snowflake
Description: In Batch Optimized Apply mode, explicit COMMITs would be performed when applying changes to Snowflake, resulting in unacceptable costs.
Jira issue: RECOB-5164
Salesforce case: 31074
Type: Issue
Component/Process: Control Tables
Description: When the DDL History Control table was enabled, and a column was changed from TEXT to VARCHAR(max) or vice versa, the task would encounter a recoverable error.
Jira issue: RECOB-5342
Salesforce case: 30113
Type: Issue
Component/Process: SAP DB
Description: A special SAP date using the year 0101 would not be replicated correctly.
Jira issue: RECOB-5268
Salesforce case: 28583
Type: Issue
Component/Process: SAP DB
Description: Changes would sometimes not be captured when replicating from SAP cluster tables with Microsoft SQL Server as the underlying database.
Jira issue: RECOB-5174
Salesforce case: 32472
Type: Issue
Component/Process: LOB Support
Description: LOB support would be disabled when the No record found for applying an update → INSERT the missing target record error handling option was selected, AND a table was changed with a transformation.
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.
Table of Contents
The following release notes cover the versions of Qlik Catalog released in November 2022. Resolved defects and limitations for Qlik Catalog are also listed.
Update Publish Target Credentials Via UI and API
Allow Properties to be Added to Discover Module QVD Entities
Catalog Failed to Start When "en_US" Locale Was Not Used
Enhanced User Session Logging
Prevent QVD Sources from Being Orphaned
API to Create JDBC Entity
Required Configuration for RHEL 9, SELinux and podman
Includes issues resolved in the November 2022 initial release - November 2022 SR1.
Jira ID: QDC-1377
Publish target credentials are now editable in the UI. Previously, editing of a publish target was disabled if the target was in use by a publish job.
In addition, an API was added to update target credentials, /qdc/target/v1/targets/{id}/credentials
Details of this API are available in Qlik Catalog under Support / API Documentation, where the API may be tried out and a sample script using curl is available.
Jira ID: QDCB-1199
Previously, properties could not be added to Discover module QVD entities. This prevented the user from adding custom properties, as well as setting relevant properties (e.g., podium.qlik.script).
It is now possible to add properties to Discover module QVD entities. Caution should be used as most system properties should not be added to, or modified on, QVD entities.
Jira ID: QDCB-1195
Previously, Qlik Catalog did not start when installed on a host where the default locale was not "en_US" (English, United States), or if Java was configured or installed to use a locale other than "en_US".
Catalog now successfully starts with non "en_US" locales. Note: Qlik Catalog is not localized and all messages and formatting continue to use the "en_US" locale.
Jira ID: QDC-1376
Qlik Catalog now logs (in catalina.out) enhanced user session logging.
User login, logout (or session expiration) and duration are now logged:
2022-11-21 12:39:35,463 INFO User successfully authenticated: podium [SessionListenerWithMetrics[https-jsse-nio-8443-exec-2]]
2022-11-21 13:40:23,390 INFO User session invalidated: podium, duration: 1:00:47 [SessionListenerWithMetrics[Catalina-utility-1]]
In addition, two periodic counts of logins (current and total) since Tomcat restart are output:
2022-11-28 15:32:05,878 INFO type=COUNTER, name=current.logins.since.restart, count=1 [SessionListenerWithMetrics[https-jsse-nio-8443-exec-6]]
2022-11-28 15:32:05,878 INFO type=COUNTER, name=total.logins.since.restart, count=3 [SessionListenerWithMetrics[https-jsse-nio-8443-exec-6]]
Note: if Tomcat is restarted there will be "uncounted" unexpired sessions carried over from the prior execution.
Jira ID: QDCB-1200
Previously, if a QVD Path deletion (red dot) was accepted while a QVD sync or load was running, the associated source was not deleted, became disconnected from the Catalog data model, and could not be deleted. This then interfered with subsequent acceptance of the same QVD Path when the Qlik Sense Data Connection was again tagged.
The deletion of a QVD Path is now rejected if a QVD sync or load is running.
Jira ID: QDCB-1184
An API was added to script the creation of JDBC entities. This is an alternative to the standard UI wizard for adding relational schema, table and column metadata via JDBC. To use this API, a JDBC source connection must already exist, as well as a source that uses it (requiring one entity to be added via the UI wizard). Once these exist, API /qdc/entity/v2/createFromFlatFile may be used.
Details of this API are available in Catalog under Support / API Documentation, where the API may be tried out and a sample script using curl is available
If Qlik Catalog is installed on Red Hat Enterprise Linux (RHEL) 9.1+ (and some versions of 😎 and SELinux is enabled (the default on RHEL 9), configuration changes must be made to successfully use the podman containers included by Qlik Catalog to import (load) and export (publish) QVDs, and to load XML data. NOTE: The alternative to the below procedure is to disable SELinux.
For QVD import and export, do the following, which will create a dedicated "temp" directory and configure SELinux and Catalog to use it. This temporary directory is where the engine container writes its output files. It must be in the root directory as many of the other standard locations (e.g., /tmp and /usr/local) have been black-listed.
As root:
# mkdir /tmp-catalog
# chown qdc:qdc /tmp-catalog
# semanage fcontext -a -s system_u -t container_file_t /tmp-catalog
# restorecon -F -v /tmp-catalog
As the Qlik Catalog service account user (e.g., qdc), edit core_env.properties, and find and set the following property:
qvd.conversion.temp.directory=/tmp-catalog
Also, as the Qlik Catalog service account, edit /usr/local/qdc/qlikcore/pod_qlikContainers.yml and uncomment the following two blocks:
# Uncomment the following volumeMount.
- mountPath: /tmp-catalog
name: tmp-catalog
and:
# Uncomment the following volume.
- hostPath:
path: /tmp-catalog
type: Directory
name: tmp-catalog
To ensure the podman containers are started on host reboot, the container start must be made dependent on the user service for the service account user (e.g., qdc).
As root, edit /etc/systemd/system/qlikContainers.service and follow the comment:
#After=syslog.target network.target qdc_pg.service
# A dependency on the service account user service is required for RHEL 9 with SELinux.
# Please see the November 2022 SR1 release notes or the February 2023 installation guide.
# Uncomment the below Requires and After; comment off the above Requires and After.
Requires=user@1000.service qdc_pg.service
After=user@1000.service qdc_pg.service
You can ensure user "qdc" has the correct ID by running "id -u qdc". If the correct numeric value is not used in the service file, update the values above.
Then, uncomment similar lines in file /etc/systemd/system/nextgen-xml.service.
When all changes have been made, run "systemctl reboot" to restart the system.
No noteworthy issues were resolved. Please see noteworthy features below.
This section pertains to Catalog installations that use podman and are having issues starting and stopping containers. Please also apply this command before upgrading. Podman is most likely in-use on RHEL 8, and Ubuntu 20.04 and 22.04, installations. The following command must be run once:
sudo loginctl enable-linger qdc
On most installs, it will be the root user that must run this. Replace "qdc" if a different Linux service account is used. Then, reboot the server (sudo shutdown -r now).
This advice assumes that the containers have been configured to run as services, either manually or by using QDCpostinstall.sh (now CatalogPostInstall.sh). "enable-linger" allows services running as a non-root user (i.e., qdc) to continue running cleanly without the user being logged-in. It is needed to cleanly shutdown and restart services using commands such as launch_qlikContainers.sh and shutdown_qlikContainers.sh.
Without this, errors will be seen when shutting-down pods and containers, particularly important when Catalog upgrade is run. Here is the error seen at upgrade:
Info: Qlik Licenses container running - shutting down & removing
error opening file `/run/user/1001/crun/88febfa150a1c8d207cfe1cc82f387c8f27d792f2d37fd0276a7858fc6255140/status`: No such file or directory
Error: timed out waiting for file /tmp/podman-run-1001/libpod/tmp/exits/88febfa150a1c8d207cfe1cc82f387c8f27d792f2d37fd0276a7858fc6255140: internal libpod error
Beginning with the November 2022 release, the installer will enable linger automatically on initial install if either CatalogFirstTime.sh or CatalogPrereqs.sh is used.
The following command can be used to verify linger status (can be run while logged-in as qdc):
loginctl user-status qdc | grep inger
Noteworthy changes and features.
For JDBC loads, customers may need to load only those rows introduced into the source database table since the last load into Qlik Catalog. A new entity property, src.table.new.records.filter.column, allows a customer to specify a table column that is used to identify new rows. Qlik Catalog will automatically build a WHERE-clause and append it to the SQL SELECT statement specified in property src.file.glob.
Logically, this column should be an ever-increasing numeric ID column, an IDENTITY column, found in many relational systems. A timestamp column like creation_ttz could be used if it was guaranteed to always increase and be unique—duplicate timestamps would be problematic.
Qlik Catalog uses the filter column to build a distribution database profile table query to find the maximum value of the column. The resulting value is used to automatically append a WHERE clause to the src.file.glob value which is used to retrieve data from the source table
Each time a load is executed this process is repeated; thereby ensuring only new rows are read from the source database table. To ensure consistent load behavior, the property src.table.new.records.filter.column should be set immediately after the entity is created and no later than before the second load is run.
Please see the online help for more details and a video demonstration.
Publish Job: Use Business Name for Header
The Publish Job "Entities" File Format dialog has been modified to include a new checkbox "Use Business Name for Header" – it should be "checkable" whenever the "Header" checkbox is checkable, generally TEXTFILE formats being output to some sort of file (e.g., LOCALFILE and S3; but not Amazon or Hadoop or QCS_S3):
Originally released as part of August 2022 SR1.
Previously, business metadata import was "additive" for tags – tags specified in the spreadsheet (CSV or XLS) were added to the existing source/entity/field tag set. With this enhancement, the source/entity/field tag set can be reset (aka overwritten or cleared).
This can be done both for the entire business metadata import (the entire file) by selecting the “Overwrite Tags” UI checkbox, or on a row-by-row basis by inserting a column with header “Overwrite Tags” between “Technical Description” and “Tag1” columns and setting the value for any source/entity/field tag set to true/TRUE in that column. The source/entity/field tag set will then be overwritten upon metadata import. If no tags are supplied in the sheet, the tag set is effectively cleared.
The "Overwrite Tags" column does not have to be present. If the column is present, TRUE/true can be put in as many or few cells as needed (for example: all, none or only one).
Catalog now supports the concurrent use of both SAML SSO and PODIUM (username and password) authentication. This enables end-users to logon using SSO while at the same time supporting API usage, including Sense and QEM API usage, that requires traditional username and password authentication.
Previously two Tomcat instances were required. This can now be accomplished using only a single Tomcat instance. Please see the install guide for details.
The entire Qlik Catalog first time installation process can now be driven by a single script, CatalogFirstTime.sh. This script, run as a sudo capable user, automatically:
The above three Qlik Catalog installation steps may still be separately run using:
All the above scripts require properties to be set in CatalogInstaller.properties (formerly QDCinstaller.properties). Upgrades continue to use the main installer script, "./CatalogInstaller.sh -u".
Please see the install guide for more details.
NOTE: on first time install, initial password properties must be set in CatalogInstaller.properties for the two accounts to be created by the installer:
NOTE: the installer now quickly detects corrupt podium zip files (e.g., podium-4.15-16448_Linux_X64.zip) and fails the installation process at the beginning.
Beginning with the May 2021 release, only Apache Tomcat 9 is supported. The installer will prohibit other versions. If using Tomcat 7, please first initiate a migration to Tomcat 9 before installing this release. Then, when installing, the upgrade option (-u) is NOT used.
These instructions may also be used to upgrade from an older version of Tomcat 9 to a newer version.
Step | Sample Commands |
Shutdown and rename old Tomcat 7 or 9 | cd /usr/local/qdc (or cd /usr/local/podium) ./apache-tomcat-<OLD_VERSION>/bin/shutdown.sh mv apache-tomcat-<OLD_VERSION> old-apache-tomcat |
Download and expand Tomcat 9 - NOTE: adjust version 9.0.64 to use latest 9.0.x series | wget https://archive.apache.org/dist/tomcat/tomcat-9/v9.0.64/bin/apache-tomcat-9.0.64.tar.gz tar -xf apache-tomcat-9.0.64.tar.gz rm apache-tomcat-9.0.64.tar.gz |
Copy core_env.properties from old Tomcat to new Tomcat 9 | cp old-apache-tomcat/conf/core_env.properties apache-tomcat-9.0.64/conf/ |
If migrating from Tomcat 7: Extract server.xml from podium.zip and copy to new Tomcat | unzip -j podium-4.<VERSION>-<BUILD>.zip podium/config/tomcat9-server.xml -d . mv ./tomcat9-server.xml apache-tomcat-9.0.64/conf/server.xml |
If upgrading Tomcat 9: Copy server.xml from old Tomcat 9 to new Tomcat 9 | cp old-apache-tomcat/conf/server.xml apache-tomcat-9.0.64/conf/ If the old Tomcat 9 was configured for HTTPS, and the keystore (jks file) was stored in the old Tomcat directory, migrate it to the new Tomcat directory, and update conf/server.xml to reference it. Consider placing the keystore file in a non-Tomcat directory such as /usr/local/qdc/keystore. |
Configure QDCinstaller.properties for Tomcat 9 | Whether using an existing QDCinstaller.properties file from a previous install, or configuring one for the first time, ensure that it is updated to point to Tomcat 9: TOMCAT_HOME=/usr/local/podium/apache-tomcat-9.0.64 |
Finally, when the installer is run, do NOT specify upgrade mode (-u), as some files should be created as if it were a first-time install. | ./QDCinstaller.sh |
At this point, Tomcat 9, if newly installed, will support only HTTP on port 8080.
Verify successful Qlik Catalog startup and basic functionality.
Additional configuration will be required to enable HTTPS on port 8443, apply security headers, etc. If Tomcat 7 used HTTPS, the keystore (jks file) containing the public-private keypair should be copied to Tomcat 9 and conf/server.xml updated.
In addition, Tomcat 7 may have been configured as a service. It should be disabled. Tomcat 9 may be configured as a service to automatically start.
Please see the install guide for guidance on both.
Do not attempt to upgrade until the following is understood.
If upgrading from a version of Qlik Catalog prior to September 2020 (4.7) there are utilities that MUST be run after Catalog is upgraded. Once run, the utilities need never be run again.
The server may not start until the first two utilities have been run and will log a WARN at startup until the third is run. Do NOT upgrade the server until familiar with these utilities and the information required to run them. It will take time to gather this information. Gathering the information BEFORE Catalog is upgraded will minimize downtime.
Run the utilities in this order:
This will be required if Qlik Sense Connectors have been defined to load QVDs.
Will need to gather networking info and certificate files from Qlik Sense servers.
May be run from any directory.
This will be required only if the installation is single node.
Will need podium_dist database info if defaults altered.
May be run from any directory.
This will be required only if the installation is single node.
Will need podium_dist database info if defaults altered.
May be run from any directory.
A chronological listing (most recent first) of additions, changes in behavior, and deletions to the primary global configuration file, core_env.properties.
No additions, changes or deletions.
ADDITION: Configurable LDAP Username Attribute for Active Directory Sync
When performing Active Directory (AD) sync using LDAP, Catalog hardcoded the use of LDAP user attribute sAMAccountName to extract the Catalog username. The attribute is now configurable, enabling a customer to choose an alternate attribute such as userPrincipalName. A new core_env property has been added:
# LDAP attribute used to extract the username from the LDAP record. Only
# the username before any "@domain" will be used. userPrincipalName is a
# logical alternative. Default: sAMAccountName
#ad.ldap.username.attribute=userPrincipalName
DELETION: Field-Level Encryption Removed
The ability to encrypt a field has been removed -- the "Encrypt" checkbox will no longer be present on the Field Information dialog. The following properties can now be retired (either commented-off or removed from core_env.properties):
ADDITION: Fixed "Host" Header Poisoning
The Host header value should not automatically be trusted by Catalog. Instead, a protected configuration setting is introduced. See earlier description of QDCB-404.
# To protect against HTTP headers such as "Host" and "X-Forwarded-Host" being abused by a malicious client, set this
# to the hostname used by clients. It is embedded in link results returned by Catalog searches (e.g., /catalog/search).
# Restart required. Default: not set.
external.hostname=<FULLY_QUALIFIED_DOMAIN_NAME>
CHANGE: Enable Publish to Qlik Sense by Default
Publish to Qlik Sense will now be enabled by default.
# Setting this to true will start showing 'Publish to Qlik' option in Podium UI cart checkouts.
# Default: true
is.publish.to.qlik.enabled=true
DELETION: Publish to Qlik Sense: Multiple Sense Server Support in User Interface
Configuration of specific Sense servers for Publish to Qlik Sense has been moved to the Catalog user interface. General settings remain in core_env.properties.
The following is taken from the "Qlik Catalog + Qlik Sense Integration Guide". The nine, new UI fields for Publish to Qlik Sense were formerly in core_env.properties. The following properties can now be retired (either commented-off or removed from core_env.properties):
The following two properties were also removed and have been superseded by pre-existing Qlik Sense Connector fields:
The following global settings remain in the core_env.properties file -- please see the comments there:
CHANGE: Enable Catalog Auto-Creation of Sense Security Rules & Auto Add Newly Discovered QVDs to Local/AD Groups
The property controlling these capabilities is now named "qlik.sense.invert.security.model". It was formerly named "qlik.sense.auto.create.security.rules" when introduced in the initial February 2022 release. See earlier description of QDCB-1114.
# Normally, on QVD import, Catalog creates Groups that shadow Sense Data Connections. QVD entities are then added to
# these Groups. A Sense admin creates Security Rules granting Users access to Data Connections. When a User logs
# in to Catalog, a security audit is conducted against Sense, and the User is added to Groups if they have access to the
# corresponding Data Connections.
#
# This model may be inverted. A Catalog admin can instead manually add QVD entities to Catalog local/AD groups. When
# this occurs, users running Publish to Qlik Sense may need Data Connection Security Rules created in order to load
# published data in Sense. Catalog can be configured to automatically create any needed Security Rules by setting this
# property to true. In addition, this property ensures that once a single QVD entity has been manually added to a Group,
# future QVD entities discovered during import in the same Data Connection folder will be automatically added to the
# same group.
#
# Properties 'qlik.sense.root.admin.directory.name' and 'qlik.sense.root.admin.user.name' must also be set.
# Formerly: qlik.sense.auto.create.security.rules. Default: false
#qlik.sense.invert.security.model=true
ADDITION: Enable Qlik Catalog Auto-Creation of Sense Security Rules
Set this property to true to have Catalog auto-create Qlik Sense Data Connection Security Rules (if needed) as part of the Publish to Qlik Sense process. See earlier description.
# If Catalog local or AD Groups have had QVD Sources/Entities added to them, users running Publish to Qlik Sense
# may need Data Connection Security Rules created in order to load data in Sense. Normally, these Security Rules
# should be created and managed in Sense QMC. However, Catalog can be configured to automatically create any
# needed Security Rules if this property is set to true. Properties 'qlik.sense.root.admin.directory.name' and
# 'qlik.sense.root.admin.user.name' must also be set. Default: false
#qlik.sense.auto.create.security.rules=true
ADDITION: Alter SAML Identity Provider User Domain Name
Specify this property to set or alter the domain name of the user sent by the SAML identity provider (IdP) to Catalog. See earlier description.
# If the IdP does not append a domain and one is needed, or you wish to change the domain, set this property. If the
# property is set to a value of "test.com", a SAML principal name of "jdoe" would become "jdoe@test.com"; a SAML
# principal name of "jdoe@other.com" would become "jdoe@test.com". The known use case for this property is to match
# principal (aka user) names coming from the IdP with the users imported from Active Directory. Default: not set
#saml.alternate.domain=
No changes.
CHANGE: Publish to Qlik Sense Enhancement
The Publish to Qlik Sense RootAdmin user is now more widely applied. Before, it was only used when multiple domains were specified in property "qlik.sense.active.directory.name". Now, it is used to ensure a known, valid Sense user is being used for Publish to Qlik Sense. See earlier description of QDCB-1007.
# Enter the directory and user name of a Sense 'RootAdmin' user.
# Used to validate that the domain user being used for Publish to Qlik Sense has previously logged into the
# Sense server. This prevents users known only to Catalog being inadvertently created in Sense.
# Mandatory if multiple directories were specified in property 'qlik.sense.active.directory.name'.
qlik.sense.root.admin.directory.name=AD
qlik.sense.root.admin.user.name=sense-service
ADDITION: Extended Support for Fields in Prepare Dataflows that are also Pig Reserved Words
Prepare dataflow jobs will fail if fields are named using unanticipated Apache Pig reserved words. Such words can now be configured. See earlier description of QDCB-1107.
# Entity fields used in Prepare Dataflows may also be Pig reserved words (e.g., STORE). Frequently used reserved words
# are correctly handled if they are field names. This property may be used to augment the set of known reserved words
# with unanticipated words. Words must be comma separated. Default: not used
#pig.reserved.words.additional=register,CASE
Qlik Catalog November 2022 SR1 - Application
Qlik Catalog November 2022 SR1 - Installer
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.
Table of Contents
The following release notes cover the versions of Qlik DataTransfer released in November 2022.
Qlik DataTransfer November 2022 release does not have any new feature, but it has fixes for the issues described below and few other improvements which can help customer to avoid any issues.
Qlik DataTransfer November 2022 comes with fixes for the issues described below.
File Upload error if Folders with same name is configured.
Jira issue ID: DTB-61
Description: Qlik DataTransfer attempts to move files to a temporary folder created based on parent directory name. If two or more folders had the same name and two separate files in both folders had the same name, then the temporary file copies would conflict with each other, potentially causing local file and upload operations to fail. This also potentially left orphaned files in the temporary files folder, interfering with uploads already in progress and subsequent upload of files having the same name.
File is deleted from Source if failed to upload from Data Folder.
Jira issue ID: DTB-62
Description: File(s) are deleted from source folder when an error occurs during the manual upload of a Data folder.
QDT UI hangs indefinitely and cannot handle large lists of tables in data preview.
Jira issue ID: DTB-63
Description: Data Preview screen hangs while fetching tables when there is a large list of tables (around 100k).
App Reload Delay Too Short and Not Configurable.
Jira issue ID: DTB-64
Description: In some cases, app reload is triggered too quickly during automatic folder upload.
Qlik DataTransfer November 2022 comes with below improvements in current features.
Improved upload process by adding extra validation, more configurable settings, and better error handling.
Description:
Qlik DataTransfer calculates the time to upload based on the assumption of bandwidth being equally divided among concurrent uploads. It also adds a 20% safety margin and the sum of all retry delays to estimate overall worst case TTL.
The minimum TTL is 600 secs (10 minutes), and the maximum is 259200 secs (3 days).
Backup recommendations:
Please refer to the online help for information about the requirements for Qlik DataTransfer.
System requirements for Qlik DataTransfer
The following issues and limitations were identified at release time. The list is not comprehensive; it does however list all known major issues and limitations.
General
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.
Table of Contents
The following release notes cover the Qlik ODBC Connector for QlikView released in October 2022.
The Qlik online help provides full documentation of the ODBC Connector Package.
All included ODBC drivers have been updated to the latest available versions. This delivers new functionality, enhanced stability, and improved performance.
Specific updates are included in the following connectors:
Amazon Redshift:
Databricks:
Google BigQuery:
Snowflake:
There are no issues and limitations identified at the time of release.
The Qlik ODBC Connector package installs from the file QlikOdbcConnectorPackage_setup.exe. See the Qlik Connectors section of the online help for detailed installation instructions.
If any previous version of the Qlik ODBC Connector package is installed on the system, it must be uninstalled before the new version can be installed. It is recommended that you make a backup of the system before upgrading.
Please refer to the System requirements for QlikView section of the online help for up-to-date information about system requirements and browser support.
This ODBC Connector package (6.211) is compatible with QlikView 12.40 and later.
The new Qlik ODBC Connectors package is available from the Qlik Downloads site.
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.
Table of Contents
The following release notes cover the versions of Qlik Catalog released in February 2021.
QDCB-947 – Publish to Qlik Sense of QVD Entities Containing Mixed-Case Fields
QDCB-948 – Publish to Qlik Initiated by User with Hyphen in Name
Jira ID: QDCB-947
When Publish to Qlik was invoked for a QVD entity, an issue arose if the QVD fields contained any upper-case characters. Previously, the script passed to Qlik Sense used "LOAD *". However, a recent change explicitly lists each field, for example, "LOAD field1, field2". The fields included in the LOAD statement were all lower-cased, causing the LOAD statement to fail in Qlik Sense if the fields contained any upper-case characters.
The fix is to preserve the original case found in the QVD file when constructing the LOAD statement to pass to Qlik Sense.
Publish to Qlik Initiated by User with Hyphen in Name
Jira ID: QDCB-948
If the logged-in Catalog username contained a hyphen "-" or other non-alpha-numeric character besides underscore "_", Publish to Qlik Sense failed. It failed because the Publish dataset and job names embed the username -- the hyphen character is not allowed in that context.
The fix was to transform the username, replacing any problematic characters with underscore, prior to embedding the username in the Publish dataset and job names.
QDCB-761 – Hide Source and/or Security Module for Roles including Prepare Access
QDCB-919 - Use business name as primary entity/ field name
Jira ID: QDCB-761
In order to run Prepare workflows, the access masks created for this custom role require access to the source and security modules as prepare adds data (targets) and permissions (group security on targets). Some customers have requested an ability to restrict access to those modules.
Two new core_env props have been added to forcefully hide security and source section for specific role names.
The core env props are:
# The following property works on top of QDC's security mechanism. If a user has access to the source
# section because of the roles they is associated with and there is a need to hide the source section, then
# the following property can be used. QDC will loop over all the roles logged in user is part of, and if
# any of the below roles(separated by comma) are found in the logged in user's roles, then the source module will not be displayed to them.
# Value for this can be a CSV. Default:
#roles.to.exclude.source=
# The following property works on top of QDC's security mechanism. If a user has access to the security
# section because of the roles they is associated with and there is a need to hide the security section, then
# the following property can be used. QDC will loop over all the roles logged in user is part of, and if
# any of the below roles(separated by comma) are found in the logged in user's roles, then the security module will not be displayed to them.
# Value for this can be a CSV. Default:
#roles.to.exclude.security=
As an example, if there is a custom role named 'PREPARE_EXECUTOR' with an access mask of 251721703, which gives it access to the source, prepare, and security modules. However, you want to restrict it from accessing the source module but allow it to access the security module.
roles.to.exclude.source=PREPARE_EXECUTOR
roles.to.exclude.security=
Jira ID: QDCB-919
Historically, technical name was used as the primary entity/ field name. With the addition of the following property, users can now use business name as primary entity name on catalog, and business name as primary field name while viewing the sample data. Business name column has also been added to the 'Field Statistics and Metadata' table in 'Catalog Details' view.
Property to configure if you want to display business or technical name at catalog, sample data The value can be BUSINESS or TECHNICAL . Default: TECHNICAL #display.entity.name.preference=TECHNICAL
The external Source, Entity and Field names in the "Source" module now exactly match their schema, table and column JDBC counterparts. For example, Cyrillic and Chinese characters may be used in imported table names -- they now properly appear in the Catalog UI.
The matching internal Source, Entity and Field names in the "Discover" module support virtually the same character set with the exception of the following characters: ./":'{}[],\. These eleven characters will be converted to "_" (underscore) in the Discover module -- all other characters will be preserved and appear in the UI. The conversion to underscore allows these names to be used in file-system directory names (where data is "landed") and in a variety of scripting and database usages. Queries against the Catalog distribution database (e.g., from the Discover / Query tab) should double quote schema and table names containing non-alphanumeric characters.
Support for these characters extends across the entire Catalog product, including the Prepare and Publish modules. The only special handling required is when referencing Field names in Prepare Pig expressions: Field names with non-alphanumeric characters must be double quoted. For example, if a Field (column) was named "F2#1", to reference it in the Pig CONCAT expression, double quotes must be used: CONCAT("F2#1", '-suffix').
Jira ID: QDCB-590
When core_env property "podium.qlik.dataconnection.addressed.registered.entity.generating.from=INTERNAL", REGISTERED and ADDRESSED JDBC entities are loaded on-demand prior to Publish-to-Qlik Sense. At the completion, the entity is "demoted" and its files and distribution tables are scheduled for deletion. The asynchronous garbage cleaner runs on a cycle of five minutes, meaning the data may be deleted before the Qlik Sense load is completed.
The deletion of these records is now deferred for eight hours. This can be adjusted in core_env.properties:
# For entities that are ad-hoc promoted as part of Publish to Qlik, the follow-on deletion (aka demotion) of files and
# distribution database tables will be deferred for this many hours. This prevents the Garbage Cleaner from
# inadvertently deleting data while it is being loaded into Qlik Sense. Fractional hours may be entered. Default: 8 hours.
#qlik.sense.data.deletion.deferral.period.hours=8
Jira ID: QDCB-696
While doing the import of QVD entities along with their data, the status column in the "View Details" modal of a single QVD import run only tells about the status of the scan and not the data load.
The label from "Status" to "Scan Status".
Core Env and qdc_qvd_2_csv.sh changes
Jira: QDCB-712
qvd.openconnector.script.path property of core_env has been modified to include a temp directory parameter..
qvd.openconnector.script.path=qlikcore-integration/qdc_qvd_2_csv.sh %prop.qvd.file.linux.folder %prop.qvd.file.entity.original.name %loadingDockLocation %loadingDockUri %qlikCoreScript %tempDir
A new core_env property has been introduced as well: qvd.conversion.temp.directory
P2Q select statement not explicit
Jira: QDCB-740
The Publish to Qlik (P2Q) script for Managed entities and QVD entities now supports aliases. If you want to provide alias to your column names in the script, please modify the fields to add business name into them - the business name is then used as an alias.
License agreement in the Support dropdown
Jira ID: QDCB-756
We have now added the Qlik User License Agreement in the 'Support' button in the UI.
Prepare Dataflow Editor not Saving Added/Deleted Fields
Jira ID: QDCB-773
The Prepare Dataflow "Save" action was not persisting target Entity field additions and deletions. If fields were added or deleted from a target Entity, the "Save" action failed to include the modified Entity with the HTTP API request. This was due to a Catalog user interface (UI) JavaScript bug. This issue has been fixed, and it is now possible to add and delete fields on a Prepare Dataflow target Entity.
License Agreement option in the support dropdown is now configurable
Jira ID: QDCB-826
The change can be controlled via two new core_env props:
# The value of this property is used as a label in the drop/down. Even though there are no invalid/ names
# We think the value of this property will mostly say License Agreement OR Terms of Use
# Default: License Agreement
#license.agreement.menu.display=License Agreement
# This is the document that comes up when the button with the above text is clicked from the UI.
# This document must be put in the <apache_tomcat>/<web_apps>/<qdc_web_app>/resources folder.
# The path will then be set as resources/<document_name> as below
# Default: resources/QULA.pdf
#license.agreement.text.display=resources/QULA.pdf
QVD Import fails due to long names in Postgres (63+)
Jira ID: QDCB-887
QVDs with entity names containing more than 63 characters were failing import due to a missing customization within the Postgres installer that is packaged with Catalog. The Postgres installer has been modified to support QVD import of entity names which contain up to 256 characters.
Change to Catalog Search
Jira ID: QDCB-901
Previously, the search query used to build the data displayed on the Catalog home page used multiple SQL "like" operators. The search term was concatenated with both a leading and trailing wildcard "%" character, denoting "contains". This resulted in an expensive SQL query.
Now, the default behavior is to only add a trailing "%" character, denoting "starts with". This is quicker.
If the customer desires the original behavior, they can either manually prepend a "%" character to the beginning of the search term or set core_env property "prepend.leading.percent.sign.for.catalog.search" to true.
The new property:
# Flag to control if the searched term in Catalog will have a percent sign prepended to it implicitly.
# The term always has a trailing percent sign appended to it implicitly. If the value of this flag
# is set to false, the user must put the percent sign (%) themselves in the search term for the code
# to do wildcard search. Default: false
#prepend.leading.percent.sign.for.catalog.search=false
New Property Allowing Compression to be Disabled During Prepare
Jira ID: QDCB-915
On at least one multi-node Catalog install, Prepare dataflows fail when run in LOCAL mode due to a native compression library issue unrelated to Catalog (AWS EMR installs, snappy library).
Set core_env property "prepare.mapreduce.map.output.compress" to "false" to disable the use of compression during Prepare dataflow LOCAL execution.
The property:
# When running Prepare in LOCAL mode, this property controls whether Pig intermediate Map job output is compressed.
# On some multi-node environments, there have been problems with native compression libraries. Setting this to false
# avoids the use of compression. True means the Pig default will be used for the environment. False explicitly disables
# compression. Default: true
#prepare.mapreduce.map.output.compress=true
Jira ID: QDCB-8265
For a loaded entity, if the field types are changed (for example modifying external metadata from float to int), and it is reloaded, the Postgres table fields will show incorrectly, still using the old data types for definition of the Postgres foreign table, though the two should resync.
Do not attempt to upgrade until the following is understood.
If upgrading from a version of Qlik Catalog prior to September 2020 there are utilities that MUST be run after Catalog is upgraded to February 2021 (4.9 release). The server may not start until the first two have been run and will log a WARN at startup until the third is run. Do NOT upgrade the server until familiar with these utilities and the information required to run them. It will take time to gather this information. Gathering the information BEFORE Catalog is upgraded will minimize downtime.
Run the utilities in this order:
This will be required if Qlik Sense Connectors have been defined in order to load QVDs.
Will need to gather networking info and certificate files from Qlik Sense servers.
May be run from any directory.
This will be required if the installation is single-node.
Will need podium_dist database info if defaults altered.
May be run from any directory.
This will be required if the installation is single-node.
Will need podium_dist database info if defaults altered.
May be run from any directory.
# This is the temporary location which houses the CSV & QVD created as a result of execution of qdc_qvd_2_csv and qdc_csv_2_qvd.sh respectively.
# The default location is set to /tmp but can be overridden using this property
#qvd.conversion.temp.directory=/tmp
# When running Prepare in LOCAL mode, this property controls whether Pig intermediate Map job output is compressed.
# On some multi-node environments, there have been problems with native compression libraries. Setting this to false
# avoids the use of compression. True means the Pig default will be used for the environment. False explicitly disables
# compression. Default: true
#prepare.mapreduce.map.output.compress=true
# For entities that are ad-hoc promoted as part of Publish to Qlik, the follow-on deletion (aka demotion) of files and
# distribution database tables will be deferred for this many hours. This prevents the Garbage Cleaner from
# inadvertently deleting data while it is being loaded into Qlik Sense. Fractional hours may be entered. Default: 8 hours.
#qlik.sense.data.deletion.deferral.period.hours=8
# The value of this property is used as a label in the drop/down. Even though there are no invalid/ names
# We think the value of this property will mostly say License Agreement OR Terms of Use
# Default: License Agreement
#license.agreement.menu.display=License Agreement
# This is the document that comes up when the button with the above text is clicked from the UI.
# This document must be put in the <apache_tomcat>/<web_apps>/<qdc_web_app>/resources folder.
# The path will then be set as resources/<document_name> as below
# Default: resources/QULA.pdf
#license.agreement.text.display=resources/QULA.pdf
# Flag to control if the searched term in Catalog will have a percent sign prepended to it implicitly.
# The term always has a trailing percent sign appended to it implicitly. If the value of this flag
# is set to false, the user must put the percent sign (%) themselves in the search term for the code
# to do wildcard search. Default: false
#prepend.leading.percent.sign.for.catalog.search=false
# The Qlik Core script path to convert QVD to CSV.
#qvd.openconnector.script.path=qlikcore-integration/qdc_qvd_2_csv.sh %prop.qvd.file.linux.folder %prop.qvd.file.entity.original.name %loadingDockLocation %loadingDockUri %qlikCoreScript %tempDir
# The Qlik Core script path to convert CSV to QVD.
#qvd.publish.script.path=qlikcore-integration/qdc_csv_2_qvd.sh %sourceDir %targetDir %targetFileName %tempDir
# The maximum size of the connection pool used to load entities from a specific JDBC source.
# Each unique JDBC URL has its own connection pool. 0 indicates do not use a connection pool and
# instead create a new connection for each load. Default: 32
#jdbc.source.pool.size=32
# The fetch size used when loading JDBC sources. Fetch size is analogous to page size, incrementally processing
# the data. If specified, the fetch size is only altered if the JDBC driver would normally use 0 or greater than
# 1,000. Some JDBC drivers, like PostgreSQL, will read _ALL_ records into memory if left to their default of 0 --
# this can result in out-of-memory. 0 indicates do not alter the fetch size. Default: 250
#jdbc.load.fetch.size=250
WAS saml.logout.url
# Logout page. The user will be redirected to this page once the session expires via a timeout. You can set this to any page
# including logged-out to get a QlikSense like logout page. Please note that for SAML & DISABLED authentication modes, this property
# is used to not only configure the landing page for session timeout, but also for logout. If the value for this is not a Qlik Catalog
# page, then the URL must start with http(s); if it's a Qlik Catalog page, it must be a jsp page name without the .jsp extension
# extension. Default: logged-out
#logout.url=logged-out
# Entity type to determine if the Publish to Qlik load script query should be generating from the internal or external
# object for the managed entity. Please note that this pertains only to JDBC entities. QVDs are already sourced locally
# in Sense. Other entity types (e.g., files) can only be published from INTERNAL to Catalog.
# Choices: INTERNAL, EXTERNAL. Default: INTERNAL
#podium.qlik.dataconnection.managed.entity.generating.from=INTERNAL
# Entity type to determine if the Publish to Qlik load script query should be generating from the internal or external
# object for the addressed or registered entity. Please note that this pertains only to JDBC entities. QVDs are already
# sourced locally in Sense. Other entity types (e.g., files) can only be published from INTERNAL to Catalog. As such,
# these entities will go through adhoc promotion to managed and demotion after publish.
# Choices: INTERNAL, EXTERNAL. Default: EXTERNAL
#podium.qlik.dataconnection.addressed.registered.entity.generating.from=EXTERNAL
Jira ID: QDCB-590
When core_env property "podium.qlik.dataconnection.addressed.registered.entity.generating.from=INTERNAL", REGISTERED and ADDRESSED JDBC entities are loaded on-demand prior to Publish-to-Qlik Sense. At the completion, the entity is "demoted" and its files and distribution tables are scheduled for deletion. The asynchronous garbage cleaner runs on a cycle of five minutes, meaning the data may be deleted before the Qlik Sense load is completed.
The deletion of these records is now deferred for eight hours. This can be adjusted in core_env.properties:
# For entities that are ad-hoc promoted as part of Publish to Qlik, the follow-on deletion (aka demotion) of files and
# distribution database tables will be deferred for this many hours. This prevents the Garbage Cleaner from
# inadvertently deleting data while it is being loaded into Qlik Sense. Fractional hours may be entered. Default: 8 hours.
#qlik.sense.data.deletion.deferral.period.hours=8
Jira: QDCB-712
qvd.openconnector.script.path property of core_env has been modified to include a temp directory parameter..
qvd.openconnector.script.path=qlikcore-integration/qdc_qvd_2_csv.sh %prop.qvd.file.linux.folder %prop.qvd.file.entity.original.name %loadingDockLocation %loadingDockUri %qlikCoreScript %tempDir
A new core_env property has been introduced as well: qvd.conversion.temp.directory
Jira ID: QDCB-826
The change can be controlled via two new core_env props:
# The value of this property is used as a label in the drop/down. Even though there are no invalid/ names
# We think the value of this property will mostly say License Agreement OR Terms of Use
# Default: License Agreement
#license.agreement.menu.display=License Agreement
# This is the document that comes up when the button with the above text is clicked from the UI.
# This document must be put in the <apache_tomcat>/<web_apps>/<qdc_web_app>/resources folder.
# The path will then be set as resources/<document_name> as below
# Default: resources/QULA.pdf
#license.agreement.text.display=resources/QULA.pdf
Jira ID: QDCB-901
Previously, the search query used to build the data displayed on the Catalog home page used multiple SQL "like" operators. The search term was concatenated with both a leading and trailing wildcard "%" character, denoting "contains". This resulted in an expensive SQL query.
Now, the default behavior is to only add a trailing "%" character, denoting "starts with". This is quicker.
If the customer desires the original behavior, they can either manually prepend a "%" character to the beginning of the search term or set core_env property "prepend.leading.percent.sign.for.catalog.search" to true.
The new property:
# Flag to control if the searched term in Catalog will have a percent sign prepended to it implicitly.
# The term always has a trailing percent sign appended to it implicitly. If the value of this flag
# is set to false, the user must put the percent sign (%) themselves in the search term for the code
# to do wildcard search. Default: false
#prepend.leading.percent.sign.for.catalog.search=false
Jira ID: QDCB-815
On at least one multi-node Catalog install, Prepare dataflows fail when run in LOCAL mode due to a native compression library issue unrelated to Catalog (AWS EMR installs, snappy library).
Set core_env property "prepare.mapreduce.map.output.compress" to "false" to disable the use of compression during Prepare dataflow LOCAL execution.
The property:
# When running Prepare in LOCAL mode, this property controls whether Pig intermediate Map job output is compressed.
# On some multi-node environments, there have been problems with native compression libraries. Setting this to false
# avoids the use of compression. True means the Pig default will be used for the environment. False explicitly disables
# compression. Default: true
#prepare.mapreduce.map.output.compress=true
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.
Table of Contents
The following release notes cover the versions of Qlik Catalog released in May 2021.
With the May 2021 release, Microsoft Internet Explorer 11 is no longer supported.
Single sign-on using SAML authentication has significantly changed. Please see the “Enabling SAML” section in the installation guide.
Qlik Catalog may now be configured to load encrypted QVDs using an engine running on a Microsoft Windows Qlik Sense server. Please see the “Loading Encrypted QVDs” section in the Qlik Catalog + Qlik Sense Integration Guide.
Logging configuration changes, for single-node installations, are now made in file WEB-INF/classes/log4j2.xml rather than log4j.xml. Formerly, a logger entry looked like:
<logger name="com.nvs.ui.interceptor.LoggingInterceptor">
<level value="info" />
</logger>
Now, in log4j2.xml, it looks like:
<Logger name="com.nvs.ui.interceptor.LoggingInterceptor" level="info" additivity="false">
<AppenderRef ref="Console" />
</Logger>
The Hive JDBC driver is no longer included by default for single-node installations.
If you want to load from a Hive JDBC source, or publish to Hadoop+Hive, you will need to get the appropriate Hive JDBC driver for your cluster. The example below allows a single-node installation to interact with Hive running on a CDH 5.16.2 cluster.
Copy the JDBC driver jar(s) to a dedicated directory (also add the three log4j2 jars from WEB-INF/lib):
$ pwd
/usr/local/qdc/jdbcDrivers/hive-jdbc-cdh5.16.2
$ ls -la
total 51360
drwxr-xr-x 6 qdc staff 204B Jan 29 17:25 .
drwxr-xr-x 7 qdc staff 238B Jan 29 16:31 ..
-rw-r--r-- 1 qdc staff 23M Jan 29 16:30 hive-jdbc-1.1.0-cdh5.16.2-standalone.jar
-rw-r--r-- 1 qdc staff 285K Jan 29 17:21 log4j-api-2.13.2.jar
-rw-r--r-- 1 qdc staff 1.6M Jan 29 17:25 log4j-core-2.13.2.jar
-rw-r--r-- 1 qdc staff 23K Jan 29 17:18 log4j-slf4j-impl-2.13.2.jar
There is already a "HIVE" JDBC driver defined in the Admin “Database Drivers” section of the UI. It must be updated to point to the above directory:
update podium_core.pd_jdbc_source_info
set alt_classpath='/usr/local/qdc/jdbcDrivers/hive-jdbc-cdh5.16.2' where sname='HIVE';
A Tomcat restart is required.
Jira ID: QDC-1285
Single-node Catalog has been upgraded to use log4j2 version 2.17.0.
Jira ID: QDCB-1023
For Publish to Qlik Sense, when publishing to an existing app, registered non-QVD entities were not being "loaded on demand". This meant that new data in the source system (e.g., a relational database table) was not seen in Qlik Sense. This issue has been addressed.
Also, when publishing to an existing app, a new LOAD or SELECT script is appended to the previous script (this allows the user to add an entity to an app). For some scenarios (e.g., when publishing REGISTERED or ADDRESSED entities), this required the user to hand-edit the script and remove a duplicated LOAD/SELECT script.
Catalog can now be configured to automatically replace the previous script. Set the following core_env property to true for this behavior:
# When publishing to an existing app, this property controls whether a new LOAD/SELECT script is appended to the end
# of the script, or if the previous script is replaced. If true, "//CATALOG-SCRIPT-START" and "//CATALOG-SCRIPT-END"
# will be included in the script, and used to demarcate the script to be replaced. Be careful if setting to true -- if
# you later add entities to the app, the previous entities will be overwritten unless moved above //CATALOG-SCRIPT-START
# or below //CATALOG-SCRIPT-END. Setting this to true is appropriate if publishing ADDRESSED or REGISTERED entities,
# using INTERNAL mode, as the publish to an existing app feature is used to force an on-demand load. Default: false
#podium.qlik.replace.previous.script=false
Jira ID: QDCB-1028
With the May 2021 release, Catalog upgraded the Spring Security SAML2 library. The service provider metadata endpoint (URI) now looks like:
https://catalog-host:8443/qdc/saml2/service-provider-metadata/catalog
However, Catalog returned a 404 (not found) when this was accessed. This issue has been fixed. Note that the above endpoint was not necessary for Identity Providers (IdPs) such as Okta and MS Azure AD.
Jira ID: QDCB-1029
When using SAML authentication, when a user with ADMIN role added a property definition, then logged out and logged in, the newly added property was not available to add to an Entity or Source. The Catalog user interface has been fixed to always [re]load property definitions on login.
Jira ID: QDCB-1030
Search dataset work properly with wildcard
Jira ID: QDCB-964
At a high level, when Publish-to-Qlik-Sense occurs, the Catalog backend: (1) creates an app; and (2) acquires a user ticket for the UI redirect to Sense. Acquisition of the user ticket may be unnecessary (when Sense uses SSO authentication) and may be problematic if the user ticket acquisition URL is proxied through an appliance that interferes with authentication.
Acquisition of the user ticket may now be skipped. The Sense redirect URL will no longer have the "qlikTicket" parameter appended to it. A new core_env property is added -- set this property to true to skip "qlikTicket" acquisition and usage.
# If true, then Catalog will _NOT_ call Sense to generate a user ticket and will _NOT_ append a ticket to either
# qlik.sense.url or qlik.sense.redirect.url. One scenario where this would be used: if qlik.sense.redirect.url is used
# and represents a single sign-on (SSO) end-point. In that case, ticket-based authentication would not be used.
# Default: false
#qlik.sense.skip.ticket=false
Jira ID: QDCB-975
When using the "Add Field" button to add a Field to an Entity, for the single-node product, a backend error occurred. This issue has been fixed.
Jira ID: QDCB-1006
When scheduling a recurring QVD Import, the selection of the "Load Data" checkbox was not saved. This setting is now correctly saved.
Jira ID: QDCB-1008
When defining a Publish Target of type "Amazon - S3 and Redshift", the "Test Connection" button only validated the S3 details. Testing the connection failed to validate the Redshift details, allowing incorrect data to be saved for URI, username and password. Now, Redshift details are correctly validated.
Jira ID: QDCB-1009
A customer requires all Catalog users imported from an Active Directory forest to share a common domain suffix in their logon name (e.g., jdoe@acme.com). The actual authentication must occur against the user's child domain (e.g., jdoe@europe.acme.com). A new core_env property "extract.realm.from.distinguished.name" enables this scenario.
In core_env.properties, it is described as:
# If true, the realm (aka domain name) will be extracted from the user's distinguished name (DN) that
# was sync'ed from Active Directory using LDAP. This allows a global user name of "jdoe@acme.com" # to be entered at the login page, but the authentication to occur against a child domain using a name # of "jdoe@europe.acme.com". One way to configure this scenario is as follows:
# - set core_env property ad.use.alias.as.domain.name=true
# - in Active Directory, place all Catalog users, in all domains, in a universal group
# - as an admin in the Catalog UI, name the domain alias "acme.com"
# - set the LDAP group query to filter on the universal group, (cn=universalGroupName)
# - set the domain host to be the Global Catalog server and port (typically 3268)
# - the DN for each user will be captured during AD sync, it will look something like # CN=jdoe,OU=AcmeProducts,DC=europe,DC=acme,DC=com
# - when the user logs in to Catalog, their Catalog user name is "jdoe@acme.com"
# - however, Catalog will use "jdoe@europe.acme.com" as the Kerberos principal when authenticating the user
#
# When this property is set to true and the user has a DN, properties java.security.krb5.realm and
# another.realm.username.pattern are ignored. Default: false.
#extract.realm.from.distinguished.name=false
Jira ID: QDCB-1020
Basic smoke testing of JDBC loads from an iSeries (AS/400) instance have been confirmed. Full regression testing was not completed.
Driver details:
With the May 2021 SR1 (4.10.1) release, an "AS400" Database Driver entry is automatically created. In an older release, to manually create it:
Once the driver has been defined, create a new Source Connection of type JDBC and using the AS400 driver.
Jira ID: QDCB-941
Additional security-focused HTTP response headers may now be specified in core_env.properties, using
property "additional.response.headers" -- see example content below.
If header "Clear-Site-Data" is specified, it will only be included with a response to a request for /logout
or /logged-out.
# Additional security-focused HTTP response headers, pipe (|) separated. If header Clear-Site-Data is specified,
# it will only be included with a response to a request for /logout or /logged-out. Requires restart. Default: [none]
additional.response.headers=X-Download-Options: noopen|X-Permitted-Cross-Domain-Policies: none|Pragma: no-cache|Clear-Site-Data: "cache", "cookies", "storage"
Jira ID: QDCB-954
In cases where an OS-level firewall on the Qlik Catalog node is configured to redirect traffic from 443 to 8443 to avoid specifying the port number in the Catalog URL, the license validation request does not route to https://license.qlikcloud.com. Instead, the request exits the licenses container subnet and is immediately redirected to the localhost port 8443.
Beginning with Catalog 4.10, docker-compose-qlikContainer.yml will set the docker container subnet for Catalog containers to 172.20.0.0/16:
networks:
qdc:
driver: bridge
ipam:
config:
- subnet: 172.20.0.0/16
(This subnet range may be modified in the event of a conflicting subnet within a customer's network topology.)
Additionally, the following two firewalld rules should be created to allow the Catalog containers to route requests on port 443 appropriately:
443 Redirection to 8443:
firewall-cmd --permanent --direct --add-rule ipv4 nat PREROUTING 1 -p tcp --dport 443 -j REDIRECT --to-ports 8443
Container bypass port 443 redirection:
firewall-cmd --permanent --direct --add-rule ipv4 nat PREROUTING 0 -s 172.20.0.0/16 -j ACCEPT
Jira ID: QDCB-955
The Source name "public" is reserved. This means that a JDBC schema named "public" can not be imported and loaded without taking action. During the JDBC Source and Entity definition process, the Source should be named to not conflict with "public", perhaps adding a unique suffix. There was no code change for this issue.
Jira ID: QDCB-958
A customer may have imported users from multiple directories (domains) into both Qlik Sense and Qlik Catalog. When "Publish to Qlik Sense" is selected, apps are listed and created/updated using the logged-in Catalog user (or the user specified in core_env property 'podium.qlik.username'). However, until this release, the property 'qlik.sense.active.directory.name' only supported specifying a single domain. Now, multiple domains may be specified. Catalog will iterate through the combinations of domain-and-user until a combination is found that has previously logged into Qlik Sense. This matched user will then be used to list and create/update apps. If multiple domains are specified, two additional properties are needed.
The revised core_env property and two additional properties are:
# Directory name (aka domain name) which is combined with either the logged
# in user name or property 'podium.qlik.username'. Qlik Sense applications are
# then listed and created/updated using the user represented by combining the
# directory and user names. This user should have previously logged in to Qlik
# Sense. Required property when 'is.publish.to.qlik.enabled' is set to true.
# Multiple directories may be specified by using commas to separate each. In this
# case, Qlik Sense will be queried for each directory\user combination -- if that
# user previously logged in, that directory\user combination will be used for
# Publish to Qlik operations.
#qlik.sense.active.directory.name=
# If multiple directories were specified in property 'qlik.sense.active.directory.name',
# then a Qlik Sense 'RootAdmin' user is required in order to query Qlik Sense. Enter the
# directory and user names of a 'RootAdmin' user.
#qlik.sense.root.admin.directory.name=
#qlik.sense.root.admin.user.name=
Jira ID: QDCB-963
The primary database view (pd_dashbrd_with_fld_tag_v) supporting text search in the Catalog module (the product home page) has been restructured.
Previously, performance degraded as the number of search matches increased. A search match returning 10,000+ entities (paged in increments of 100) was executing in approximately 30 seconds.
With the restructured view, this same search now executes in less than 3 seconds (as measured at the server, not inclusive of network transport or browser rendering).
Jira ID: QDCB-966
When importing Business Metadata, multiple tags should appear as distinct, separate tags in the Catalog UI and database. However, due to a defect, the discrete tags were concatenated as a single string, when the file format was XLS. This issue has been fixed. The issue was not present with file format CSV.
Jira ID: QDCB-988
Customer reports server out-of-memory or UI hang when attempting to create Security Group with all Sources and Entities (28 Sources, 14,000+ Entities).
Both are related to a poorly structured query producing a large result set, large enough that either the server exhausted heap memory, or the UI could not process the resulting data.
The backend query has been optimized, as well as what is returned. For the customer dataset, 11.6 MB is now returned rather than 2.3 GB.
The entire round trip to the server + display takes about 35 seconds on a development server, which is long, but is no longer a hang. Roughly 15 seconds are spent at the server generating the result, and 20 seconds is spent by the UI processing and displaying the result.
Beginning with the May 2021 release, only Apache Tomcat 9 is supported, and the installer will prohibit other versions. If using Tomcat 7, please first initiate a migration to Tomcat 9 before installing this release. Then, when installing, the upgrade option (-u) is NOT used.
Step |
Sample Commands |
Shutdown and rename old Tomcat 7 |
cd /usr/local/qdc (or cd /usr/local/podium) ./apache-tomcat-7.0.<VERSION>/bin/shutdown.sh mv apache-tomcat-7.0.<VERSION> old-apache-tomcat |
Download and expand Tomcat 9 |
wget https://apache.claz.org/tomcat/tomcat-9/v9.0.45/bin/apache-tomcat-9.0.45.tar.gz tar -xf apache-tomcat-9.0.45.tar.gz rm apache-tomcat-9.0.45.tar.gz |
Copy core_env.properties from old Tomcat 7 to new Tomcat 9 |
cp old-apache-tomcat/conf/core_env.properties apache-tomcat-9.0.45/conf/ |
Extract server.xml from podium.zip and copy to new Tomcat |
unzip -j podium-4.10-<BUILD>.zip podium/config/tomcat9-server.xml -d . mv ./tomcat9-server.xml apache-tomcat-9.0.45/conf/server.xml |
Configure QDCinstaller.properties for Tomcat 9 |
Whether using an existing QDCinstaller.properties file from a previous install, or configuring one for the first time, ensure that it is updated to point to Tomcat 9: TOMCAT_HOME=/usr/local/podium/apache-tomcat-9.0.45 |
Finally, run the installer. Do NOT specify upgrade mode (-u), as some files should be created as if it were a first-time install. |
./QDCinstaller.sh |
At this point, Tomcat 9, when started at the end of installation, will support only HTTP on port 8080.
Verify successful Qlik Catalog startup and basic functionality.
Additional configuration will be required to configure HTTPS on port 8443, apply security headers, etc. If Tomcat 7 used HTTPS, the public-private keypair should be copied to Tomcat 9.
In addition, Tomcat 7 may have been configured as a service. It should be disabled. Tomcat 9 may be configured as a service to automatically start.
Please see the install guide for guidance on both of these.
Do not attempt to upgrade until the following is understood.
If upgrading from a version of Qlik Catalog prior to September 2020 there are utilities that MUST be run after Catalog is upgraded. Once run, the utilities need never be run again.
The server may not start until the first two utilities have been run and will log a WARN at startup until the third is run. Do NOT upgrade the server until familiar with these utilities and the information required to run them. It will take time to gather this information. Gathering the information BEFORE Catalog is upgraded will minimize downtime.
Run the utilities in this order:
This will be required if Qlik Sense Connectors have been defined in order to load QVDs.
Will need to gather networking info and certificate files from Qlik Sense servers.
May be run from any directory.
This will be required if the installation is single-node.
Will need podium_dist database info if defaults altered.
May be run from any directory.
This will be required if the installation is single-node.
Will need podium_dist database info if defaults altered.
May be run from any directory.
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.
Table of Contents
The following release notes cover the versions of Qlik Catalog released in August 2021.
Noteworthy
No longer supported
Catalog may now be installed on Ubuntu 20.04 and RHEL 8. On these platforms, podman (a tool for managing images and containers) is required. Please see either the single- or multi-node installation guide.
Catalog continues to support CentOS 7 and RHEL 7. On these platforms, docker and docker compose are required. Please see either the single- or multi-node installation guide.
The multi-node version of Catalog may now be deployed on proper edge nodes of EMR 5.33 and CDP 7 cluster environments. Please see the multi-node installation guide.
The custom build of PostgreSQL (enabling support for long schema/source and table/entity names) distributed with Catalog is now compiled with the components required to enable SSL for incoming connections. Once SSL is enabled for PostgreSQL, it will listen for both normal and SSL connections on the same TCP port and will negotiate with any connecting client (including Catalog) on whether to use SSL. Follow PostgreSQL 11 documentation for configuring and enabling SSL (https://www.postgresql.org/docs/11/ssl-tcp.html).
Do NOT attempt enablement if you are not comfortable with the database administration of PostgreSQL.
Please request draft documentation of using Catalog with FIPS and PostgreSQL SSL.
Jira ID: QDC-1285
Single-node Catalog has been upgraded to use log4j2 version 2.17.0.
Jira ID: QDCB-1024
Global search, available at the top-right of all modules except Catalog, now correctly supports filtering which fields are searched. Any one of the following four fields may be checked/unchecked to indicate if the field should be searched:
Filters: x Name x Tags x Business Name x Business Description
The selection of no fields is the same as the selection of all fields. The "Search All" option has been removed -- simply check or uncheck all of the fields. It's logical to only select one, two or three fields.
The checked filter fields are transferred to the "View all results" page when that link is clicked.
Jira ID: QDCB-1051
Every search (except the Catalog module search) would return an error if the "%" wildcard character was included in the search term. For example, global search, entity search, audit log search, etc., were all broken if text like "%day" was input. "%" is the SQL multi-character wildcard. As an aside, the SQL single-character wildcard "_" is also supported.
The issue arose because the search term was embedded in the URL path. An encoded "%" (i.e., "%25) can no longer be embedded in a URL path element. This change took effect in the May 2021 release when Catalog upgraded a library (Spring Security). "%25" is disallowed in the URL path because it enables "double encoding" of other problematic characters (like ".."), see https://capec.mitre.org/data/definitions/120.html
The solution was to move the search term from the URL path to a URL parameter. In most cases, this was straightforward and was done so on non-public APIs. In three cases, a versioned, public API needed to be changed and so a new version is introduced:
Get Entities via Search Criteria (other parameters elided)
old: /qdc/entity/v1/getEntitiesByCrit/{targetFlds}/{searchTxt}
new: /qdc/entity/v2/getEntitiesByCrit/{targetFlds}?searchText=term
Get Fields by criteria (other parameters elided)
old: /qdc/field/v1/getFieldsByCrit/{targetFlds}/{searchTxt}
new: /qdc/field/v2/getFieldsByCrit/{targetFlds}?searchText=term
Get Sources by Criteria (other parameters elided)
old: /qdc/source/v1/getSourcesByCrit/{targetFlds}/{searchTxt}
new: /qdc/source/v2/getSourcesByCrit/{targetFlds}?searchText=term
Jira ID: QDCB-1053
Several releases ago, the Catalog module search was changed from a "contains" search (SQL: like '%term%') to a "starts with" search (SQL: like 'term%'). This was done for performance reasons. A core_env property exists to enable the legacy "contains" behavior.
This release converts all of the other searches (e.g., global search at the top-right of all the other modules, source search, target search, etc.) to use the same behavior and the same override property:
# Flag to control if the searched term in Catalog will have a percent sign prepended to it implicitly.
# The term always has a trailing percent sign appended to it implicitly. If the value of this flag
# is set to false, the user must put the percent sign (%) themselves in the search term for the code
# to do wildcard search. Default: false
#prepend.leading.percent.sign.for.catalog.search=false
Jira ID: QDCB-1031
When an AD user logs in to Catalog, an audit of Qlik Sense determines the data connections to which the user has access. The name used for the audit was fully qualified (e.g., jdoe@company.com). Sense security is managed using just the user name prefix (e.g., jdoe) and not the domain suffix. The audit code has been changed to only use the user name prefix. This may have prevented any QVDs from being diplayed for the user as no data connections may have matched the fully qualified username.
Jira ID: QDCB-1043
When SAML authentication is used, if the Identity Provider metadata XML has element IDPSSODescriptor with WantAuthnRequestsSigned="true", a key-pair is required to sign requests (private key is used to sign, public key is shared in Service Provider metadata XML).
The code to do this is guarded by a new core_env property, "saml.sign.requests.using.tomcat.ssl.cert". Set it to true to enable SAML request signing if required by the IdP and if/when the following is seen: "java.lang.IllegalArgumentException: Failed to resolve any signing credential".
The Tomcat SSL key-pair from conf/server.xml will be re-used for this purpose.
Jira ID: QDCB-1021
Previously, on upgrade, core_env property "doc.webhelp.uri" had to be manually updated to the latest doc release (e.g., https://help.qlik.com/en-US/catalog/August2021/Content/QlikCatalog/Overview/Home.htm). This is now done automatically.
Jira ID: QDCB-1045
A defect was introduced in the May 2021 SR1 release preventing XML entities from being defined when using the "NextGen XML" feature (core_env property enable.new.xml.ingestion=true). An HTTP 400 response was returned to the private API call /discovery/extractMetadataFromXSDFile. This has been fixed.
Jira ID: QDCB-1046
On multi-node Catalog deployments using CDP Private Cloud 7, Prepare Dataflows may encounter the following issues when using the TEZ execution engine:
(1) 5+ minute job completion. While the job itself runs quickly, the handshake between Pig and Tez over job completion takes 5+ minutes. This overhead means Tez is not suitable for smaller Dataflows.
(2) coop.error.code.GRAPH_EXECUTION_ERROR. Pig and Tez may not agree on object serialization formats.
The workaround is to use the LOCAL execution engine for small Dataflows, and the MAP_REDUCE execution engine for larger Dataflows.
Note that Prepare uses Pig, which is not supported on CDP 7. Catalog instead includes and uses an older version of Pig.
Beginning with the May 2021 release, only Apache Tomcat 9 is supported, and the installer will prohibit other versions. If using Tomcat 7, please first initiate a migration to Tomcat 9 before installing this release. Then, when installing, the upgrade option (-u) is NOT used.
Step |
Sample Commands |
Shutdown and rename old Tomcat 7 |
cd /usr/local/qdc (or cd /usr/local/podium) ./apache-tomcat-7.0.<VERSION>/bin/shutdown.sh mv apache-tomcat-7.0.<VERSION> old-apache-tomcat |
Download and expand Tomcat 9 - NOTE: adjust version 9.0.45 to use latest 9.0.x series |
wget https://apache.claz.org/tomcat/tomcat-9/v9.0.45/bin/apache-tomcat-9.0.45.tar.gz tar -xf apache-tomcat-9.0.45.tar.gz rm apache-tomcat-9.0.45.tar.gz |
Copy core_env.properties from old Tomcat 7 to new Tomcat 9 |
cp old-apache-tomcat/conf/core_env.properties apache-tomcat-9.0.45/conf/ |
Extract server.xml from podium.zip and copy to new Tomcat |
unzip -j podium-4.10-<BUILD>.zip podium/config/tomcat9-server.xml -d . mv ./tomcat9-server.xml apache-tomcat-9.0.45/conf/server.xml |
Configure QDCinstaller.properties for Tomcat 9 |
Whether using an existing QDCinstaller.properties file from a previous install, or configuring one for the first time, ensure that it is updated to point to Tomcat 9: TOMCAT_HOME=/usr/local/podium/apache-tomcat-9.0.45 |
Finally, run the installer. Do NOT specify upgrade mode (-u), as some files should be created as if it were a first-time install. |
./QDCinstaller.sh |
At this point, Tomcat 9, when started at the end of installation, will support only HTTP on port 8080.
Verify successful Qlik Catalog startup and basic functionality.
Additional configuration will be required to configure HTTPS on port 8443, apply security headers, etc. If Tomcat 7 used HTTPS, the keystore (jks file) containing the public-private keypair should be copied to Tomcat 9.
In addition, Tomcat 7 may have been configured as a service. It should be disabled. Tomcat 9 may be configured as a service to automatically start.
Please see the install guide for guidance on both of these.
Do not attempt to upgrade until the following is understood.
If upgrading from a version of Qlik Catalog prior to September 2020 there are utilities that MUST be run after Catalog is upgraded. Once run, the utilities need never be run again.
The server may not start until the first two utilities have been run and will log a WARN at startup until the third is run. Do NOT upgrade the server until familiar with these utilities and the information required to run them. It will take time to gather this information. Gathering the information BEFORE Catalog is upgraded will minimize downtime.
Run the utilities in this order:
This will be required if Qlik Sense Connectors have been defined in order to load QVDs.
Will need to gather networking info and certificate files from Qlik Sense servers.
May be run from any directory.
This will be required if the installation is single-node.
Will need podium_dist database info if defaults altered.
May be run from any directory.
This will be required if the installation is single-node.
Will need podium_dist database info if defaults altered.
May be run from any directory.
Qlik Catalog August 2021 SR2 - Application
Qlik Catalog August 2021 SR2 - Installer
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.