While working in an app, users may be unable to access the Expression editor. Clicking the fX (expression) button results in nothing happening. 

Both the right-side property pane and the variable editor are affected.

Resolution

The app might contain bookmarks that, for some reason, lack titles. Without titles, these bookmarks can cause unexpected behavior. If the bookmarks are private, only the owner of the bookmarks will be affected. 

Workaround:

1. Open the app's Bookmarks section (A) and identify bookmarks without titles (B)
   
   
   
   
2. Access the bookmark's Details 
   
   
   
   
3. Select Edit Details 
   
   
   
   
4. Add a Title to the bookmark
   
   
   
   
5. Click Done

Environment

• Qlik Cloud Analytics

When you need to integrate auth0 JWT Bear Token auth with Talend tRestRequest component, it is possible to use JWT Bearer Token with Keystore Type : Java Keystore *.jks to achive this.

How To

Please follow the some similar steps from Obtaining a JWT from Microsoft Entra ID | Qlik Help

1. Open https://dev-xxxx.us.auth0.com/.well-known/jwks.json in a Web browser.
   Reference: json-web-key-sets| auth0.com 
2. Copy the String value from the x5c field of the matched key and save it to a text file.
   Convert the text file to an talend-esb.cer file, for example:

   -----BEGIN CERTIFICATE-----
   MGLqj98VNLoXaFfpJCBpgB4JaKs
   -----END CERTIFICATE-----

3. Import this trusted key into your keystore JKS using Java keytool.

   keytool -import -keystore talend-esb.jks -storepass changeit -alias talend-esb talend-esb.cer -noprompt

4. Use this talend-esb.jks in tRestRequest with the following configurations

   Security: JWT Bearer Token
   Keystore File: /path_to/talend-esb.jks
   Keystore Password : changeit
   Keystore Alias : talend-esb
   Audience: "https://dev-xxxx.us.auth0.com/api/v2/"

5. Use the bear token fetched from  https://dev-xxxx.us.auth0.com/oauth/token to send request to tRestRequest defined endpoint for testing.

Environment

• Talend Studio 
• Talend ESB 

A binary load command that refers to the app ID (example Binary[idapp];) does not work and fails with:

General Script Error

or

Binary load fails with error Cannot open file

Before Qlik Sense Enterprise on Windows November 2024 Patch 8, the Qlik Engine permitted an unsupported and insecure method of binary loading from applications managed by Qlik Sense Enterprise on Windows.

Due to security hardening, this unsupported and insecure action is now denied.

Binary loads of Qlik Sense applications require a QVF file extension. In practice, this will require exporting the Qlik Sense app from the Qlik Sense Enterprise on Windows site to a folder location from which a binary load can be performed. See  Binary Load and Limitations for details.

Example of a valid binary load:

