Search our knowledge base, curated by global Support, for answers ranging from account questions to troubleshooting error messages.
Qlik Sense charts may not render or display text on charts correctly.
This has been addressed in Qlik Cloud. On-premise Qlik Sense Enterprise on Windows is actively being worked on.
When using Qlik Sense with Chromium-based browsers (such as Google Chrome or Microsoft Edge) and Windows 10, text in labels and values in visualizations are sometimes not rendered correctly.
Qlik Cloud
Qlik Sense Enterprise on Windows
IM-4962
QB-18418
The Chart Exploration panel is not shown in straight tables after the upgrade to Qlik Sense May 2023 Patch 3. The option is still visible when you right click on the table, but it does not work: the table is just enlarged or an empty window appears instead of the Chart Exploration.
The problem is not present in any Qlik Sense releases previous to May 2023 Patch 3. It is fixed in Qlik Sense May 2023 Patch 6 and higher releases. The Qlik Sense August release was not affected.
In releases prior to May Patch 6, it is possible to resolve the problem on the affected releases by following these steps:
An incorrect formatting of the paths in the 'import-map.json' file causes the problem.
QB-20719, QB-21856
On IPAD & iPhone, Qlik Sense session ends immediately if a user minimizes the browser to switch to another application. Once back to Qlik Sense, the following error will be displayed
Defect QB-14264 was identified by R&D. The issue is caused by an Experimental Feature being enabled in Safari, namely: NSURLSession WebSocket
Fixed in
The issue is resolved in Qlik Sense Enterprise on Windows February 2023 and any later releases.
Additional patches which include the fix are:
For additional information, please review your version's release notes.
Workaround for previous versions:
Disable NSURLSession WebSocket in the iOS Experimental Features.
This article describes how to resolve the following issues when using Qlik NPrinting Designer:
Requirements:
If you operating an unsupported NPrinting Designer and Server, you will need to upgrade to a supported version.
Update User Interface options in MS Office Settings:
In rare cases, some organization's will actually disable drag and drop capability through windows group policy. Please check with this following article and work with your internal Windows Group Policy team to re-enable this feature as needed https://community.qlik.com/t5/Knowledge-Base/NPrinting-Designer-Drag-and-Drop-Not-Working/ta-p/1717399
Qlik NPrinting can't find supported reporting temp... - Qlik Community - 1716228
This Techspert Talks session covers:
Chapters:
Resources:
Q&A:
Q: Your multi language apps is really critical to my business as we globalise - where is there more content about how we can handle dimension name translation in line with the native Qlik langauge translations?
A: Dimension names can be renamed in the load script, but it may not be necessary, just translate the dimension labels in the app instead.
Making a Multilingual Qlik Sense App
Q: Do the objects within the new Container have to be master visualizations?
A: No, you don't need to use Master visualizations. You can add new charts to the object or drag and drop existing charts from the sheet.
Q: When will the Layout Container be available?
A: Most likely later this year
Q: After update, there is a problem with filtering a "toString" field. I can't open the application for 10 minutes. What wrong with that field? (e.g. load * inline [toString test1];)
A: Hard to tell without seeing the app and knowing what the field is. As a general rule, keep the cardinality of fields down. If I would guess toString in this case may stop the engine from optimizing the field. To learn more, read HiCs post.
Symbol Tables and Bit-Stuffed Pointers
Q: Will we be able to pin objects to certain locations on the grid? As shown, a sheet menu build using the layout container would be nice to pin to the top left corner for example?
A: In the first release positioning and size will be using percentages. So, if you would have the position 0% for both axis then it would be pinned in the corner.
Click here to see video transcript
The button object background is not displayed when exporting it as an image or PDF or when used in Qlik NPrinting reports.
This is a known defect, and a fix is included in Qlik Sense November 2023 and later versions.
This is a defect in the Qlik Sense functionality to export the background of the button object. Since Qlik NPrinting relies on Qlik Sense APIs to provide this functionality, the same issue occurs also in Qlik NPrinting reports.
QB-19943
QB-22141
ErrorCode.-2 (Object Not Found) appears randomly when navigating through sheets in an app.
When using the debugger in the browser developer tools, we can see that the object type "ColorMapModel" is returning the error.
This is a known defect and a fix is included in Qlik Sense August 2023 and later versions.
This is due to a bad handling of the ColorMapModel object type.
QB-18515
Opening a new Office report in Qlik NPrinting designer fails with:
Tags (unknown member): Invalid request. Presentation cannot be modified.
It is not possible to modify the templates. The performed changes are lost even if the templates are saved. Sensitivity labels are requested for all Office files.
It is necessary to apply a sensitivity label to the Office templates as the organisation requires. This can be done in two ways:
Option one:
Option two:
Qlik NPrinting can't automatically apply sensitivity labels to the reports templates. It is not possible to save any Office files without a sensitivity label if they are set as mandatory inside the organization. For this reason, Qlik NPrinting Designer can't save changes in the template. The loss of the label also triggers the Office error message that Qlik NPrinting Designer shows on opening.
Qlik NPrinting all supported versions
Users assigned Analyzer Licenses in Qlik Cloud can publish bookmarks as of May 2023.
Publishing of bookmarks is only available to Analyzer License Users in Managed Spaces. The correct space roles must be assigned. See App actions by space role in a managed space.
Qlik Cloud
Qlik Sense Business
Qlik NPrinting On-Demand report generation for Qlik Sense fails when connecting with Firefox 118.0.0 or with Firefox 118.0.1.
The browser Web Console tool shows an error with the CORS header: Access-Control-Allow-Origin
The report generation works with other browsers.
Upgrade Firefox to release 118.0.2 or higher.
The problem is due to a defect in Firefox fixed in the 118.0.2 version. See WWW-Authenticate: Negotiate not working cross-site since FF118 | Bugzilla.mozilla.org for more information.
A report containing an incompatible filter on a single object is not generated even if there are many other objects in the report.
This happens regardless of how the Error handling is set up as per Configuring report behavior:
Generate report. Invalid content will be replaced with placeholder images.
Invalid charts are replaced with placeholder images. They have a grey background and black overlay text that says "Invalid selections". These images are scaled according to maximum size settings in your report template. Invalid tables are replaced with empty tables with no overlay text.
Upgrade NPrinting to May 2023 SR2 or to a higher release.
The problem is due to a defect discovered in Qlik NPrinting May 2023 IR and Qlik NPrinting May 2023 SR1. It has been fixed in Qlik NPrinting May 2023 SR2.
QB-22415
The default maximum number of rows and columns in the Excel export file is:
These limitations are documented in the Qlik Engine API documentation for your specific version of Qlik Sense.
Example: ExportData method
Note however that the user may end up with errors like the following ones without passing the above limits. This could occur due to the default file size limit described in API ExportData method page, which is 1024*1024*800 for export to an Excel file (If the exported file is larger than the maximum value, then an out-of-memory error with code 13000 is returned):
It's not so much that the XLSX file has a limitation of 1024*1024*800 bytes (always important to put units on numbers). It's that an XLSX file consists of many different text files in a .zip file. Each individual (text/xml) file in there has a limitation of 1024*1024*800 bytes. For example, every sheet has an individual file, if they get over the limit the error happens. But the data in a Sheet is compressed by referencing commonly occurring cells in another file so it's not possible to calculate this size by just looking at data in the current sheet. From the user's point of view, the 1024*1024*800 number is likely meaningless; usually, a part of the XLSX file was too large during export (likely the contents of a sheet).
Review the documentation for the Qlik Sense version in use to determine the documented excel export limitations. If you get a warning or an error about limitations, make selections to limit the data you want to export and then export again.
After upgrading QlikView to May 2023 IR, charts may show as blank objects in Qlik NPrinting.
Qlik NPrinting Designer displays the images correctly in preview mode.
Qlik NPrinting Any version
QlikView May 2023 IR
Nprinting Reports: Excel, PowerPoint, PDF
This is currently being investigated.
The issue is found to be with QlikView May 2023 IR not with any Qlik NPrinting versions. It works perfectly fine with QlikView May 2022 SR2 and earlier supported QlikView versions.
Also, the problem occurs when Qlik View Server Connection is used in Qlik NPrinting connections.
QV-24977
Information on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes with the ID QV-24977 for reference.
To install or upgrade your existing Qlik NPrinting governance dashboard, simply deploy the new QVF and reload the app: NPrinting Governance Dashboard - version3
If and only if you have altered the engine.config file(s) on your NPrinting Engine computer(s) to change the default 'resolvers-count' value, then go to the 'deployment summary' sheet and enter the 'resolvers-count' value under 'Available Resolvers'. This value sets a baseline that the new concurrency metric can evaluate to ensure your NPrinting environment is not core constrained.
Please enjoy and post comments/suggestions in GitHub preferably, or in the community comments below.
Version 3.0 (4/12/2022)
-Fixed a bug introduced by NP May 2021 SR3 where the reload fails in the load script:
< Field 'id' not found FROM "nprinting"."public"."task_execution" >
-Updated background colours on the "Task Recipients" Pivot Table to green
Version 2.0
Deployment Summary Sheet:
-New KPI "Peak Connection Concurrency". This is the number of unique connections used at any one time by executing publish tasks, subscriptions, on-demand requests, or metadata reload requests. It does not include preview requests. If this number exceeds 60% of your resolver count, queuing is expected to occur and reports will take longer to run. The metric will turn red indicating it is time to add logical engine processors to your NPrinting Engine(s) to a maximum of 16 logical processors per engine.
-New KPI "Peak Execution Concurrency". This is the number of concurrent execution requests at any one time . It is the sum of executing publish tasks + executing subscription requests + executing onDemand Requests + executing Metadata reload requests. If multiple reports are running in a single publish task, it counts as just '1' in this resolver . Does not include 'preview' requests.
Report Delivery Sheet:
-New filters added
Data Connections Sheet:
-New filters added
-Section Access field (yes/no ) added
Qlik Lineage Sheet:
-New filters added
-New KPIs added: Complex reports , Medium reports, simple reports
App Content Sheet:
-new filters added
Task Recipients Sheet:
-new filters added
Execution Analysis Sheet:
-New table "Days when Concurrency Exceeded". Shows the number of days where the peak concurrency connections exceeds 60% of vResolvers.
-New table "Peak Concurrency by Day". Shows peak concurrency by day.
Report Performance Sheet:
-Container with 4 distribution plots showing execution length for publish tasks, subscriptions,ondemand requests and metadata reloads. Colored by status (green = success, red = failed)
-Container with 4 tables showing detailed executions
Users Sheet:
-New Filters added
Execution Log Messages:
-New Filters added
Load Script / Model:
- vResolvers variable set to the sum of logical processors on each NP engine found
section access field added to connections
New master date table intervalmatched to executions.
vMonthsToLoad variable determines how many trailing months to generate in the master date table (default is 3 months)
For anybody upgrading you will need to re-edit the data source in the load script and if and only if you have changed the resolvers-count setting in the NPrinting engine.config file .... then after reloading the app , go to the deployment summary sheet and update the vResolvers variable to be equivalent to the same value as 'resolvers-count' in the engine.config. If you have multiple NP engines, sum the number together and set vResolvers to the sum of the values found in the engine.config files.
Previewing Qlik NPrinting report templates in the Qlik NPrinting Designer leads to the error:
An error occurred while elaborating the entity tags.
Please check if the entities are properly placed inside their level tags.
Error message:
TemplateEntities list does not contain this column
Parameter name: templateEntities
Qlik NPrinting Designer May 2023 IR, May 2023 SR 1
Upgrade to Qlik NPrinting May 2023 SR 2.
Information on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes with the ID OP-95892 for reference.
Replace the current Qlik.Reporting.Adapters.dll file in C:\Program Files (x86)\NPrinting\Designer\libs.
For this workaround to function, the installed Qlik NPrinting designer version must be May 2023 SR1.
Upgrade to May 2023 SR2 when released.
Qlik NPrinting May 2023 SR 2
OP-95892
If a Qlik Sense Dashboard is secured with Section Access, a Qlik NPrinting report generated from it may fail if the user does not have full RDUP permissions. If only Read access has been provided, the report fails to generate with the error:
ERROR in setting limited dimension default label: Access denied [5]:Access denied(SetProperties)
This was identified as an old defect in versions of Qlik NPrinting prior to September 2020. Later versions should no longer be affected.
However, if the error occurs, verify that the user running the report has Read permissions or full permissions.
OP-9376
Qlik Cloud and Qlik Sense Enterprise on Windows only render 100 bookmarks. If more than 100 bookmarks have been created and are being viewed, specific bookmarks will need to be filtered using the bookmark search.
Qlik Sense Enterprise on Windows
Qlik Cloud
HLP-15300
Dragging and dropping the Qlik Map object onto a sheet results in the following error:
The visualization was not found on the server. This extension is not available: map ()
Inspecting the error in the browser developer tools (Developer tool console logs) shows the following error:
geo.error.WebmapInvalidkey
Invalid key
Match the serverKey between Qlik Sense Enterprise on Windows and Qlik GeoAnalytics.
The serverKey value must not be surrounded by quotes (" ").Optional: If a custom URL is used in the mapconf.json file, match the serverURL value to the custom URL in use.
Qlik Sense Upgrade or Migration. Every time Qlik Sense is upgraded or migrated, the "mapconf.json" file will be overwritten and needs to be updated again.
Qlik Sense Enterprise on Windows
Qlik GeoAnalytics
The problem occurs on buttons containing multiple actions. It can happen that these actions are not performed in the order set in the button. The result is then different from the expected one.
The issue is more common when the actions contain different selections or a "Clear selections" on a field. Sometimes, the selections seem not to be applied or it may be necessary to click twice on the button to get the desired result.
The actions may seem to be applied incorrectly because the expressions that are used for the actions in the button are all evaluated at the time the user presses the button. The actions are then applied sequentially, however with the evaluated expressions.
Evaluating the actions at the same time may lead to different results than evaluating them sequentially, especially if these actions include selections.
This is considered the designed behavior at the moment, in fact there are technical limitations preventing to apply actions sequentially. Moreover, some implementations are currently based on this behavior.
For these reasons this is considered a feature request instead of a defect.
A possible improvement would be to have an additional option where one can configure the actions flow in the button. A post has been added in our ideation program in the community.
QB-20651
This Techspert Talks session addresses the following:
Resources:
24 Days of Visualizations, season 2
Let’s Make New Charts with Qlik Sense
Click here to see video transcript