Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Search our knowledge base, curated by global Support, for answers ranging from account questions to troubleshooting error messages.
When attempting to add data files, the preview does not utilize the entire modal to display data in Microsoft Edge or Chrome browsers (latest releases) on both Qlik Sense Enterprise on Windows and Qlik Cloud.
When selecting a source data file, the preview of the data is limited to showing only one row, and the whole modal space is not being utilized.
Affected versions are Qlik Sense Enterprise on Windows:
This behavior is caused by defect QB-25217.
Fixed in Qlik Cloud Services as of the 28th of February 2024.
Fixed for Qlik Sense Enterprise on Windows on the following versions:
Use non-Chromium-based browsers such as Firefox or Safari.
QB-25217
Information provided on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes, or contact support with the QB-25217 for reference.
No scroll bar in the data files preview in Microsoft Edge or Chrome Browsers
Table is not rendered properly in Chrome/Edge while selecting data from the Data Source
The error message Wrong content node response type and other report failures can be caused by invalid applied filters or a cycle that tries to select an invalid value for the field (a value that doesn't exist in the field).
Note: By default, 'verify filter' is enforced programmatically in NPrinting 17 meaning that if a filter produces empty values in a chart, a report will not be produced and the error you will see is Wrong Content Node Type error.
Example 1:
Your source contains the Year field that contains the values 2012, 2013 and 2014 but you added a filter with Year = 2015 to the report resulting in an empty data set.
Example 2:
You added to the report the filter Year = 2014 and the Country field into the Levels node. Remember that adding a field in the Levels node is like a filter. When the report is created it is possible that a value of Country has an empty data set for the year selected. For example, there are no sales in Italy in 2014. This generates the error.
Qlik Mobile app for Qlik Cloud crashes when an app containing invalid dimensions is opened.
The Qlik Development team is currently investigating. The best workaround is to remove invalid dimensions form the applications that are used in Qlik Sense Mobile app.
This problem could be due to a defect. We have an investigation opened (QB-26065).
QB-26065
Qlik Sense shows a data download zlib error when downloading data from a Qlik Sense chart.
Qlik Sense May 2023 Patch 3 and earlier versions
Upgrade to any of the versions listed below.
Product Defect ID: QB-20708, QB-17474
Qlik Sense charts may not render or display text on charts correctly.
This has been addressed in Qlik Cloud Qlik Sense Enterprise on Windows February 2024.
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.
The behavior was improved. Upgrade to Qlik Sense Enterprise on Windows February 2024.
Qlik Cloud
Qlik Sense Enterprise on Windows
IM-4962
QB-18418
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
How many characters can be viewed as data in a table object cell and what is the maximum number of characters visible in a table cell tooltip?
This article covers table cells, including their tooltips. For custom tooltip information and limitations, see Creating custom tooltips (Qlik Cloud) and Custom tooltips (Qlik Sense on-premise).
Table object cell has a very high limit and depends on the limitation from Excel. For example, when importing from Excel, the Excel file's limitation itself is 32943 characters for Microsoft Excel 2016.
One caveat to this limitation is that likely not all of the characters will be displayed in the table cell. The number of characters displayed will depend on how wide the column displayed is made and the displayable view (definition). To view all the characters it will likely be necessary to export the data to an Excel file.
The table cell tooltip depends on the browser used when viewing the app. This limitation is not configurable or manageable by Qlik and entirely depends on the browser's native limitations as these tooltips are provided by the browser itself. Other Qlik Sense objects do not have the same character limit for their tooltips (see custom tooltips).
This article states why the default auto number format in sheet objects such as charts is set to K,M,G instead of K,M.B.
Qlik Sense Enterprise on Windows
The default number-abbreviation format for billions is set to the international SI unit of "G".
1. You are able to change this beginning in charts using a load script modification.
Use the load script statement and modify to your preference:
SET NumericalAbbreviation='3:k;6:M;9:B;12:T;15:P;18:E;21:Z;24:Y;-3:m;-6:μ;-9:n;-12:p;-15:f;-18:a;-21:z;-24:y';
2. You can also change the default that the script generates.
Do this by adding NumericalAbbreviation=3:k;6:M;9:B;12:T;15:P;18:E;21:Z;24:Y;-3:m;-6:μ;-9:n;-12:p;-15:f;-18:a;-21:z;-24:y to the Settings.ini file located here C:\ProgramData\Qlik\Sense\Engine.
Please review How to modify Qlik Sense Engine's Settings.ini for guidance on editing the Qlik Sense Engine's Settings.ini
When attempting to add data files, the Table is not rendered properly in Chrome/Edge while selecting data from the Data Source in Qlik Sense Enterprise on Windows.
Affected versions are Qlik Sense Enterprise on Windows:
This behavior is caused by defect QB-25295.
Fixed for Qlik Sense Enterprise on Windows on the following versions:
Use non-Chromium-based browsers such as Firefox or Safari.
QB-25295
Information provided on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes, or contact support with the QB-25295 for reference.
Add data files preview is not using the whole model to preview data in Microsoft Edge or Chrome Browsers
No scroll bar in the data files preview in Microsoft Edge or Chrome Browsers
Due to a defect discovered in the Qlik NPrinting Engine (May 2022 SR2) in combination with Qlik Sense client-managed connections, we advise holding on upgrading Qlik NPrinting to the May 2022 SR2 version and instead upgrading directly to SR3 (Qlik NPrinting May 2022 SR3).
Only connections to Qlik Sense client-managed are impacted on the following Qlik NPrinting version:
Qlik NPrinting May 2022 SR2
Upgrade to Qlik NPrinting May 2022 SR3.
We strongly recommend upgrading to Qlik NPrinting May 2022 SR3 once available, rather than to the SR2 release. In case you have already upgraded to Qlik NPrinting May 2022 SR2, follow the recommended workaround.
OP-95779
Qlik NPrinting May 2022 SR2
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.
When attempting to add data files through File Locations, there is no scroll bar in the data files preview in Microsoft Edge or Chrome Browsers.
Affected versions are Qlik Sense Enterprise on Windows:
This behavior is caused by defect QB-25238.
Fixed for Qlik Sense Enterprise on Windows on the following versions:
Use non-Chromium-based browsers such as Firefox or Safari.
QB-25238
Information provided on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes, or contact support with the QB-25238 for reference.
Table is not rendered properly in Chrome/Edge while selecting data from the Data Source
Add data files preview is not using the whole model to preview data in Microsoft Edge or Chrome Browsers
Tabular reporting can't create table individual columns with some specific objects. This will lead to an error during the report production, so the option will be removed soon from the Add-Inn.
The fields in these columns can't neither be used in levels: this possibility will be soon removed as well.
It is possible that individual column or levels are currently present in Excel templates, especially if the report is imported from Qlik NPrinting.
In this case, the preview or the report generation by task fails with this message: " Error code: REP-500200"
The affected objects are:
It is necessary to manually remove these objects from any reports by editing them with the Tabular reporting Add-Inn.
It is possible to duplicate the same objects in table format on the Qlik Cloud Sense app and import the table in the Tabular Reporting template.
Tabular Reporting does not support these objects to create table individual column . Since they can be used in Qlik NPrinting, it is possible that they are present in imported reports.
It is finally here: The first public iteration of the Log Analysis app. Built with love by Customer First and Support.
"With great power comes great responsibility."
Before you get started, a few notes from the author(s):
Chapters:
01:23 - Log Collector
02:28 - Qlik Sense Services
04:17 - How to load data into the app
05:42 - Troubleshooting poor response times
08:03 - Repository Service Log Level
08:35 - Transactions sheet
12:44 - Troubleshooting Engine crashes
14:00 - Engine Log Level
14:47 - QIX Performance sheets
17:50 - General Log Investigation
20:28 - Where to download the app
20:58 - Q&A: Can you see a log message timeline?
21:38 - Q&A: Is this app supported?
21:51 - Q&A: What apps are there for Cloud?
22:25 - Q&A: Are logs collected from all nodes?
22:45 - Q&A: Where is the latest version?
23:12 - Q&A: Are there NPrinting templates?
23:40 - Q&A: Where to download Qlik Sense Desktop?
24:20 - Q&A: Are log from Archived folder collected?
25:53 - Q&A: User app activity logging?
26:07 - Q&A: How to lower log file size?
26:42 - Q&A: How does the QRS communicate?
28:14 - Q&A: Can this identify a problem chart?
28:52 - Q&A: Will this app be in-product?
29:28 - Q&A: Do you have to use Desktop?
Qlik Sense Enterprise on Windows (all modern versions post-Nov 2019)
*It is best used in an isolated environment or via Qlik Sense Desktop. It can be very RAM and CPU intensive.
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
Optimizing Performance for Qlik Sense Enterprise - Qlik Community - 1858594
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.
You can apply styling to customize the app based on your company standards. These styles are managed through custom themes.
To create your own custom theme, you’ll need to compile a compressed zip folder with three key components:
See Themes overview.
Once you’ve created the theme, you can upload it to your Qlik Cloud Management Console.
This Techspert Talks session addresses:
00:00 - Intro
01:06 - Simplified Authoring
08:02 - Dynamic Titles
10:04 - Adding Help using Containers
11:05 - Extending Sheets
11:44 - Show Condition
12:02 - Link apps with a button
12:46 - Using Table Indicators
14:13 - Sparklines
15:20 - Trellis Container with KPI Cards
17:14 - Custom Tooltips
19:49 - Using Dynamic Images with SVG for Custom Charts
22:15 - Q&A: How to build a Gantt Chart?
26:38 - Q&A: How to color odd rows?
27:41 - Q&A: Where can I learn about new capabilities?
29:14 - Q&A: Can we increase font size in chart?
30:09 - Q&A: Best way to customize apps?
Resources:
Sense Visualization tips apps
VI: 2022, 37 tips, V: 2021, 29 tips, IV: 2020, 32 tips,
III: 2020, 43 tips, II: 2019, 41 tips, I: 2019, 28 tips
Best of compilation: 24 days of Visualization
Same but for GeoAnalytics : 2020 (23 tips), 2019 (22 tips), 2018 (19 tips).
Financial Times Visual Vocabulary: #1 NBS, #2 Qlik only.
List of charts: “Let’s Make New Charts with Qlik Sense”
Patrik Lundblads Data Visualization blog
News about new releases: Qlik Product Innovation blog
What’s new demo app: https://demos.qlik.com/qliksense/WhatsNew
Q&A:
Coming soon...
In December 2023 I posted one Visualization tip for Qlik Sense on LinkedIn per day until Christmas Eve.
Here's the app with more details for each tip.
Number 5, 6, 12, 13, 17, 24 will work on client managed in February 2024 release. Number 7 is Qlik Cloud only.
If you liked it, here's more tips in the same style:
Similar but for Qlik GeoAnalytics :
Thanks,
Patric
In some cases Qlik Sense master measures used in charts included in Qlik NPrinting report templates are not expanded in the produced reports as described in the following community discussions:
Two workarounds:
Note: The steps above may be performed on versions of Qlik Sense from the Feb. 2021 GA release and later versions. Previous versions of Qlik Sense do not support this Qlik Sense feature/option setting.
Related Community Discussion:
Internal IDs: