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 value of a reference line for a scatter plot chart may be beyond the displayed range and out of view. In this case, hovering over the icon indicating the reference line will not show its label tooltip.

The issue persists even if Show Label is checked.

Waterfall charts are also affected. 

No tooltip in scatter plot

tooltip works in other charts

Resolution

This behavior is being investigated as a defect (SUPPORT-3799). The expected fix release is the Qlik Sense Enterprise on Windows November 2025 release.

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 SUPPORT-3799 for reference.

Fix Version:

Qlik Sense Enterprise on Windows November 2025

Cause

Product Defect ID: SUPPORT-3799

Environment

• Qlik Sense Enterprise on Windows May 2024 to May 2025 
• Qlik Sense Desktop May 2024 to May 2025 
• Scatterplot charts and Waterfall charts

You might be experiencing an issue in data formatting where input source values with leading zeros are not being reflected in the destination.

For example, a value like "00000001“  in the source may appear as ”1“ in the target

From above example, the leading zeros are not retained in the target column( unique ID in this case) when transferring data from a BigDecimal source type to a String type

Resolution

Use the following expression in the tMap Component of Talend Studio while mapping from source to destination

"String.format("%08d", row1.InputColumn.toBigInteger())"

Cause

A BigDecimal's standard canonical string representation does not include leading zeros.
Therefore, if you need to preserve leading zeros, you must explicitly format the value accordingly.

Related Content 

For more information about BigDecimal math, please refer to Oracle Official Document as below

https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/math/BigDecimal.html

Environment

Talend Studio 

Talend Data Integration 

The Qlik Sense Mobile app displays empty streams.

Empty streams are typically not displayed when viewing the Qlik Sense hub from a browser. The Qlik Sense Mobile app will list them, regardless of content.

Example

These streams created in the Qlik Sense Management Console do not have content (apps):

The Qlik Sense Mobile app displays the empty streams:

Resolution

This behaviour is being reviewed by Qlik. See the Release Notes or contact support for details on QCB-26110.

Cause

Product Defect ID: QCB-26110

Environment

• Qlik Sense Enterprise on Windows
• Qlik Sense Mobile on-premise

After modifying the .item file to change the context values within an exported Job, the Job can no longer be imported into Talend Studio, rendering the item file invalid.

Cause

There is a signature in the .item file , if it is modified, the file will no longer be valid.

Resolution

Manual modification of the .item file is not feasible.

Environment

• Talend Studio 8.0.1

Qlik Cloud Analytics customers can now easily include highly formatted tabular or PixelPerfect reports in their automations with two new blocks:

Get PixelPerfect Report

Get Tabular Report

Report developers can create highly formatted report templates to achieve stakeholder analytics presentation requirements. Using these new blocks, automation developers can then easily configure report production from a target Qlik Sense app, using selection states to produce a report output that can be used in the business process definition.

Need to know

Passing selections for the report

• To control the data reduction, bookmark Id’s can be referenced in the block definition. The common practice would be to create a temp bookmark using the Select Field Value and Create Bookmark blocks.
• Be sure to specify in the report block the same type of bookmark as specified in the Create Bookmark block.

Move report with Create Binary File Block

• The recommended practice would be to use the Create Binary File block using the output of the report block.

Copy report with Copy To block

• A Copy To block can also be used, but note that the file name returned from the reporting services will always be a GUID with a “:” in the file name. The file should be renamed as part of the move to the target channel.

Environment

• Qlik Automate

This article explains how the session API works and the workflow.
Postman is used to perform the API call to add the session in Qlik Sense.
In the browser, developer tools or an extension can be used to set the cookie.

Authentication workflow

1. User authenticate to an external session module (This module must be built by the customer)
2. The module adds the session to the Proxy using the session API
3. The module sets the cookie for the end user
4. The end user is recognized as authenticated and can access the hub and apps.
 

Virtual Proxy settings:

It does not matter which authentication method is set on the virtual proxy as we are creating directly a session when using this method. However, the following information: Session Cookie header name, Authentication module redirect URI and Session Cookie domain are important to remember when you use the Session API. 


 

Add the session:

You will need to have the QlikClient certificate installed for the user performing this API call. More information is available in following articles:
QRS API using Xrfkey header in Postman
Export client certificate and root certificate to make API calls with Postman

