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

Resolution

Ensure you do not have any 3rd party extensions running in the browser, such as AdBlock or similar. Disable or remove them and verify the Create Report button is once again available.

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.

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 II, Season I
• Top 10 Tips Part 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.

 

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.

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

A Binary Load on a Qlik Sense App located in the Qlik Sense App share fails. 

The following error is logged in the Script Log: 

Environment:

Qlik Sense Enterprise on Windows 
QlikView 

There are four main requirements for a successful binary load:

1. Binary load must be the first statement in the load script
2. Only one binary load statement per script
3. The source QVW or QVF file must be available during the entire binary load*
4. The reloading user must have access to read the source QVW or QVF file*

*Binary Loads from live Qlik Sense Apps are not supported in Qlik Sense Enterprise on Windows.

Example: BINARY [SenseAppID];  (for example BINARY 2d405d18-ddd3-5353-5128-adce12e482bd;)

QVF files in the Server Apps folder are read/written by Engine service when:

1. When users are doing modifications on those apps, so a file lock will be always possible to happen on those files at any moment.
2. In a multi-node environment, apps are constantly being synchronized(called 'binary sync) onto all nodes, which means any changes on such app from any node will have the possibility to lock the app.
3. And some 'binary sync does not happen instantly. The sync actions will be delayed for several hours when the system load is high. So the file lock is very unpredictable.

During these operations, those files may be locked and causing reload task failure.

Resolution

For Qlik Sense:

Do binary load on static QVF/QVW files if necessary, or load QVD files generated by other QVD generators.

What to generally consider:

• Binary load is not the first command line in the script
  It is a requirement that binary load is the first executable command in the load script. See below online help references:
  Qlik Sense: Binary Load
  QlikView: Binary Load 
   
• The source application is Section Access protected
  The reloading user must be allowed to access and open the file being targeted in the binary load. This means that the QlikView or Qlik Sense service user must be included in the Section Access table. 
   
• Source QVW is updated by another task during binary load
  No other task can update the source QlikView (QVW) or Qlik Sense (QVF) application file during the binary load. 
   
• Source QVW is locked by 3rd party process, like anti-virus or backup
  No other software can lock the source QlikView (QVW) or Qlik Sense (QVF) application file during the binary load. 
   
• Source QVW is located on a file share, and file share access is interrupted by network problem
  Any file share hosting the source QlikView (QVW) or Qlik Sense (QVF) application file must be available during the binary load.

Storing a table containing NULL value to a txt or qvd file fails with error General Script Error in statement handling

For example, the following piece of the script fails with the above error when executed:

DataTable: 
LOAD * INLINE [ 
NP 
1 
]; 

LEFT JOIN
LOAD  * INLINE [ 
NP, AD 
2, test 
]; 

STORE AD FROM DataTable INTO [lib://Temp/test.csv] (txt); 

Environment:

• Qlik Sense Enterprise on Windows , November 2018 IR to Patch 4 versions

Resolution:

• Verify if there are extra and unintended characters in any of the column names (blank spaces, extra letters). Remove them and run the script again. In addition, see IsNull - script and chart function which may help with troubleshooting.
• Verify that sufficient disk space is available. 
• This issue was reproduced in lab only in the November 2018 releases and not on newer builds. There was no fix officially produced for the problem found on November 2018. Note that November 2018 is no longer a supported version, so upgrading to a newer release to check if issue is resolved would be required. See Qlik Sense, QlikView, NPrinting, Qlik Insight Bot End of Support Date 

If you experience the issue in an up to date Sense environment, connect with our active Qlik Community for creative application development assistance and ideas.

QlikView QVD files contain lineage information of the stored data. 

Environment:

QlikView any version

The lineage information can be found in the QVD file XML header and might look like below, with connection details and the SQL statements used during reload. 

Resolution:

1. Open Qlikview Desktop client 
2. Go to Help > About Qlikview...
3. Right click the QlikView logo in the bottom right corner
4. Highlight the AllowDataLineage value
5. Set the value to -1 to disable the Lineage information
6. Click Set to store the value change
7. Close the settings and about dialog boxes
8. Reload the QVD generator application
   
   

1. Open the QlikView Server’s batch settings.ini file in a text editor. Default file path; C:\Windows\System32\config\systemprofile\AppData\Roaming\QlikTech\QlikViewBatch\Settings.ini
2. Add AllowDataLineage=-1 in the [Settings 7] section of the settings file. 
3. Save the settings file and close text editor
4. Restart QlikView Server, to trigger loading of the altered settings 
5. Reload the QVW file from QlikView management console to see that the setting has been changed
6. To enable the lineage information follow the steps above, but set the Value to 0 instead of -1 in step 5.

QlikView and Qlik Sense load either missing or additional zeros, compared to the values in the data source. 

For example data like in the below script is loaded with incorrect leading zeros. 

LOAD * Inline [
F1, F2
1, a
01, b
02, c
2, d
];

On the second row the leading zero is missing, and on the fourth row, there is an unexpected additional leading zero.

Environment:

QlikView 
Qlik Sense Enterprise on Windows 
Qlik Cloud 

Cause:

The observed behaviour is a part of fundamental Qlik engine functionality and data compression technique. 

In short, this means that Qlik interprets and associates loaded data by best effort. As part of Qlik optimization and compression technique the same reoccurring value in a field is stored on the first occurrence only, and the following occurrence reference to the first (stored) value. This means that two values with identical numerical representation can not be stored with two different textual presentations in the same field in Qlik.

Please keep in mind that all numerical values in Qlik act as dual values. This means that they have an underlying numerical value that is used for calculations, and a textual formatted value which is the value seen in charts or as calculations results. 

In the example below four rows of data are loaded. In the field F1 there are four different value.

LOAD * Inline [
F1, F2
1, a
01, b
02, c
2, d
];

1. The first value in F1 is interpreted by Qlik as a numerical 1
2. The first value is stored as numerical value 1 with textual presentation 1
3. The second value in F1 is interpreted by Qlik as a numerical 1
4. There is already a numerical value 1 stored in the field F1, so Qlik associates the second occurrence to the first value. This means that the value 01 will be associated as a numerical 1 with presentation value 1.
5. The third value in F1 is interpreted by Qlik as a numerical 2
6. There is no other value stored in the field  F1 as a numerical 2, hence this value is stored as numerical 2 with the textual presentation value 02.
7. The fourth value in F1 is interpreted by Qlik as a numerical 2
8. There is already a numerical value 2 stored in the field F1, so Qlik associates the second occurrence to the first value. This means that the value 2 will be associated as a numerical 2 with presentation value 02.
9. The loaded data will visually not look like the data source. 
   
   
   

    

Resolution:

Identical numerical values are associated with the same textual presentation value in Qlik . For this reason, it is not possible to store the same numerical value with different textual presentation values. 

One way to resolve this is to format the values as text by using Text() during reload. 

LOAD 
    text(F1) as F1,
    F2
Inline [
F1, F2
1, a
01, b
02, c
2, d
];

This will result in the visual values looking identical to the data source. 

NOTE: Value formatted with Text() will not have underlying numerical values, hence calculations on these values is not possible. 

Scheduled tasks will fail in Qlik Sense, if the App contains Section Access while could be working fine from the script editor.

Investigating the log file <Servername>_System_Engine.txt shows a warning message similar to:

WARN    domain    System.Engine.Engine    89    6ac41964-2910-4a17-9162-c40119b2d3d6    domain\qliksense     System: DetermineAccess: Failed to access the following document af18ffcb-6b60-4546-9fa5-f385172eebec  with the user:      0         sa_scheduler    20181126T181325.903+0100    6864    7120    eaa1c5c2-1850-40cb-a490-0e6158df82b0    af18ffcb-6b60-4546-9fa5-f385172eebec     20181126T181055.000+0100    6ac41964-2910-4a17-9162-c40119b2d3d6  

On the script log you will see:

Execution Failed
Execution finished.

Qlik Sense Enterprise on Windows governs access to resources (such as Apps) through the Repository Service. An account for each service is created in the PostgreSQL database during setup, such as the sa_scheduler account above. For the Scheduler to be able to access the App during reload, this account must be added into Section Access, not the account running the actual service.

See also the help documentation:
"The INTERNAL\SA_SCHEDULER account user is required to enable reload of the script in a Qlik Management Console task." Managing security with section access

Resolution:

The following requirements must be met:

• Make sure the relevant account is added to Section Access with access ADMIN. This may be the Qlik Sense internal (non-Windows) account INTERNAL\SA_SCHEDULER or the account chosen to impersonate it during reload. See also Managing security with section access 
• The app owner must have access to all data connections or at least all data connections used in the app

Example

Section Access;
LOAD * INLINE [
ACCESS, USERID
ADMIN, INTERNAL\SA_SCHEDULER
];

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.

Support has collected a number of resources helpful for the implementation of Qlik Sense Version Control functionality.

• QS event driven cross site app promoter:  https://github.com/eapowertools/qs-event-driven-cross-site-app-promoter
• EAPowertools - QMCU- SCLite:  https://github.com/eapowertools/qmcu-sclite
• Qlik Sense Developers Help                 
• C# .NET Example: https://github.com/StevenJDH/Qlik-Sense-.NET-Example
• QRS API Endpoints (subset)  
• Qlik Branch (Garden)  https://developer.qlik.com/garden      

Qlik Partner Solutions:

• Gitoqlok: A Chrome Extension that adds source versioning control to Qlik, Gitoqlok 
  For more information from the vendor, see How to use git with Qlik Sense 
• EBIExperts Solution:  WIP: https://www.ebiexperts.com/products/
• In4BI Solution:  Platform Manager: https://in4bi

Saving an edited task in Qlik Cloud may lead to the error:

Unable to save task

Analyzing the issue with the browser's developer tools, we see that the error 500 Internal Server Error is returned. For tips on how to use developer tools, see Save network web traffic (HAR/XML file) and console logs from the browser's developer tools.

Resolution

To resolve the issue, we remove the connection to the corrupt cron job, then set the task to its correct schedule:

1. Edit the task again, set the schedule to When data is refreshed and Save. This will remove the connection to a corrupt cron job.
   
   
   
   
2. Edit the task again, this time with the correct schedule and the desired change.

Cause

There was a problem with the task's cron job in Qlik Cloud.

Environment

• Qlik Cloud

In Qlik Sense, when there is a commented out portion of the script, if "//" is deleted and the script is saved, all the text will turn black and all syntax highlighting will be lost. If pages of the script are toggled between, a message that says "we have disabled syntax highlight to maintain performance" appears and the highlighting will come back but if previous steps are followed again,commenting will also be disabled again.  

This is working as designed.

It is the current solution for dealing with deeply nested if statements. In many cases these deeply nested if blocks will cause real performance issues (crashing the browser). The best practice is to not use nested ifs when possible. The commenting/uncommenting works because we count the levels. Pretty sure 10 levels deep we trigger the perf warning. So if they comment out one and it's only 9 it won't complain.

Environment: 

Internal Investigation ID(s):

The Sense System Performance Analyzer app has been deprecated.

The Sense System Performance Analyzer (Sense System Performance Analyzer) does not show data. The reload of the app has finished successfully.

Environment

• Qlik Sense Enterprise on Windows May 2021 and later

This is expected. The app pulls platform and process performance data as well as Windows event data from the logging database. However, since the May 21 release centralized logging has been deprecated.  See Deprecation of Centralized Logging in Qlik Sense Enterprise on Windows.

Internal Investigation ID(s) 

HLP-10692