Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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 May 2025 and Replicate November 2025.
Note: When upgrading, select All releases and all patches on the Downloads page to see all the available versions. The upgrade paths below refer to initial versions, but the upgrade path is identical for SR versions as well.
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.
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
This version of Replicate is compatible with the following related products only:
The following issues have been resolved in this version:
Jira issue: RECOB-11251
Salesforce case: 430619
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: In rare scenarios, an UPDATE operation might not capture an after-image value of one or more starting columns in a wide table.
Jira issue: RECOB-11215
Salesforce case: 441160
Type: Issue
Component/Process: Amazon RDS for MariaDB source
Description: Connecting to Amazon RDS for MariaDB with TLS 1.3 would fail.
Jira issue: RECOB-11197
Salesforce case: 418337
Type: Issue
Component/Process: Global Transformation
Description: Any global column transformation would remove the original endpoint column subtype of JSON and XML.
Jira issue: RECOB-10689
Salesforce case: 393670
Type: Issue
Component/Process: Security
Description: SQLite versions were upgraded to 3.51.1 due to a known vulnerability with earlier versions.
Jira issue: RECOB-10213
Salesforce case: 397801
Type: Issue
Component/Process: SAP ODP source
Description: The SAP ODP filter would not be passed to SAP when defined on an extractor running in CDC-only mode.
Jira issue: RECOB-10213
Salesforce case: 397801
Type: Issue
Component/Process: SAP ODP source
Description: The SAP ODP filter would not be passed to SAP when defined on an extractor running in CDC-only mode.
Jira issue: RECOB-10361
Salesforce case: 403874
Type: Issue
Component/Process: Notifications
Description: Test notification email would not allow the “+” sign.
Jira issue: RECOB-11122
Salesforce case: 414220
Type: Issue
Component/Process: IBM DB2 for LUW source + File target
Description: Some UPDATEs would be missing when replicating a VARCHAR column.
Jira issue: RECOB-11123
Salesforce case: 396347
Type: Issue
Component/Process: IBM DB2 for iSeries source
Description: After resuming a task, capturing changes from a table that contained binary decimal columns would cause the task to crash.
Jira issue: RECOB-11159
Salesforce case: 423853
Type: Issue
Component/Process: Sybase target
Description: Truncate table would not be performed within a multi-statement transaction.
Jira issue: RECOB-11158
Salesforce case: 416046
Type: Issue
Component/Process: Sybase target
Description: When a table on the target was defined with cluster primary key, duplicate records would cause the task to enter an endless recoverable error instead of handling it as a standard duplication error.
Jira issue: RECOB-11148
Salesforce case: 438331
Type: Issue
Component/Process: IBM DB2 for z/OS source
Description: Failure to communicate with the source database would be handled as a FATAL error in a very specific scenario.
Jira issue: RECOB-11134
Salesforce case: 442203
Type: Issue
Component/Process: Task import
Description: Importing a task would fail for task names exceeding 32 characters.
Jira issue: RECOB-11085
Salesforce case: 439592
Type: Issue
Component/Process: Task import
Description: The repctl gettaskstatus command requires the monitor_data parameter instead of it being optional.
Jira issue: RECOB-11084
Salesforce case: 439984
Type: Issue
Component/Process: Snowflake target
Description: The task would sometimes fail with a timeout error during the "COPY INTO" phase.
Jira issue: RECOB-11046
Salesforce case: 440089
Type: Issue
Component/Process: Snowflake target with Snowpipe Streaming
Description: When using Snowpipe Streaming as the loading method, loading very large tables would consume an excessive amount of memory, which would eventually result in the task crashing and entering a loop of loading and crashing.
Jira issue: RECOB-11039
Salesforce case: 437801
Type: Issue
Component/Process: Amazon Redshift target
Description: VARBYTE column in Redshift appears as a BLOB
Jira issue: RECOB-11010
Salesforce case: 437226
Type: Issue
Component/Process: Microsoft SQL Server source
Description: When specifying an Alternate backup folder which did not contain the required logs, the task would stop with an unclear message instead of issuing a warning an continuing.
Jira issue: RECOB-10997
Salesforce case: 430021
Type: Issue
Component/Process: Microsoft Fabric Target – Mirrored Database
Description: Tables would sometimes be suspended with the following error:
No data rows available
Jira issue: RECOB-10996
Salesforce case: 436142
Type: Issue
Component/Process: Microsoft SQL Server source
Description: The task would sometimes crash while reading the transaction log backup.
Jira issue: RECOB-10995
Salesforce case: 437152
Type: Issue
Component/Process: Snowflake target
Description: The Snowflake hostname for China account (.cn) would not work.
Jira issue: RECOB-10983
Salesforce case: 435943
Type: Issue
Component/Process: Table transformation
Description: Table transformation would cause the table key columns to be ordered incorrectly, even if the index was not changed in the manipulation.
Jira issue: RECOB-10970
Salesforce case: 432837
Type: Issue
Component/Process: PostgreSQL source
Description: After resuming a task that did not capture any changes for the minute before it was stopped, no changes would be captured.
Jira issue: RECOB-10967
Salesforce case: 432391
Type: Issue
Component/Process: Kafka target
Description: Excessive memory consumption during the task, that steadily increases.
Jira issue: RECOB-10936
Salesforce case: 433474
Type: Issue
Component/Process: Amazon S3 target
Description: Corrupted data file would be treated as a recoverable error instead of a fatal table error.
Jira issue: RECOB-10933
Salesforce case: 430775
Type: Issue
Component/Process: Security
Description: The org.apache.logging.log4j:log4j-core component was upgraded to 2.25.3 due to known vulnerabilities with the installed versions.
Jira issue: RECOB-10930
Salesforce case: 435016
Type: Issue
Component/Process: Oracle source
Description: Incorrect 11.12 parsing of multi-delete operation would occur when a table was created with ROWDEPENDENCIES.
Jira issue: RECOB-10880
Salesforce case: 424255
Type: Issue
Component/Process: SAP HANA source
Description: Full record mode would sometimes not work properly with tables that contained numerous columns.
Jira issue: RECOB-10878
Salesforce case: 432913
Type: Issue
Component/Process: SAP ODP source
Description: Capture from CDS View would start failing after stopping and resuming the task.
Jira issue: RECOB-10869
Salesforce case: 417562
Type: Issue
Component/Process: SAP Extractor source
Description: CDC was aborted one hour after a table was reloaded, which caused the task to enter a recoverable error.
Jira issue: RECOB-10861
Salesforce case: 420989
Type: Issue
Component/Process: SAP Hana Log based CDC
Description: When capturing changes from partitioned tables, DELETE operations would sometimes fail at the target with a 'row not found' error.
Jira issue: RECOB-10856
Salesforce case: 404961
Type: Issue
Component/Process: Metadata run option
Description: After Stopping the task and using the “Recreate all tables” run option, the task would be resumed from NOW instead of the last LSN/LRI stream position.
Jira issue: RECOB-10853
Salesforce case: 428408
Type: Issue
Component/Process: Snowflake target
Description: After replicating to Snowflake, intermediate files on Replicate server would never be deleted.
Jira issue: RECOB-10805
Salesforce case: 427401
Type: Issue
Component/Process: Oracle source
Description: Clarification of the v$transaction permission in the help.
Jira issue: RECOB-10797
Salesforce case: 427417
Type: Issue
Component/Process: Engine
Description: When a user without CREATE SCHEMA permission tried to create an existing schema, an error would be returned incorrectly.
Jira issue: RECOB-10774
Salesforce case: 423114
Type: Issue
Component/Process: Microsoft SQL Server source
Description: The task would sometimes crash after DBCC Lookup invocation.
Jira issue: RECOB-10773
Salesforce case: 427484
Type: Issue
Component/Process: Oracle source
Description: When a table contained a long raw and the maximum LOB size was greater than or equal to 64K, the task would crash.
Jira issue: RECOB-10748
Salesforce case: 420235
Type: Issue
Component/Process: Oracle source
Description: The table would be suspended if the limited LOB size value was changed and a DDL was detected.
Jira issue: RECOB-10667
Salesforce case: 421961
Type: Issue
Component/Process: MySQL-to-MySQL task
Description: When the schema of the source and target are in the same MySQL instance and a control table is included in the replication, the task would sometime fail with the following error:
Process crashed with signal 11
Jira issue: RECOB-10637
Salesforce case: 419699
Type: Issue
Component/Process: Amazon S3 staging
Description: During Full Load, tasks would sometimes fail with the following error due to the connection being actively refused by Amazon:
Unable to execute HTTP request: Connect to s3.amazonaws.com:443
The issue was resolved by implementing a retry mechanism with a maximum of three retries before the error occurs.
Jira issue: RECOB-10577
Salesforce case: 403115
Type: Issue
Component/Process: SAP extractor
Description: When using the internal parameter removeJobAfterTaskStop, failed tasks used the existing job run in SAP instead of initiating a new process, resulting in missing data on the target.
Jira issue: RECOB-10824
Salesforce case: 428945
Type: Issue
Component/Process: IBM Informix source
Description: The task would sometimes not recover automatically after database maintenance.
Jira issue: RECOB-10746
Salesforce case: 408429
Type: Issue
Component/Process: PostgreSQL target
Description: Failure to load the CSV file into the Net Changes table would return a recoverable error (resulting in an endless loop) instead of switching to one-by-one apply.
Salesforce (Incremental Load) source endpoint: In the Technical Preview version, the new option to connect via HTTPS to the proxy server is not supported.
Download this release from the Product Downloads page on Qlik Community.
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Table of Contents
Learn about new features and improvements in Qlik Enterprise Manager.
Before upgrading, it's important to review the migration and upgrade considerations below.
Qlik supports four Enterprise Manager 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 Enterprise Manager May 2025 and Enterprise Manager November 2025.
Note: When upgrading, select All releases and all patches on the Downloads page to see all the available versions. The upgrade paths below refer to initial versions, but the upgrade path is identical for SR versions as well.
If you are upgrading from Enterprise Manager April 2020 (6.6), perform the upgrades in the following order:
If you are upgrading from Enterprise Manager 6.x (starting from 6.3), perform the upgrades in the following order:
If you are upgrading from Enterprise Manager 3.3, please contact Qlik Support.
This version of Enterprise Manager is compatible with the following related products only:
Download this release from the Product Downloads page on Qlik Community.
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
This release includes updates to support Intune SDK 21.5. Other improvements are related to handling specific crash scenarios, improving app download speed in offline mode and improving security.
There is a known issue for iOS and when you are using MAM/MDM, leaving the application in background till the offline grace period set in App Protection Policy expires. We are currently working with Microsoft to resolve the issue. Issue can be found here: iOS app crash when launch app after keeping phone idle for long time · Issue #654 · microsoftconnect/ms-intune-app-sdk-ios
Download this release from the Play Store / App Store
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Table of Contents
The following release notes cover the R2026-03 release of the Qlik Talend Cloud Migration Toolkit (QTCMT) on-premises upgrade tool, allowing users to upgrade from Talend 7 to Talend 8 with much less effort. Same-version migrations, inlcuding Talend 7 to 7 and Talend 8 to 8, are also supported. For questions please contact Qlik Support.
This release introduces support for migrating a Talend Administration Center (TAC) environment to a new on-premises TAC environment. The source server inventory can be viewed directly in QTCMT before any migration begins, giving a clear picture of what exists on the source server and what needs to be migrated. The migration is broken down into three steps:
Manually upgrading a TAC environment means recreating every user, group, task, trigger, and plan by hand on a new Talend 8 TAC environment. QTCMT automates that process in a structured order, preserving all asset data and reducing the risk of errors. Users also have full control over what gets migrated, with assets being selectively chosen rather than moving everything over at once. This is especially relevant now that Talend 7 has reached end of support, with Talend 8 being the only supported on-premises version.
QTCMT R2026-03 or later is required. Check out the full documentation for prerequisites and setup steps.
Download this release from the Migration Center page on Qlik Help
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
This release includes several enhancements, along with updates to the iOS app to enable TLS 1.3 communication with Qlik Sense Server, scheduled for release in May 2026.
There is a known issue for iOS and when you are using MAM/MDM, leaving the application in background till the offline grace period set in App Protection Policy expires. We are currently working with Microsoft to resolve the issue. Issue can be found here: https://github.com/microsoftconnect/ms-intune-app-sdk-ios/issues/654
Download the new version from the App Store
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Table of Contents
The following release notes cover the initial release and version 1.3 of the QlikView to Qlik Sense Converter Tool. For questions or comments, post in the Product Forums or contact Qlik Support.
This initial release of the QlikView to Qlik Sense Converter Tool includes the following capabilities and features:
QV2QS delivers complete, ready-to-use apps with sheets, layout, expressions, and data, deployed to Qlik Cloud in under 5 minutes. Other converters produce master items from a subset of charts and tables. No sheets, no layout, no text objects, buttons, containers, or backgrounds. Calculation conditions, conditional show/hide, alternate states, and custom colors are lost.
Download this release from the Product Downloads page on Qlik Community.
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Table of Contents
The following release notes cover Qlik NPrinting February 2025 SR4 to SR5.
Jira issue ID: SUPPORT-8939
Erlang was updated to version 27.3.4.8.
Jira issue ID: SUPPORT-8618 SUPPORT-8694
The Qlik NPrinting Repository service version of PostgreSQL is upgraded to 17.9-1.
Jira issue ID: QCB-33687
The “Send test email” action always returned a success message, even when the email configuration was incorrect.
Jira issue ID: QCB-33713
Updated .Net dependencies in Qlik NPrinting Designer to mitigate known vulnerabilities.
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.
Alternate states
QlikView and Qlik Sense alternate states are not supported.
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-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. It has an internal limit, not configurable, about messages size of 512MB. Previous limit was 2GB. As consequence, is not possible to 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.
Jira issue ID: OP-95797
Images linked by using URLs in Qlik Sense tables are exported as text. This affects only Qlik Sense connections. A workaround exists for PixelPerfect templates.
Jira issue ID: HLP-17139
The sensitivity labels feature in Microsoft Office is not supported. If used, report generation and preview will fail with errors.
As a workaround to the issue, block the Active Directory domain policy that pushes the sensitivity labels requirement to domain users.
To upgrade to Qlik NPrinting February 2025 SR5, you must start from one of the following versions:
Note that the minimum starting version for a direct update has changed, starting from February 2025 SR2 (25.5.8).
If you are using a version older than May 2022 (22.15.2) you must first upgrade to a version from May 2022 (22.15.2) to February 2025 SR1 (25.5.5). You can then upgrade to the current version. Skipping this step will stop the installation process with an error message that the upgrade is not supported. Your installation will not be modified or broken in this case and you will be able to continue following the correct procedure.
To upgrade directly to Qlik NPrinting May 2022 (22.15.2), you must start from one of the following versions:
If you have a version of Qlik NPrinting older than April 2018, you must first upgrade to Qlik NPrinting April 2018 before you can upgrade to Qlik NPrinting May 2022 (22.15.2) and then to Qlik NPrinting February 2025 SR5.
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 (22.15.2) and then to Qlik NPrinting February 2025 SR5.
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 February 2025 SR5 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 February 2025 SR5 Server.
Setups are available at https://community.qlik.com/t5/Downloads/tkb-p/Downloads
About Qlik
| Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive. |
Qlik Alerting Mobile App - has been released on iOS and Android. It mainly contains compatibility with 16kB memory page sizes to continue to support Android 15+, and other improvements.
Download this release from the respective app stores
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
This release includes fixes addressing UI-related issues, along with enhancements to resolve challenges encountered when downloading larger applications on mobile devices and tablets across both iOS and Android platforms
Install this update from the App Store / Play Store
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Table of Contents
The following release notes cover version 2.2.2 of the Qlik Analytics Migration Tool. For questions or comments, post in the Product Forums or contact Qlik Support.
After executing the Migrate Applications job, Community sheets, bookmarks and stories would show on App in the Shared space, but after executing the Publish Applications job, the community content would not be available in the published App.
Download this release from the Product Downloads page on Qlik Community.
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Updates in this release
This release contains several fixes along with updates to Intune SDK 21.1.0 support, iOS 26 and MSAL 2.8 compatibility.
Install this update from the App Store / Play Store
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Table of Contents
The following release notes cover the versions of Qlik Web Connectors released in February 2026 Release (2.184.0). For questions or comments, post in the Product Forums or contact Qlik Support.
The following updates have been made to the Qlik Web Connectors Core and Web UI as well as the connectors listed.
Please pay particular attention to any connectors which may have breaking changes highlighted below.
Core Engine
Qlik Amazon S3 Connector V2
Qlik Facebook Connector
Qlik Azure Storage Connector
Qlik Dropbox Connector
Qlik Google Ad Manager Connector
Qlik Google Ads Connector
Qlik Google Drive & Spreadsheets Connector
Qlik JIRA Connector
Qlik ODATA Connector
Qlik Slack Connector V2
IP v6 addresses are not supported when you enter an IP v6 address for the purpose of white listing.
Load Balancing is not supported.
Download this release from the Product Downloads page on Qlik Community.
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Table of Contents
The following release notes cover the versions of Qlik Analytics Migration Tool released in 2.2.0. For questions or comments, post in the Product Forums or contact Qlik Support.
Download this release from the Product Downloads page on Qlik Community.
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Table of Contents
The following release notes cover the versions of the Qlik Analytics Migration Tool released in 2.1.2. For questions or comments, post in the Product Forums or contact Qlik Support.
Download this release from the Product Downloads page on Qlik Community.
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
This release contains support for 16kB memory page size for the Android app as mandated by Google for all apps targeting Android 15+, along with upgrades which will help improve security and maintainability of the dependencies within Qlik Sense Mobile Client Managed app.
Teh new version can be downloades from the App Stores.
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Table of Contents
The following release notes cover Qlik NPrinting February 2025 SR3 to SR4.
Jira issue ID: QCB-33319
Resolved an issue where report generation based on Qlik Sense apps could intermittently fail with the error “System.ArgumentNullException: Value cannot be null.”
Jira issue ID: QCB-33214
Resolved an issue where entity bindings for images, cells, variables, and formulas were not displayed in the PixelPerfect template editor, although report generation remained unaffected.
Jira issue ID: QCB-33090
Excel pivot tables containing custom background colors lost their original formatting when exported to PDF, resulting in yellow backgrounds being rendered as gray. The problem affected only the following versions: February 2025 SR3 (25.5.11) and February 2024 SR7 (24.4.28).
Jira issue ID: QCB-32600
Reports using structured references in Excel native tables could crashed during production due to a NullReferenceException.
Jira issue ID: QCB-33189
Qlik NPrinting Designer authentication dialog failed to appear when using SAML. The Qlik NPrinting Designer now uses a modern component to load the modern browser based login window instead of Internet Explorer, ensuring correct authentication behavior.
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.
Alternate states
QlikView and Qlik Sense alternate states are not supported.
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-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. It has an internal limit, not configurable, about messages size of 512MB. Previous limit was 2GB. As consequence, is not possible to 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.
Jira issue ID: OP-95797
Images linked by using URLs in Qlik Sense tables are exported as text. This affects only Qlik Sense connections. A workaround exists for PixelPerfect templates.
Jira issue ID: HLP-17139
The sensitivity labels feature in Microsoft Office is not supported. If used, report generation and preview will fail with errors.
As a workaround to the issue, block the Active Directory domain policy that pushes the sensitivity labels requirement to domain users.
To upgrade to Qlik NPrinting February 2025 SR4, you must start from one of the following versions:
Note that the minimum starting version for a direct update has changed, starting from February 2025 SR2 (25.5.8).
If you are using a version older than May 2022 (22.15.2) you must first upgrade to a version from May 2022 (22.15.2) to February 2025 SR1 (25.5.5). You can then upgrade to the current version. Skipping this step will stop the installation process with an error message that the upgrade is not supported. Your installation will not be modified or broken in this case and you will be able to continue following the correct procedure.
To upgrade directly to Qlik NPrinting May 2022 (22.15.2), you must start from one of the following versions:
If you have a version of Qlik NPrinting older than April 2018, you must first upgrade to Qlik NPrinting April 2018 before you can upgrade to Qlik NPrinting May 2022 (22.15.2) and then to Qlik NPrinting February 2025 SR4.
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 (22.15.2) and then to Qlik NPrinting February 2025 SR4.
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 February 2025 SR4 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 February 2025 SR4 Server.
Setups are available at https://community.qlik.com/t5/Downloads/tkb-p/Downloads
About Qlik
| Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive. |
Table of Contents
The following release notes cover the versions of Qlik NPrinting released in February 2024 Service Release 8.
Jira issue ID: QCB-33319
Resolved an issue where report generation based on Qlik Sense apps could intermittently fail with the error “System.ArgumentNullException: Value cannot be null.”
Jira issue ID: QCB-33189
Qlik NPrinting Designer authentication dialog failed to appear when using SAML. The Qlik NPrinting Designer now uses a modern component to load the modern browser based login window instead of Internet Explorer, ensuring correct authentication behavior.
Jira issue ID: QCB-32600
Reports using structured references in Excel native tables could crashed during production due to a NullReferenceException.
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.
Alternate states
QlikView and Qlik Sense alternate states are not supported.
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-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. It has an internal limit, not configurable, about messages size of 512MB. Previous limit was 2GB. As consequence, is not possible to 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.
Jira issue ID: OP-95797
Images linked by using URLs in Qlik Sense tables are exported as text. This affects only Qlik Sense connections. A workaround exists for PixelPerfect templates.
Jira issue ID: HLP-17139
The sensitivity labels feature in Microsoft Office is not supported. If used, report generation and preview will fail with errors.
As a workaround to the issue, block the Active Directory domain policy that pushes the sensitivity labels requirement to domain users.
If you update Qlik NPrinting to February 2024 SR8 (or any later version of the February 2024 series), the earliest February 2025 version you can move to afterward is SR2 or later.
Qlik NPrinting to February 2024 SR8 makes a large change to the Qlik NPrinting Repository (PostgreSQL). Once this change is in place, you cannot go back to the older Repository used in the February 2025 Initial Release (IR) and SR1.
To upgrade to Qlik NPrinting February 2024 SR8, you must start from one of the following versions:
Note that the minimum starting version for a direct update has changed, starting from February 2024 SR6 (24.4.25).
If you are using a version older than May 2022 (22.15.2) you must first upgrade to a version from May 2022 (22.15.2) to February 2025 SR1 (25.5.5). Then you can upgrade to the current version. Skipping this step will stop the installation process with an error message that the upgrade is not supported. Your installation will not be modified or broken in this case and you will be able to continue following the correct procedure.
To upgrade directly to Qlik NPrinting May 2022 (22.15.2), 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 (22.15.2). Then you can upgrade to Qlik NPrinting February 2024 SR8.
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 Qlik NPrinting May 2022 (22.15.2) and then to Qlik NPrinting February 2024 SR8.
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 Qlik NPrinting May 2022 (22.15.2), and then to Qlik NPrinting February 2024 SR8, from September 2018 SR3 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 February 2024 SR8 Server.
Setups are available at https://community.qlik.com/t5/Downloads/tkb-p/Downloads
About Qlik
| Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive. |
This release has upgrades to several third party dependencies used by Qlik Sense Mobile Client Managed app, improving security and maintainability.
Downloads
Download this release from respective Apple AppStore and Google PlayStore.
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
The following release notes cover the versions of QlikView released in September 2025.
Added a feature for ease-of-administration
In the QlikView Management Console, you will now be able to see any non-default settings that has been applied for the QlikView Server Service, just as you have been able to see them for the other services since QlikView 12.30.
Version upgrade of Skia to version 121.0.0.0
|
Key |
Title |
Decription |
|
QV-25497 |
FQDN for leasing license by setting “CustomLicenseServiceUrl“ env. |
New setting the “CustomLicenseServiceUrl“ is set with FQDN and overwrites "LicenseServiceUrl" env value on restart services. |
|
QV-25479 |
Alternate state value not retained when exporting |
This change fixes an issue when a user prints an object in AJAX, the object's alternate state is not restored. This means the printed report wrongly includes Current Selection in Default State instead. |
|
QV-25377 |
QlikView: Authentication redirect filtering not working |
The QlikView Authentication redirect filtering has now been fixed and is working correctly. |
|
QV-25376 |
QlikView: License tracking events not captured |
QlikView report license tracking and CAL events are now captured in the Event log. |
|
QV-25375 |
QlikView: Publisher function missing |
Fixed a problem that caused the Publisher function to disappear in the QMC |
|
QV-25371 |
QlikView: Cannot open files on server from QlikView desktop |
Fixed a problem where the files could not be opened on server from QlikView Desktop if the .qvw extension was in mixed casing or if it occurred more than once. |
|
QV-25347 |
QlikView: WebView not working on desktop when QVS has SSL enabled |
Fixed a problem that caused WebView to fail in QlikView desktop when QVS has SSL enabled in the same system. |
|
QV-25339 |
QlikView: Wrong value displayed in popup label |
Fixed a problem that caused the popup label to display the wrong value for bar charts with two expressions and no dimensions. |
|
QV-25323 |
QlikView Publisher: Additional lines added to the log file |
Fixed a problem that caused, for every task reload, an additional four lines to be added to the log file named with the current date. |
|
QV-25189 |
Unexpected selections, freezing, or disconnection |
Adjusted alt vector re-calculation not to impact cardinality of result |
|
QCB-32291 |
<CreatorDoc> tag in QVD files created with STORE empty |
Fixed a problem where the <CreatorDoc> tag in the metadata header of QVD files created with the STORE statement was empty. It is now written correctly. |
|
QCB-32144 |
Improved Alternate State Selections After Server Reloads |
We've resolved an issue that affected applications using Alternate States in server environments. Previously, after a server reload, selections in Alternate States were not correctly reapplied. Now, field selections in Alternate States are consistently maintained and correctly propagated after server reloads. |
|
QCB-31582 |
Fixed: Data Reload Issue Causing Unresponsive Behavior |
We've resolved an issue where certain data reload operations could become unresponsive, potentially causing the system to appear frozen. This problem occurred when using specific data processing functions together. |
|
QCB-31540 |
QlikView: Fixed black background color export to Excel |
We've resolved an issue in QlikView where the black background color was not correctly exported to Excel. With this fix, tables exported from QlikView to Excel now correctly display the black background color. |
|
QCB-31441 |
Table Box: Added sort option for columns in Ajax and QlikView Cloud |
Users can now sort columns in Table Boxes when using Ajax and QlikView Cloud. |
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.
Limitations
None known at time of release
If a standard Upgrade is done, new certificates will be created using the AES 256
GCM mode as part of the upgrade.
Instructions for upgrading QlikView with new certificates mode (GCM) – Before implementing this, TLS 1.2 has to be enabled for QVS to work normally.
Perform the upgrade on all machines in the cluster.
After completion, the installer will ask you to restart the machine/s.
After restart and services are running, stop all the services and open "C:\Program Files\QlikView\Management Service\QVManagementService.exe.config" and apply the following config:
<add key="InstallingNewCertificatesAndCryptoKey" value="true"></add>
If Services are clustered, all the cluster nodes also need the new certificate.
Add into resp config files for each (one on each node):
<add key="InstallingNewCertificatesAndCryptoKey" value="true"></add>
or
InstallingNewCertificatesAndCryptoKey=1 if QVS.
Start the QMS first and then rest of all services
In the QMC, go to the service’s System/setup, for example if QDS select the node and distribute the new certificates to QDS machine with Apply in setup and follow the popup instructions. Do this for one service om each node to distribute new certs mode. Stop QMS again and all services. Make above configuration false in all config/settings files
"<add key="InstallingNewCertificatesAndCryptoKey" value="false"></add>".
Start all services. All machines in the cluster shall now have the new certs mode.
If you for some reason need to downgrade to the previous version again, follow this
Support Article to re-generate certificates using the old encryption algorithm.
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/September2025/Content/QV_HelpSites/System-requirements.htm
https://community.qlik.com/t5/Product-Downloads/tkb-p/Downloads
|
Key |
Title |
Description |
|
QCB-33101 |
Missing QvConnect32 connector |
The QvConnect32 connector was missing in Qlikview server bundle due to change of build paths where the path to QvConnect32 pointed to wrong folder. |
|
QCB-32937 |
Bar chart printing fixed in Access Point |
We've resolved an issue with bar chart printing in Access Point. Previously, when using alternate states and expression conditionals, bar chart data didn't print correctly. This update ensures accurate printing of bar charts with these features. |
|
QCB-32926 |
Window Functions: Improved Handling of Calculated Fields
|
We've resolved an issue with Window Functions. Previously, fields calculated in a preceding load statement were not properly recognized by Window Functions, causing them to be incorrectly interpreted as null values. |
|
QCB-32885 |
QlikView Window function: Improvements |
Several enhancements to the Window function have been implemented and are now enabled by default in QlikView. |
|
QCB-32690 |
Excel Export: Option for Mixed Data Export
|
To choose how to export mixed data, use the setting 'ExcelExportMixedAsText'. It is set to 1 by default, to export mixed data exported as text. Set to 0 to export mixed data as integers. |
https://community.qlik.com/t5/Product-Downloads/tkb-p/Downloads