Binary [lib://My_Extract_Apps/Sales_Model.qvf];

Example of an invalid binary load:

"Binary [lib://Apps/777a0a66-555x-8888-xx7e-64442fa4xxx44];"

Environment

• Qlik Sense Enterprise on Windows November 2024 Patch 8 and any later releases

NPrinting has a library of APIs that can be used to customize many native NPrinting functions outside the NPrinting Web Console.

Environment:

Qlik NPrinting 

An example of two of the more common capabilities available via NPrinting APIs are as follows

• Connection reloads
• Publish Task executions

These and many other public NPrinting APIs can be found here: Qlik NPrinting API

In the Qlik Sense data load editor of your Qlik Sense app, two REST connections are required (These two REST Connectors must also be configured in the QlikView Desktop application>load where the API's are used. See Nprinting Rest API Connection through QlikView desktop)

• GET
• POST

Requirements of REST user account:

• Windows Authentication is required in both these connectors. The required user account is the NPrinting service account (which is also ROOTADMIN on the Qlik Sense server)
• This user account must also be a member of the NPrinting 'Administrators' Security Role on the NPrinting Server.

Creating REST "GET" connections

Note: Replace QlikServer3.domain.local with the name and port of your NPrinting Server

NOTE: replace domain\administrator with the domain and user name of your NPrinting service user account

Creating REST "POST" connections

Note: Replace QlikServer3.domain.local with the name and port of your NPrinting Server

NOTE: replace domain\administrator with the domain and user name of your NPrinting service user account

Ensure to enter the 'Name' Origin and 'Value' of the Qlik Sense (or QlikView) server address in your POST REST connection only.

Replace https://qlikserver1.domain.local with your Qlik sense (or QlikView) server address.

Ensure that the 'Origin' Qlik Sense or QlikView server is added as a 'Trusted Origin' on the NPrinting Server computer

Related Content

• Distribute NPrinting reports after reloading a Qlik App
• Extending Qlik NPrinting
• Run a Qlik NPrinting API POST command via QlikView reload script
• Troubleshooting Common NPrinting API Errors

NOTE: The information in this article is provided as-is and to be used at own discretion. NPrinting API usage requires developer expertise and usage therein is significant customization outside the turnkey NPrinting Web Console functionality. Depending on tool(s) used, customization(s), and/or other factors ongoing, support on the solution below may not be provided by Qlik Support.

Monthly monitoring of the data volume used in Qlik Cloud (Data for Analysis) is essential when using a capacity-based subscription.

This data is accessible in the Qlik Cloud Administration Center Home section:

For an overview of how the Data for Analysis is calculated, see Understanding the subscription value meters | Data for Analysis; its calculation considers the size of all resources on each day, and the day with the maximum size is treated as the high-water mark, which is then used for billing purposes. 

However, you may sometimes notice that the usage does not decrease as expected, even after reducing your app data. In such cases, it is recommended to review unused or rarely reloaded apps, as the previous app reload size may still be used for the calculation.

Resolution

To review the detailed usage, you can use a Consumption Report.

1. Distribute a consumption report; see Distributing detailed consumption reports | help.qlik.com for details on how to achieve this.
2. Review your data usage on the Data for Analysis sheet.
3. If you observe unexpected usage in apps, such as apps with reload infrequently, the is possible that the size is carried over from the previous reload.

To prevent the previous reload size from being carried over into the following month in similar use cases (specifically for apps that are not actively in use), a possible workaround is to reload apps using small dummy data to update the previous reload size of the apps.

Note that while offloading QVD files to, for example, S3 incurs no cost, any subsequent reload of those QVDs into Qlik Cloud will be counted toward Data for Analysis. Users should carefully evaluate whether this approach is beneficial.

Cause

Example case:

1. Extract external data into an app during reload.
2. Store the data as QVD files, and save the files outside Qlik Cloud (such as AWS S3).
3. Drop the source tables from the data model at the end of the script.
4. Reload completes; the final data model contains no tables.

The app is reloaded only once a month (or even less frequently) for the purpose of creating QVD files. At the end of the script, all tables are dropped, and the final app size is empty.

In this scenario, the usage of Data for Analysis won't be reset in the following month since it takes into consideration the size of loading the app. Therefore, the loading size continues to be charged in the next month as a previous reload.

Environment

• Qlik Cloud Analytics

Related Content

Qlik Cloud Analyticsの キャパシティ容量の仕様に関する解説(Explanation of Qlik Cloud Analytics capacity specification) 

The error System.Byte[] was occurring when attempting to load data from a binary data type column from MS SQL Server database.

Environment:
Qlik Sense Enterprise on Windows any version

Resolution:

This issue was resolved by creating a new column in the SQL Server database and converting the column to be varchar data type. Then this new varchar column could be read into Qlik Sense without any error.

This type of conversion function was used in the database in the process to create the new column:
Convert(NVARCHAR(MAX), "FieldName", 1) as Varchar_FieldName.

See Data Types for available Data Types in Qlik Sense. 

How to reduce the size of the Operations Monitor App or decide how much history is being stored.

Scenario: There are only 3 months of history/data in Operation Monitor app. Even though there are enough logs in Archived log folder to provide information for more months. 

Scenario 2: There are 3 months of history/data seen but less data is required due to too high traffic. 

This article explains how Operation monitor app can be displayed more or less than 3 months of history/data. Note: We do not recommend configuring the Operations Monitor to provide a history longer than 3 months as this amount of data will lead to long loading times and large apps.

Resolution:

1. Duplicate the Operation Monitor app. You can do so from the Hub or the Qlik Sense Management Console if you have access to the App.
   
   
2. Open the Qlik Sense Hub, Navigate to Work and open your copy of the Operations Monitor(1)
   
   
3. Open the Data load editor
   
   
4. Locate line 24 in the Initialize tab (first tab)
   
   
5. Line 24 will read: SET monthsOfHistory = 3
   
   
6. Modify SET monthsOfHistory = 3  to your preferred value.  The Operations Monitor will be able to load data as long as you have log files that go that far back. 
   
   Example:
   

   "SET monthsOfHistory = 3"        -- 3 Months
   "SET monthsOfHistory = 6"        -- 6 Months
   "SET monthsOfHistory = 12"      -- 12 Months​

    

7. Open a Windows file browser and navigate to: %PROGRAMDATA%\Qlik\Sense\Log (default install folder)
   
   
8. Remove all “governance” QVDs from this folder. This step is crucial for the changes to work.
   
   
9. Go to the Qlik Sense Management Console
   
   
10. Open Apps
    
    
11. Locate your copy of the Operations Monitor.
    
    
12. Click publish
    
    
13. Select the Monitoring Apps stream
    
    
14. Check the Replace existing app checkbox
    
    
15. Select the original Operations Monitor 
    
16. Click OK
    
    
17. Go to Tasks and start the Operations Monitor task
    
    
18. Your app will now show the desired number of months. 

Note: 
Please note that the reload time for that long of data will be rather long.

The reload task fails with a message like this in the document log:

or

           2017-11-10 10:16:48 0454       WHERE isnum(Sequence#)
            2017-11-10 10:16:48      Error: Field 'Sequence#' not found
            2017-11-10 10:16:48      Execution Failed
            2017-11-10 10:16:48      Execution finished.

or
 

Sequence# field not found in 'lib://SHARE/Repository/Trace/SERVERNAME_Synchronization_Repository.txt' 

The steps below apply where it cannot find any field. The field that cannot be found includes but is not limited to CounterName, ProxySessionID.

Environment:

• Qlik Sense Enterprise on Windows and Qlik Sense Monitoring apps

Cause:

QLIK-35804: Occasionally when Qlik Sense services stop, they do not fully write to the logs in the expected format. 

Resolution:

Services need a restart

Restart the Qlik Sense services 

Last stop of services did not write logs in the expected format

Modify the License and Operations Monitor apps such that it will continue parsing logs even if it fails to fully parse a particular log.

1. When logged in to the server, import a new copy of the problematic app from C:\ProgramData\Qlik\Sense\Repository\DefaultApps (You will need to give it a new name, i.e. License Monitor (New))
2. Go to the Hub to the My Work section and open the application
3. Click on Open to go to the Data Load Editor
4. Go to the Run Logic section
5. It will initially look like below. For reference, the screenshots are from the Operations Monitor but the principle applies to the License Monitor as well even though the load script will look slightly different.
   
6. Wrap the section labelled working: with the following code:

   //begin ignoring errors parsing logs
   set errormode = 0;

   and 

   //end ignoring errors parsing logs
   set errormode = 1;

   This will look something like this:
   
   
7. Save the file
8. Reload from the Hub or QMC
   1. From the Hub: Click on the Load Data icon in the upper right hand corner
   2. From the QMC: Apps > Select the new License or Operations Monitor App > More Actions > Reload Now
9. Ensure that it has reloaded successfully
10. Delete the original License or Operations Monitor app
11. Rename the new copy, i.e. License Monitor (New) will be renamed to License Monitor
12. Publish the new app to the Monitoring Apps stream
13. Create a reload task to reload the new app. The default reload schedule for the default apps is to reload every hour, but you can set to this to be as frequent as your needs require.

You can set a table's background to black using the Black() function or RGB(0,0,0). It will display correctly in the table, but will not be exported as expected. The export reverts to the default color.

Black background not exported:

Resolution

This is a known defect. QCB-31540 is expected to be fixed in the next major QlikView 2025 release (Release of QlikView 12.100 IR moved to Fall 2025).

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 ID QCB-31540 for reference.

Internal Investigation ID(s)

Product Defect ID: QCB-31540

Environment

• QlikView 12.80 and QlikView 12.90

The feature allowing the Date format to be changed from the Data Manager is inaccessible from the Qlik Sense Enterprise on Windows November 2024 IR release to the SR 10 release. 

Resolution

Upgrade to the latest version of Qlik Sense Enterprise on Windows.

Workaround:

If an upgrade is not possible, change the Date Format from the Data Load Editor.

Example:

Date(Date#(YearMonth, 'YYYYMM'), 'YYYY/MM') AS YearMonthFormatChanged

Fix Version:

Qlik Sense Enterprise on Windows November 2024 SR 11 and higher.

Cause

Product Defect ID: SUPPORT-1846

Environment

• Qlik Sense Enterprise on Windows November 2024 IR to SR 10

A Managed Space member is not able to create new report tasks even with the correct space permissions set. The Create button is greyed out and cannot be clicked. The minimal managed space permissions are set:

• Can View
• Can Manage
• Can Operate

There are multiple possible root causes and solutions.

Third-Party Extensions and Browser Used

• Ensure you do not have any third-party extensions running in the browser, such as AdBlock or similar. Disable or remove them, and verify that the Create Report button is once again available.
• Ensure that you are using a supported browser. See System requirements and supported browsers for details.

Recipient File not available

• The Create Report Task button will remain 'Greyed out' until a required recipient file is uploaded. For implementation details, click the following link: Workflow

Cause

• Adblock has been found to negatively interact with the Qlik Reporting create task button and other Qlik Reporting browser elements by aggressively blocking them.
• Using an unsupported browser
• A recipient import file has not yet been uploaded

Environment

• Qlik Cloud Analytics
• Qlik Reporting

An outer set expression returns an empty selection.

Examples:

Table 1 has source data that contains a row for Beta. The inner set and outer set behave identically. 

Table 2 has source data that does not include a row for Beta. The inner set and outer set behave differently.

Resolution

To make this work as expected, add “&” to the beginning of the set expression.

Example:

{&<group1={'Beta'}>} sum( {&<Company1={'A'}>} salary1)

Cause

This behavior is caused by how sets are combined when using multiple set expressions.

If the outer set expression produces an empty set, it is ignored when the inner set expression is evaluated.

The result is that only the inner set expression is used.

Internal Investigation ID(s)

SUPPORT-3523

Environment

• Qlik Cloud Analytics

You can access Qlik Sense demo apps from https://demos.qlik.com/.

If you are looking for real-life business examples, our Qlik Gallery hosts a platform meant for sharing apps, outcomes, and ideas. It is not restricted to Qlik-provided demos and mostly consists of customer examples.

If you are looking to download demo apps:

1. Go to https://demos.qlik.com/ 
2. Select Downloadable from the available Tags
   
3. Open the App
4. A Download button will be available (if logged in)
   
   

This article explains how to avoid the "Failed to create search index" script error during reload.

A data load may fail with: 

An error occurred

Internal engine error.

The script log will show:

2017-02-28 17:17:55      Creating search index
2017-02-28 17:17:55      Failed to create search index
2017-02-28 17:17:55      Execution finished.

The cause is currently unknown. Suspected to be an App corruption caused by external influences.

Resolution

Solution 1

1. Remove all search index files from the shared location configured in your Service Cluster shared location for the app which fails to reload. To locate the AppID, see How to find App ID.
   Example: \\ShareDrive\Apps\Search\AppID folder
2. Reload the app again.

Solution 2

1. Open the Qlik Sense Management Console
2. Navigate to Engine
3. Select an engine
4. Open the tab Advanced
5. Uncheck "Create search index during reload"
6. Press Apply

Solution 3

Insert "Set CreateSearchIndexOnReload=0" in the load script.

Even if this is disabled during the reload, the search index will be created later after the first search request of users.

Solution 4

Increase the timeout value.

Rather than disabling or removing the Search Index, you can attempt to increase the timeout before the reload will error out.

To do so, you will need to modify the Qlik Sense engine settings.ini and add a customized timeout value. 

1. Follow the instructions documented in How to modify Qlik Sense Engine's Settings.ini 
2. Add SearchTimeoutLimit=40000
   Where 40000 is the default value and in milliseconds. Increase the value, for example by adding a 0 to increase it to 400000 or any value you wish to begin troubleshooting with. 

At QlikWorld 2020 I'm hosting a session called "Top 10 Visualization tips". Here's the app I used with all tips including test data. Tip titles, more details in app:

* Charts *
Parliament diagram
Scatter with trackline
Calendar Graph - Month view
Calendar Graph - Year view
Meteogram
Spiral plot
Rank chart
Slope graph
Timeline chart
Candlestick chart
Range chart
Ridgeline chart
Stream Graph
Chord diagram
Coxcomb chart
Race chart

* UI tweaks
Toolbar toggle
Hide toolbar
Hide selection bar
Hide sheet title
Hide popup buttons
Hide Pivot buttons
Hide search bar
Hide three nav
Watermark
Center titles
Highlight rows
Larger scrollbars

* Dev tips*
Scatter overlap
Persistent colors
Color thresholds
Trellis container
Responsive and mobile tips
Include from Github
Tooltip table
Radial bar charts
100% bar charts
Title and text matters more than we think
Thumbnails
Quarterly month average
Image to chart
Magic quadrant
Link to app

I want to emphasize that many of the tips are invented by others than me, I tried to credit the original author at all places when possible. Many of the tips have been published before on the Qlik Community, the app below can be viewed as my current top picks.

If you liked it, here's more in the same style:

• 24 days of visualization Season III, II, I
• Top 10 Tips Part IX, VIII, VII, VI, V, IV, III, II , I 
• Let's make new charts with Qlik Sense
• FT Visual Vocabulary Qlik Sense version
• Similar but for Qlik GeoAnalytics : Part III,  II, I

Thanks,
Patric

A Qlik application has been successfully reloaded in a tenant. The reload has stored additional tables in a QVD.

Reviewing the Dataset (QVD) in the Catalog does not show the correct number of rows after the reload. The information is not automatically updated.

The rows only update once the Compute button is clicked.

Resolution

This is currently working as expected. 

Qlik plans to provide scheduling capabilities for the Profile and Data Quality compute. No estimated release date or other details can yet be determined for this feature. 

Cause

Profiling information is not automatically refreshed when QVD files change. 

Internal Investigation ID(s)

SUPPORT-2319

Environment

• Qlik Cloud Analytics

To create a sample document follow below steps. The steps can be applied to all editions of Qlik Sense, such as Qlik Sense Enterprise on Windows and Qlik Sense Business and SaaS.

1. Open Sense (Hub or Desktop) and create a new application
2. Choose Script editor 
   
   

    

3. Press the following key combination: CTRL 0 0
4. This generates an automatic script with random data:
   
   

    

   Content:
   
   

   Characters:
   Load Chr(RecNo()+Ord('A')-1) as Alpha, RecNo() as Num autogenerate 26;
    
   ASCII:
   Load 
    if(RecNo()>=65 and RecNo()<=90,RecNo()-64) as Num,
    Chr(RecNo()) as AsciiAlpha, 
    RecNo() as AsciiNum
   autogenerate 255
    Where (RecNo()>=32 and RecNo()<=126) or RecNo()>=160 ;
    
   Transactions:
   Load
    TransLineID, 
    TransID,
    mod(TransID,26)+1 as Num,
    Pick(Ceil(3*Rand1),'A','B','C') as Dim1,
    Pick(Ceil(6*Rand1),'a','b','c','d','e','f') as Dim2,
    Pick(Ceil(3*Rand()),'X','Y','Z') as Dim3,
    Round(1000*Rand()*Rand()*Rand1) as Expression1,
    Round(  10*Rand()*Rand()*Rand1) as Expression2,
    Round(Rand()*Rand1,0.00001) as Expression3;
   Load 
    Rand() as Rand1,
    IterNo() as TransLineID,
    RecNo() as TransID
   Autogenerate 1000
    While Rand()<=0.5 or IterNo()=1;
   
    Comment Field Dim1 With "This is a field comment";​

5. Click Load Data 
6. This loads in a very simple data model that can be used to test the basic functionality of Qlik Sense.

 

Qlik provides a QlikView Converter tool to convert QlikView documents (QVW files) to Qlik Sense apps. The converter tool can be used in the Dev Hub in Qlik Sense Enterprise and Qlik Sense Desktop.

Using the tool on the Qlik Sense Dev Hub may successfully proceed by converting Dimensions, Measures, Visualizations, and Variables, but will then fail as soon as the Create app button is clicked:

Internal Server Error

The following error is shown in the QlikView converter tool:

Global ERROR UserId: User.Name4Server.com@USERDIR, Error: More than one user matching UserDirectory=USERDIRECTORY; UserId=User.Namel%Server.com

Resolution

The QlikView converter tool is provided as it is.

It is possible that some specific server configurations are not fully compatible with this tool. In some cases, user directories are not read correctly and may require the encoding system to be changed from ascii to utf8. 

If this does not work, it is possible to use the same functionality provided by Qlik Sense Desktop.

Change the encoding system:

1. Find the QSBuild.js file located in C:\Program Files\Qlik\Sense\ConverterService\node_modules\@qlik-trial\freyja-qsbuild\dist\src
2. Open the file in, for example, Notepad++
3. Set QSBuild.js to read UTF8 for AD accounts.
   
   To do so, modify the following string from: 
   

   const base64EncodedHost = FileSystem.readFileSync("C:\\ProgramData\\Qlik\\Sense\\Host.cfg", "ascii");

   to
   

   const base64EncodedHost = FileSystem.readFileSync("C:\\ProgramData\\Qlik\\Sense\\Host.cfg", "utf8");

Use Qlik Sense Desktop

1. Install Qlik Sense Desktop on a local machine
2. Work with the QlikView converter tool provided by Qlik Sense Desktop

Environment

• Qlik Sense Enterprise on Windows (Dev Hub)
• QlikView Converter