Table of Contents
The following release notes cover the versions of Qlik NPrinting released in May 2022 SR4.
Qlik Sense February 2023 is supported starting from this version.
QlikView 12.70 SR2 is supported starting from this version.
Jira issue ID: OP-95794
Improved Qlik NPrinting Engine code to remove this message from logs: "Command=Doc::GetFieldDescription;Result=8;ResultText=Warning: Invalid parameters" . This message would appear in Qlik Sense Engine System logs when exporting Qlik Sense tables, columns, and cell data during the reloading of Qlik Sense connection caches.
Jira issue ID: OP-95807
Qlik NPrinting Messaging service (RabbitMQ) has been upgraded to 3.11.7 and Erlang to 25.2.
Jira issue ID: OP-95792
The size of images created from linked pictures was modified when exporting an Excel template in PDF.
Jira issue ID: OP-95768
The error: "Object reference not set to an instance of an object" was shown when previewing an Excel report with merged cells.
Jira issue ID: OP-95791
Excel native charts were displayed with axes labels and legend, even when the source table or level had no data.
Jira issue ID: OP-95805
Table and column tags from Qlik Sense connections were displayed in generated reports, instead of the table or column headers when the table had no data as result of applied filters.
Jira issue ID: QV-23632
QlikView On-Demand extension had incorrect alignment when using some locales, like French. This was because those strings were longer than the English version.
Jira issue ID: OP-95822
The Log4net library was updated also in Qlik NPrinting Designer to solve CVE-2018-1285. Qlik NPrinting Server and Engine were not affected.
Jira issue ID: OP-95796
Preview from Designer and publish tasks could fail with the error message: “ERROR: Newtonsoft.Json.JsonReaderException: The reader's MaxDepth of 64 has been exceeded”.
Jira issue ID: OP-95777
Thanks to the permission query optimization, Web Console has improved performance, in particular for environments with a lot of Qlik NPrinting apps.
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
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. 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.
To upgrade to Qlik NPrinting May 2022 SR4, 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 SR4.
If you have a version of Qlik NPrinting older than 17.3, you must f irst upgrade to Qlik NPrinting 17.3. Then you
must upgrade to a version f rom April 2018 to May 2021 SR4 before you can upgrade to Qlik NPrinting May
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
After backup, you must follow the instructions for upgrading on the help site page Qlik NPrinting upgrade.
If you are upgrading to May 2022 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 May 2022 SR4 Server.
Setups are available at https://community.qlik.com/t5/Downloads/tkb-p/Downloads
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.