In order to add a session to the virtual proxy, you need to provide the following information:
UserDirectory
UserId
Attributes (optional, these are for example groups to which the user belongs to)
Cookie value (In Qlik Sense by default, a 36 characters string such as aa051074-13a1-4f2a-842b-a64aa4d21001 is used, however this can be any value, but it must be long enough and randomized to ensure there is not 2 session cookies with the same value that are added to the virtual proxy)

Example of API call:
https://qlikserver1.domain.local:4243/qps/{virtual proxy prefix}/session?xrfkey=0123456789abcdef

Headers:

Body:
{
  "UserDirectory": "DOMAIN",
  "UserId": "User1",
  "Attributes":
    [],
  "SessionId": "aa051074-13a1-4f2a-842b-a64aa4d21001"
}

Postman:



PowerShell:

$body = '{
  "UserDirectory": "DOMAIN",
  "UserId": "User1",
  "Attributes":
    [],
  "SessionId": "aa051074-13a1-4f2a-842b-a64aa4d21001"
}'
   $hdrs = @{}
   $hdrs.Add("X-Qlik-xrfkey","iX83QmNlvu87yyAB")
   $url = "https://qlikserver1.domain.local:4243/qps/session?xrfkey=iX83QmNlvu87yyAB"
   $cert = Get-ChildItem -Path "Cert:\CurrentUser\My" | Where {$_.Subject -like '*QlikClient*'}
   Invoke-RestMethod -Uri $url -Method Post -Body $body -ContentType 'application/json' -Headers $hdrs -Certificate $cert

Set the cookie:

In Chrome, an extension such as "EditThisCookie" can be used to test that the session API works.

Open the hub and add a cookie with the following information:

Name: X-Qlik-Session-sessionvp
Value: aa051074-13a1-4f2a-842b-a64aa4d21001
Domain: domain.local
Expiration: 0001-01-01 00:00:00
HttpOnly:True
Secure:True




Save the cookie and refresh the page, make sure the address is https://qlikserver1.domain.local/{virtual proxy prefix}/hub/ when you refresh.

Now you should be logged in as the user requested in the previous API call and able to access the hub/your apps.

This article explains how to view your own and your colleague's cases in the Support Case Portal.

Steps:

1. Login to the Qlik Community
2. Click on Support in the top navigational ribbon
3. Click Manage Cases (or use the direct link: Case Portal)
   
   
   
   
4. From here, use the ribbon menu to select Cases or scroll down and click the Cases tile
   
   
   
   
5. You will be shown a list of all your cases and can now:
   
   
    
   
   1. Select fields: Helps you configure what fields you want to see in your list)
   2. Manage filters: What cases do you want to see?
       
      • Filter by Creator: Only your cases or your entire account's cases
      • Filter on Selected Fields: Allows you to drill down to specific fields
        
        Example to list only Closed cases restricted to My Cases:
        
        
        
        Tip: Don't forget to click + ADD FILTER once you have created it.
        
        
   3. Create a Case: Create a new case
      
      

Don't have access to your collogues cases? See How To View Other User Cases Within Your Organization.

Related Content:

How to create a case and contact Qlik Support 
How To View Other User Cases Within Your Organization

Content

• Introduction
• Identity Federation
• Case Study - KeyCloak Federating with Auth0
• User Experience and Security
• Final Thoughts

Introduction

Qlik Cloud is designed to support a single interactive Identity Provider (IdP) per tenant.

As my friend @DaveChannon explains in Why Qlik doesn't support multiple interactive identity providers on a Qlik Cloud tenant, only one interactive identity provider can be enabled at any one time for Qlik Cloud (Which includes Qlik Cloud Analytics and Qlik Talend Cloud Data Integration).  Without restating the points Dave made, the short answer is we do not plan to change this as we don't consider this good practice.

So, if your organisation needs to support multiple IDPs, what can you do?  There are many use-cases that require this, such as:

• Providing access to external parties without adding them to your Organisation's IDP.
• OEM use-cases with customers who have their own IDPs
• Company mergers (This is one we've used ourselves a few times)

These are just a few examples but this is a very common use case for most large organisations.  So what do you have to do?  Well, you could solve this with multiple tenants, but that's often a high-maintenance solution and isn't ideal.  That's why, as Dave mentioned, we recommend that customers use Identity federation to address this. 

Identity Federation

Identity federation is a mechanism that links a user's identity across multiple identity management systems, allowing them to access different applications and resources without needing separate logins or credentials.  Almost all major providers support this.  For example, these IDPs all support federation:

Case Study - KeyCloak Federating with Auth0

So, how complex is this,s and how does it look to my users and Qlik Cloud tenant?

 

I set up a simple example of this using KeyCloak and Auth0. The way this works is:

1. The user tries to connect to their Qlik Cloud tenant
2. Qlik sends the user to KeyCloak for authentication
3. KeyCloak provides the user the option to either log in directly with KeyCloak or be directed to Auth0 to log in.
4. After logging in, KeyCloak received user metadata, such as e-mail, groups, etc.
5. KeyCloak then provides this to Qlik Cloud
6. The user gains access to Qlik Cloud.

 

 

While this is not a 'how-to' article, at a high level, what I've set up is:

1. KeyCloud is the IDP for my Qlik Cloud tenant:
   
   
   
   
2. In Keycloak I have my Groups and users set up as group members:
   
   
   
   
   
   
   
   
   
3. And I have also set up Auth0 as an Identity provider for KeyCloak:
   
   
   
   
4. And hard-coded the 'External' group to any users coming from Auth0:
   
   
   

 

This may not always be what you want to do.  You may wish to use the groups coming from Auth0 also, and that is possible, but not needed for my use case.

Finally, here are my users set up in Auth0:

 

User Experience and Security

So what happens when I log in?

First, let's look at jane@qmi.com.  Jane is set up in KeyCloak. After opening the URL for our Qlik Cloud tenant, I am redirected to the keycloak login screen:

 

 

I can log in directly here or choose to sign in with Auth0.  Jane logs into KeyCloak directly and is then sent back to the Qlik Tenant:

 

 

To understand what information Qlik Clouid has been provided, we can append "/api/v1/diagnose-claims" to the end of our tenant URL. This will show us the metadata Qlik has received about Jane, such as: 

 

 

We are most concerned about Jane's groups, as that is how we will control access. Jane is in the Finance and Human Resources groups. 

In our tenant, we have the following spaces and access rules:

Space Name	Space Type	Groups with Access
External	Managed	External:  Read Only
External_development	Shared	Finance: full access Sales: full access Human Resources: full access
Finance	Shared	Finance: Read Only
Sales	Shared	Sales: Read Only
Human Resources	Shared	Human Resources: Read Only

 

So Jane sees the Finance, Human Resources, and External_development spaces:

 

 

 

What happens when a user logs in through Auth0? This time joe.public@company1.com will log in via Auth0:

 

 

As this user has never logged in before, KeyCloak asks for some details:

 

 

After logging in, we can look at the "/api/v1/diagnose-claims" endpoint to see the user's metadata.  We see the External group, which we hard-coded for Auth0 users in KeyCloak:

 

And when looking at the user's space access, we can only see the External space as expected:

 

Final Thoughts

This is a simple example I put together in a couple of hours. I selected KeyCloak and Auth0 simply because I have some experience with them - most IDPs could do this (and also, I could have chosen to reverse the order and have Auth0 as the primary IDP).

Neither Qlik nor I make any specific recommendations as to what identity providers customers should use.

While we haven't looked at it here, it's also possible to use social services (such as LinkedIn, GitHub, Facebook, etc.) as external Identity providers, which may well be a better solution for some use-cases. And you can support many of these at the same time as your needs require.  

If you require assistance in this, your friendly neighbourhood Qlik Services team can assist, as can our partners.  

Talend Administration Center (TAC) git and nexus passwords are not being stored normally. After every restarting of the TAC services, the password has to be applied again.

A review of the Technical Log shows the following error: 

The value can't be decrypted java.lang.IllegalArgumentException: Required master key master.key.<Date> not found

Resolution

1. Clear Talend Administration Center Cache
   • Stop Talend Administration Center services
   • Navigate to <Apache Tomcat>\ ‘Temp’ and ‘work’ folders and clear contents
   • Do not start TAC services yet. 

    

2. Rotate Talend Administration Center's Masterkey
   • Navigate to <TalendAdministrationCenterInstallationDirectory>/apache-tomcat/webapps/org.talend.administrator/WEB-INF/classes/configuration.properties file and set the following property to true

     configuration.dbadmin.enable=true

   • Start Talend Administration Center.
   • In the Database configuration page after the database configuration has been tested, click “Change master key' and complete rotation steps.
   • Login to Talend Administration Center and re-insert the Passwords.  
   • Restart Talend Administration Center Service to test the solution.

Cause

There might be some mess with Master keys probably during Migration to patch or Master keys became corrupted.

The master.key parameter is mandatory for encoding and decoding all sensitive information. If this parameter is missing, Talend Administration Center can not work properly (there was some encryption algorithm change between version) , So first of all rotate the master key.

Related Content 

For more information about how to clear Talend Administration Center Cache, please check below article

How-to-clear-the-Talend-Administration-Center-TAC-cache

Environment

Talend Administration Center 

This article provides a guide on installing Qlik Replicate on a docker image.

Overview

1. (Optional) Remove older versions of Docker
2. Install Docker on the host Linux Server
3. FTP upload the rpm file to the Linux Server folder
4. Follow the Installing Qlik Replicate on docker steps
5. Prepare the docker build files
6. Modify the Dockerfile
7. Build the docker image
8. Startup and run the docker image

Steps

1. (Optional) Remove older versions of Docker
   

   sudo rpm -qa|grep docker 
   sudo yum remove docker docker-client docker-client-latest docker-common docker-latest docker-laster-logrotate docker-logrotate docker-engine

2. Install Docker on host Linux Server

   sudo yum install -y yum-utils device-mapper-persistent-data lvm2  
   sudo yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
   
   sudo yum install --allowerasing docker-ce docker-ce-cli containerd.io
   
   sudo systemctl start docker
   sudo systemctl enable docker  
   

3. FTP upload the Qlik Replicate rpm installation file to Linux Server folder "/kit" The /kit directory is a temporary folder used to store installation files. In the example below, the RPM file is areplicate-2024.5.0-357.x86_64.rpm. Once the installation is complete, the entire /kit folder can be safely deleted.
4. Follow the Installing Replicate on a docker steps

   mkdir -p /kit/ar_docker
   cd /kit
   rpm2cpio areplicate-2024.5.0-357.x86_64.rpm | 	cpio -iv --make-directories --no-absolute-filenames -D ar_docker/ ./opt/attunity/replicate/addons/samples/docker/*
   mv ./ar_docker/opt/attunity/replicate/addons/samples/docker/* ./ar_docker
   rm -rf ./ar_docker/opt  
   

5. Prepare the docker build files

   cd /kit/ar_docker
   cp ../areplicate-2024.5.0-357.x86_64.rpm .
   
   ./create-dockerfile.sh  
   

6. Change the line of file /kit/ar_docker/Dockerfile , from:

   RUN yum -y install /tmp/areplicate-*.rpm

   to

   RUN systemd=no yum -y install /tmp/areplicate-*.rpm

NOTE!
The parameter systemd=no is used to solve the below error you may hit during the docker build stage: This rpm is not supported on your system (no systemctl), exiting. error: %prein(areplicate-2024.5.0-357.x86_64) scriptlet failed, exit status 43

NOTE!
The password should not be empty and must be strong enough.

WARNING!
If you want to install ODBC Drivers, please make the corresponding ODBC Drivers rpm files are ready in this folder. If you want to skip the ODBC Drivers installation at present, rename or delete the file "drivers" in this folder.

7. Build the docker image

   docker build --no-cache -t johnw/replicate:2024.5 .

   where /johnw/replicate:2024.5 is the image tag.

Do not forget the last period "."

8. Startup and Run the docker image

   docker run -d --name ar --hostname cdc2 -e ReplicateRestPort=3552 -p 3552:3552 -v /dockermount/data/replicate/data:/replicate/data johnw/replicate:2024.5

Now Qlik Replicate is running in the docker and can be accessed from Qlik Replicate Console GUI.

Environment

• Qlik Replicate 2024.5  SP03 and above builds
• Qlik Replicate 2023.11 SP05 and above builds
• Linux 8.x and 9.x

After renaming a group used in the Identity Provider (IdP) set up with Qlik Cloud Analytics, the old group name continues to be listed in Qlik Cloud.

Users can log in without issues using the updated information.

Resolution

Use Qlik-CLI to remove the old group name.

Example command: 

qlik group rm <groupId>

See Delete group by ID for details.

Cause

Qlik Cloud retrieves all its information on groups from the IdP (Identity Provider), but does not delete old groups. Old groups can be removed using the API.

Renaming a group will be perceived by Qlik Cloud as a new group having been created. 

Environment

• Qlik Cloud Analytics

Can Qlik Cloud Analytics Community Sheets be unpublished using a Qlik Automate block or the Qlik REST API?

There is no unpublish sheet block in Qlik Automate, and a simple unpublish option cannot be done with the Qlik REST API.

To note:

• Duplciating a published sheet will create a private copy for the user who has unpublished it. It will only be visible to them.
• The sheet will need to be unpublished first, and ownership then needs to be transferred back to the original user. (Example: Set owner on an app object. The user must be the owner of the object)
• The published sheet behaviour in Qlik Sense is such that when published, it cannot be modified. You first need to unpublish the sheet before deleting.
• If the status or ownership of the sheet has not changed as expected: a new session will be created when the existing session is closed, either through inactivity or by the browser tab being explicitly closed (after around 120 seconds).

Environment

• Qlik Cloud Analytics

Starting from Qlik Replicate versions 2024.5 and 2024.11, Microsoft SQL Server 2012 and 2014 are no longer supported. Supported SQL Server versions include 2016, 2017, 2019, and 2022. For up-to-date information, see Support Source Endpoints for your respective version.

Attempting to connect to unsupported versions, both on-premise and cloud, can result in various errors.

Examples of reported Errors:

• Qlik Replicate 2024.5 accessing Microsoft Azure SQL Server 2014
  
  [SOURCE_CAPTURE  ]W:  Table 'dbo'.'tableName' has encrypted column(s), but the 'Capture data from Always Encrypted database' option is disabled. The table will be suspended  (sqlserver_endpoint_capture.c:157)
  
  
• Qlik Replicate 2024.11 accessing Microsoft SQL Server 2014
  
  [SOURCE_UNLOAD ]E: RetCode: SQL_ERROR SqlState: 42S02 NativeError: 208 Message: [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Invalid object name 'sys.column_encryption_keys'. Line: 1 Column: -1 [1022502] (ar_odbc_stmt.c:4067)

Cause

The system view sys.column_encryption_keys is only available starting from SQL Server 2016. Attempting to query this view on earlier versions results in errors.

Reference: sys.column_encryption_keys (Microsoft Docs)

Resolution

Upgrade your SQL Server instances to a supported version (2016 or later) to ensure compatibility with Qlik Replicate 2024.5 and above.

Internal Investigation ID(s)

00375940, 00376089

Environment

• Qlik Replicate versions 2024.5, 2024.11, and higher
• Microsoft SQL Server 2014, 2012, and lower (unsupported)

By default, Qlik Replicate translates an UPDATE operation on the source into an UPDATE on the target. However, in some scenarios, especially when a primary key column is updated, you may want to capture this change as a DELETE followed by an INSERT.

This behavior can be enabled in Qlik Replicate through a task setting called "DELETE and INSERT when updating a primary key column." For more details, refer to the Qlik Replicate User Guide: Miscellaneous tuning.

Explanation of the "DELETE and INSERT when updating a primary key column" Option

Consider the following Oracle source table example, where ID is a primary key and name is a non-primary key column:

• Non-PK columns update: update kit set name='test-upd' where id=44;
  
  This will be replicated as a standard UPDATE on the target.
  
  
• PK columns update: update kit set id=4 where id=44;
  
  With the above option enabled, this will be replicated as a DELETE followed by an INSERT.

Applicable Target Types

This behavior is supported for the following types of targets:

1. File targets with Store Changes mode enabled (Apply Changes mode is not supported):
   Includes targets such as local files, Amazon S3, Azure Data Lake Storage (ADLS), Google Cloud Storage (GCS), etc.
2. RDBMS targets with Store Changes mode enabled:
   Supported databases include Oracle, MySQL, SQL Server, IBM Db2, and others.
3. Streaming targets with Apply Changes mode enabled (Store Changes mode is not supported):
   Includes Apache Kafka, Amazon MSK, Amazon Kinesis Data Streams, Azure Event Hubs, Confluent Cloud, Google Cloud Pub/Sub, etc.

Important Notes

• When the "DELETE and INSERT when updating a primary key column" option is enabled, Qlik Replicate will automatically add all columns to Oracle supplemental logging to capture the complete row data.
• Even though the operation is internally transformed into a DELETE and an INSERT, the Qlik Replicate UI will still display it as an UPDATE under the Apply Changes view.

Internal Investigation ID(s)

00350953

Environment

• Qlik Replicate, all versions

When attempting to execute a Data Integration (DI) Job, encountered the following error messages:

Execution failed :Cannot invoke "java.util.jar.Manifest.getMainAttributes()" because "manifest" is null

The detailed log can be found from workspace\.metadata\.log:

!MESSAGE 2025-05-06 19:18:06,261 ERROR org.talend.commons.exception.CommonExceptionHandler  - Cannot invoke "java.util.jar.Manifest.getMainAttributes()" because "manifest" is null

!STACK 0
java.lang.NullPointerException: Cannot invoke "java.util.jar.Manifest.getMainAttributes()" because "manifest" is null
    at org.talend.designer.runprocess.java.JavaProcessor.compareSapjco3Version(JavaProcessor.java:1803)
    at org.talend.designer.runprocess.java.JavaProcessor.appendLibPath(JavaProcessor.java:1653)
    at org.talend.designer.runprocess.java.JavaProcessor.getNeededModulesJarStr(JavaProcessor.java:1599)
    at org.talend.designer.runprocess.java.JavaProcessor.getLibsClasspath(JavaProcessor.java:1343)
    at org.talend.designer.runprocess.java.JavaProcessor.getCommandLine(JavaProcessor.java:1243)
    at org.talend.designer.core.runprocess.Processor.getCommandLine(Processor.java:304)
    at org.talend.designer.core.runprocess.Processor.getCommandLine(Processor.java:294)

Cause

The error signifies that the JAR file utilized in Job lacks the necessary manifest meta-information, specifically, the MANIFEST.MF file is absent from the JAR.

Resolution

Navigate to the <Studio_installation_Home>\configuration\.m2 folder, locate the JAR file (specifically 'sapjco3.jar' in this instance), and unzip it to confirm the presence of the MANIFEST.MF file. If the MANIFEST.MF file is absent, it indicates an issue with the JAR file. Proceed to delete the directory containing this JAR file and reinstall the right JAR file within Talend Studio, for more further details, please refer to Installing external modules to Talend Studio.

Environment

• Talend Data Integration 

Uploading a file to a dataset using the Qlik Cloud Analytics Catalog only lists the Personal Space. No other Spaces are available.

This persists even if the user has all the correct Space permissions or owns the missing Shared Space.

Example:

1. Log in to Qlik Cloud Analytics
2. Switch to the Catalog
3. Click the Create new dropdown
4. Click Dataset
5. Click Upload data file
6. Only the Personal (B) space is available. Clicking the dropdown (A) shows No options 
   
   
   
   
   

Resolution

1. Remove the Personal/ Space from the list by clicking the X.
   
   
   
   
2. An error A space is required. Create a space. will be displayed. Ignore the error.
   
   
3. Click the drop-down arrow. All available spaces will be listed.
   

Environment

• Qlik Cloud Analytics

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

The following release notes cover the Qlik PostgreSQL installer (QPI) version 1.2.0 to 2.0.0.

Content

• What's New
• 2.0.0 May 2025 Release Notes
• Known Limitations (2.0.0)
• 1.4.0 December 2023 Release Notes
• Known Limitations (1.4.0)
• 1.3.0 May 2023Release Notes
• Known Limitations (1.3.0)
• 1.2.0 Release Notes

What's New

• The PostgreSQL version used by QPI has been updated to 14.17
• An upgrade of an already upgraded external instance is now possible
• Support for an upgrade of the embedded 14.8 database was added
• Silent installs and upgrades are supported beginning with Qlik PostgreSQL Installer 1.4.0 and later. QPI can now be used with silent commands to install or upgrade the PostgreSQL database. (SHEND-973)

2.0.0 May 2025 Release Notes

Known Limitations (2.0.0)

• Rollback is not supported.
• The database size is not checked against free disk space before a backup is taken.
• Windows Server 2012 R2 does not support PostgreSQL 14.8. QPI cannot be used on Windows Server 2012 R2.
• QPI will only upgrade a PostgreSQL instance that only contains Qlik Sense Databases (QSR, SenseServices, QSMQ, Licenses, QLogs, etc.)

1.4.0 December 2023 Release Notes

Known Limitations (1.4.0)

• QB-24990: Cannot upgrade PostgreSQL if Qlik Sense was installed in a custom directory such as D:\Sense. See Qlik PostgreSQL Installer (QPI): No supported existing Qlik Sense PostgreSQL database found.
• Rollback is not supported.
• Database size is not checked against free disk space before a backup is taken.
• QPI can only upgrade bundled PostgreSQL database listening on the default port 4432. Using QPI to upgrade a standalone database or a database previously unbundled with QPI is not supported.
• Cannot migrate a 14.8 embedded DB to standalone
• Windows Server 2012R2 does not support PostgreSQL 14.8. QPI cannot be used on Windows Server 2012R2.

1.3.0 May 2023 Release Notes