Qlik AutoML is a tool within Qlik Cloud where you can quickly train and deploy models, and the make predictions against said models. In this article, we address best practices for preparing training datasets for ML experiments and/or apply datasets for generating predictions.

Guidelines

1. For column names, use camelCase or column names without spaces or punctuation.
2. No special characters in column names.
3. When working with Excel data, remove all formatting such as bold/italics, borders, currency, or color formats.
4. Make sure data types are consistent between training and prediction datasets. It may be worth checking in Qlik Catalog to see if datasets are profiling the data type you are expecting.
5. Qlik AutoML only works with structured, tabular data. Any flat file which can be uploaded and profiled in Qlik Cloud can be used by AutoML. Based on experience, we have best results with CSV, QVD, XLSX formats.
6. AutoML does not support sentiment analysis. This would require a third-party service (such as Amazon Comprehend) to generate structured data points for AutoML to use.  You can use Comprehend in Qlik Sense directly using our connector and then use that output as a feature in AutoML.
7. For multi-table files such as Excel, only the first sheet will be used for a table.
8. Date columns are currently treated as categorical feature type. Feature engineering of date columns to numeric type should be done prior to using the dataset in an ML experiment.
9. Be aware of dataset size limits based on your tenant type.
10. For null data, if a column contains more than 50% null values it will be dropped.
    
    If greater than 50%:
    For numeric type: it uses the mean.
    For categorical type: uses value 'other'

We will continue to update this list as we encounter other issues related to data used in Qlik AutoML.

Environment

Qlik AutoML 

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.

Related Content

How To Get Started with Qlik AutoML

If you require further details on an error code or if you encounter error codes we do not have listed, please contact support. We will investigate further.

Related Content

Authentication and Authorization

Authentication and authorization with the Microsoft Excel Connector in Qlik Application Automation works through oAuth2. When a user attempts to connect a Microsoft Excel datasource, the user will be redirected to the Microsoft login page where a user is prompted to give permission for Qlik Application Automation to access their Office 365 tenant.

The following scopes are being requested by Qlik Application Automation:

• Offline_access
• User.Read
• Files.ReadWrite.All

Working with excel worksheets

The Microsoft Excel connector has blocks available to perform actions on worksheets, data inside worksheets and tables inside worksheets. When working with data, we always recommend to work with tables rather than data on the worksheet due to ease of use.

Listing rows from Excel File

This block obtains values from an excel file worksheet from a specified range. The following input parameters are used:

• Drive ID: This is a lookup that will query a user's drive.
•  Item ID: ID of an item. Using the lookup a user can query a specific folder to search for excel sheets
• Worksheet name: Can be selected using lookup or alternatively the worksheet name or ID can be manually provided.
• Start Cell: The upper left bound cell of the range to return.
• End Cell: The lower right bound cell of the range to return.

The block returns a double nested array. The first level contains a row, the second level contains the value of a column in that row.

The same block also exists for working with tables. Here the start cell and end cell are replaced by a Table ID.

Create a new worksheet

With the block Add Worksheet to Excel File a user can add a new worksheet to an Excel document. It takes the following input parameters:

• Item ID: ID of an item. Using the lookup a user can query a specific folder to search for excel sheets
• Name: Name for the new worksheet name.

Updating Rows in a Worksheet

Using the block Update Rows in Excel Sheet you can specify a range in which you want to overwrite existing data. The following input parameters are required:

• Drive ID: This is a lookup that will query a user's drive. A sharepoint drive ID can also be provided.
• Item ID: ID of an item. Using the lookup a user can query a specific folder to search for excel sheets
• Worksheet name: Can be selected using lookup or alternatively the worksheet name or ID can be manually provided.
• Start Cell: The upper left bound cell of the range to return.
• End Cell: The lower right bound cell of the range to return.
• Values: A double nested array containing data for each cell in the specified range. This has to match the range specified by the Start Cell and End Cell inputs. It is strongly recommended to work with variables and construct a listOfRows variable. This variable should be a list and it should be filled with multiple lists. An example could look like the following:

Create a new table

Using the block Create Excel Table With Headers a user can create a table in Excel. Using the block Add Table to Excel File Worksheet a user can also create a table without headers. The following input parameters are being requested:

• Drive ID: This is a lookup that will query a user's drive.  A sharepoint drive ID can also be provided.
• Item ID: ID of an item. Using the lookup a user can query a specific folder to search for excel sheets
• Worksheet: When item is selected, a lookup can be used to search for the different sheets in which the table has to be placed. You can also provide the name or ID of the worksheet.
• Start Row: The row where the headers will be placed. Indexes in Excel start from 1.
• Start Column: Use alphabetic letter.
• End column: Use alphabetic letter.
• Headers: Array of strings to use as header values. Keep in mind that the number of columns selected using the start column and end column have to match with the headers array. E.g. C-E as column start/end for an array of 3 headers.
• Name: Name of the table for easy references.

Aside from creating a table, we can also delete is by the use of the Delete Table from Excel File Worksheet block. This requires an item ID, worksheet and Table ID.

Find Row(s) in Excel Worksheet Table

Two blocks serve to find a matching row in an Excel Table. These blocks are Find Row in Excel Worksheet Table and Find Rows in Excel Worksheet Table. The first one will only return the first row found, the second one will return all rows found matching these criteria. The following input parameters are required:

• Drive ID: This is a lookup that will query a user's drive.
• Item ID: ID of an item. Using the lookup a user can query a specific folder to search for excel sheets
• Worksheet: When item is selected, a lookup can be used to search for the different sheets in which the table has to be placed. You can also provide the name or ID of the worksheet.
• Table ID: Can be obtained using the lookup once all above fields have been filled out.
• Column Index For Search: The index of the column that is being searched for a value. The indexes are zero based.
• Search Value: The value to search for. Only fully matching values will work.

Sharing workbooks

Functionality to share workbooks is not included in the Microsoft Excel connector. These actions can be done using the Microsoft Onedrive or Sharepoint connector.

Limitations

• Cannot create a new excel file.

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.

Loading data from Oracle may fail on a full load with the error:

ORA-01555: snapshot too old: rollback segment number string with name "string" too small

Resolution

This is an Oracle configuration issue which must be resolved for the task to be able to continue.

In Automatic Undo Management mode, increase the setting of UNDO_RETENTION. Otherwise, use larger rollback segments.

You can verify your current settings:

SHO PARAMETER UNDO;
SELECT SUM(BYTES)/1024/1024 "MB", TABLESPACE_NAME FROM DBA_FREE_SPACE GROUP BY TABLESPACE_NAME

Verify how large the problematic table is and what the current settings are. Then increase the sizes as per your findings. 

Oracle references: 

http://www.dba-oracle.com/t_ora_01555_snapshot_old.htm
https://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:275215756923
http://www.dba-oracle.com/oracle_tips_rollback_segments.htm

Cause

It caused by rollback records needed by a reader being overwritten by other writers.

Environment:

Qlik Replicate 

 
The message may be shown despite of the user having been allocated a license.

In Qlik Sense June 2019 and later, an additional version of the error message was introduced, indicating when a user has reached their maximum allowed concurrent sessions:
 

* See You cannot access Qlik Sense because you have no access pass - intermittent problem.

Environment:

Qlik Sense Enterprise on Windows 

Resolution:

Does the user have a license?

Verify if the user has a license assigned. 

For Signed License Keys this could be a:

• Professional License (Managing professional access)
• Analyzer License (Managing analyzer access )
• Capacity License (Analyzer capacity license and comparison with other license allocations and how to check usage)
  Verify if there are still Capacity minutes remaining. 

For licenses still using Tokens, this could be a:

• User Access Token (Allocating user access)
• Login Access Pass (Creating login access rules)
  Verify if there are still Login Access Passes available. 

Solution:

Assign a License or ensure you have sufficient Capacity minutes 

If the user has just been assigned a license prior to logging in the first time:

This often occurs when a user is being assigned a license or token based on an active directory group, and has not yet been synchronized. The license check for user-based licenses (professional and analyzer) and tokens occurs when you access the hub.

If you access the hub without a license and subsequently are assigned a token or professional or analyzer access, the license check has already occurred, and you will get a "no access pass" error, stopping you from interacting with apps. Log out and log in again for the license to be recognized.
 
Solution:

1. Logout with the user from both the hub and Qlik Sense Management Console (if applicable).
2. Log back in.

If the Qlik Sense server is licensed with a signed license and the licensing server has not been reachable for too long:

If a signed license key cannot be verified with the license backend for 5 days, licenses will be disabled. 

The below log entities can be found from Licenses Log
{"caller":"handler.go:61","level":"info","message":"invalid license error, license verification error: lic is stale","res.errorType":"licenses.InvalidLicenseError","res.statusCode":403,"timestamp":xxxxxx"}

Or:

{"caller":"sync.go:290","corrId":"26ab589a897f6e56:26ab589a897f6e56:0:1","level":"info","licenseNumber":"XXXXXXXX","message":"re-syncing assignments with the backend","timestamp":"2020-01-20T08:13:32.7038396Z"}
{"caller":"handler.go:44","corrId":"35b5cbb055734329:35b5cbb055734329:0:1","errorMessage":"Too much time has passed since the last license update","errorType":"LICENSES-OutdatedLicense","level":"info","statusCode":403,"timestamp":"2020-01-20T08:13:32.7438444Z"}


Verify that the Qlik Sense server has an active internet connection and that connectivity to license.qlikcloud.com on port 443 is possible from the server running the Qlik Sense licensing service. 

See Using a Qlik signed license in an offline environment for details. 

Solution:

• Reconnect the Qlik Sense server to the internet and allow for the licensing service to check in with license.qlikcloud.com.
• Restart Dispatcher service 
• In some rare cases, the Management-Server only has temporary access to the Internet, so sometimes it is able to connect to https://license.qlikcloud.com and sometimes not. It needs to have permanent access to the licence-URL, to be able to correctly work.
• If you are in the above rare cases or if the sync doesn't seems to be performed, there is a way to force the sync: go to the QMC site license (qmc/sitelicense), remove one character and click to "apply".

  The license will be refused as it's an incorrect one. This action will force the license synchronization.

A license conversion was planned and the date has passed

During the conversion, the client has to prepare and switch the users from tokens to professional/analyzer licenses. 

After this conversion date, a periodic cleanup of tokens in the backend license server will occur. If this clean up happens and an admin has not finished the conversion, all tokens will be removed from the users. The result will be the 'no access pass' message.

Solution:

Allocate new professional analyzer licenses according to the conversion plan. 

For additional troubleshooting steps, see:

• Qlik Sense April 2018 and later- Service account getting "You cannot access Qlik Sense because you have no access pass"
• You cannot access Qlik Sense because you have no access pass - intermittent problem
• Unable to open Qlik Sense app after changing Internet Proxy or Firewall settings  

A log stream from SQL was being loaded into Microsoft Azure Databricks Delta Target, but the process failed.  The error occurred during a full load of a table:

00007080: 2023-02-20T19:32:08 [TARGET_LOAD ]E: Failed (retcode -1) to execute statement: 'COPY INTO `raw_iso_les`.`text_translation` FROM(SELECT cast(_c0 as INT) as `TextID`, cast(_c1 as INT) as `LanguageID`, _c2 as `Micro`, _c3 as `Short`, _c4 as `Medium`, _c5 as `Extended`, _c6 as `Text`, _c7 as `MicroAudioURL`, _c8 as `ShortAudioURL`, _c9 as `MediumAudioURL`, _c10 as `LongAudioURL`, _c11 as `TextAudioURL`, _c12 as `SmallIconURL`, _c13 as `MediumIconURL`, _c14 as `LargeIconURL`, cast(_c15 as INT) as `OrgChecksum`, cast(_c16 as INT) as `CustChecksum`, cast(_c17 as INT) as `ReferenceID`, cast(_c18 as TIMESTAMP) as `LastUpdateOn`, _c19 as `LastUpdatedBy`, cast(_c20 as TIMESTAMP) as `CreatedOn`, _c21 as `CreatedBy`, cast(_c22 as BOOLEAN) as `Active`, cast(_c23 as TIMESTAMP) as `LastDeleteOn`, _c24 as `LastDeletedBy`, cast(_c25 as TIMESTAMP) as `LastReactivateOn`, _c26 as `LastReactivatedBy`, cast(_c27 as INT) as `ArchiveID`, cast(_c28 as TIMESTAMP) as `LastArchiveOn`, _c29 as `LastArchivedBy`, cast(_c30 as TIMESTAMP) as `LastRestoreOn`, _c31 as `LastRestoredBy`, cast(_c32 as INT) as `RowVersionStamp` from 'abfss://XXXX') FILEFORMAT = CSV FILES = ('/X/X/X/X/12/X.csv.gz') FORMAT_OPTIONS('nullValue' = 'attrep_null', 'multiLine'='true') COPY_OPTIONS('force' = 'true')' [1022502] (ar_odbc_stmt.c:4906)
00007080: 2023-02-20T19:32:08 [TARGET_LOAD ]E: RetCode: SQL_ERROR SqlState: HY000 NativeError: 35 Message: [Simba][Hardy] (35) Error from server: error code: '0' error message: 'org.apache.hive.service.cli.HiveSQLException: Error running query: org.apache.spark.SparkException: Job aborted due to stage failure: Task 0 in stage 3805190.0 failed 4 times, most recent failure: Lost task 0.3 in stage 3805190.0 (TID 32173534) (10.139.64.145 executor 2621): com.univocity.parsers.common.TextParsingException: java.lang.ArrayIndexOutOfBoundsException - 20480
Identified line separator characters in the parsed content. This may be the cause of the error. The line separator in your parser settings is set to '[lf]'. Parsed content: ... [1022502] (ar_odbc_stmt.c:4913)
00007080: 2023-02-20T19:32:08 [TARGET_LOAD ]E: Failed to copy data of file x\x.csv to database [1022502] (cloud_imp.c:6497)

Resolution

To resolve the issue, the user updated Qlik Replicate to the November 2022 version and reloaded the table. This will resolve the current issue and prevent the table from failing again in the future. 

Environment

Qlik Replicate 
Microsoft Azure Databricks Delta Target

To connect to Snowflake using ODBC with keypair authentication, you can use the following connection string format:

Driver={SnowflakeDSIIDriver};Server=<account_name>.<region_name>.snowflakecomputing.com;User=<username>;PrivateKey=<path_to_private_key>;Db=<database_name>;Schema=<schema_name>

Each part of the connection string represents:

• Driver: The ODBC driver name for Snowflake.
• Server: The name of your Snowflake account with the region where your account is located (e.g. us-west-2).
• User: Your Snowflake username.
• PrivateKey: The path to the private key file on your local machine.
• Db: The name of the Snowflake database you want to connect to.
• Schema: The name of the Snowflake schema you want to use.

Note that you may also need to include additional connection parameters, such as Warehouse, Role, and SSL. Here's an example connection string that includes these parameters:

Driver={SnowflakeDSIIDriver};Server=<account_name>.<region_name>.snowflakecomputing.com;User=<username>;PrivateKey=<path_to_private_key>;Db=<database_name>;Schema=<schema_name>;Warehouse=<warehouse_name>;Role=<role_name>;SSL=on

Replace the placeholders in the connection string with the appropriate values for your Snowflake account and keypair authentication setup.

Environment

Qlik Replicate 
Snowflake Target

Qlik offers a range of opportunities to assist you in troubleshooting, answering frequently asked questions, and contacting our experts. In this article, we guide you through all available avenues to secure your best possible experience.

For details on our terms and conditions, review the Qlik Support Policy.

Index:

• Support and Professional Services; who to contact when.
• Qlik Support: How to access the support you need
• 1. Qlik Community, Forums & Knowledge Base
• The Knowledge Base
• Blogs
• Our Support programs:
• The Qlik Forums
• Ideation
• How to create a Qlik ID
• 2. Chat
• To create a case using chat:
• 3. Qlik Support Case Portal
• Escalate a Support Case
• Resources

Support and Professional Services; who to contact when.

We're happy to help! Here's a breakdown of resources for each type of need.

(*) reach out to your Account Manager or Customer Success Manager

Qlik Support: How to access the support you need

1. Qlik Community, Forums & Knowledge Base

Your first line of support: https://community.qlik.com/

​Looking for content? Type your question into our global search bar:

The Knowledge Base

Leverage the enhanced and continuously updated Knowledge Base to find solutions to your questions and best practice guides. Bookmark this page for quick access!

1. Go to the Official Support Articles Knowledge base
2. Type your question into our Search Engine
   
   
   
   
3. Need more filters?
   1. Filter by Product
   2. Or switch tabs to browse content in the global community, on our Help Site, or even on our Youtube channel
      
      

Blogs

Subscribe to maximize your Qlik experience!

The Qlik Design Blog
The Design blog is all about product and Qlik solutions, such as scripting, data modelling, visual design, extensions, best practices, and more! (click)

The Product Innovation Blog
By reading the Product Innovation blog, you will learn about what's new across all of the products in our growing Qlik product portfolio. (click)

The Support Updates Blog
The Support Updates blog delivers important and useful Qlik Support information about end-of-product support, new service releases, and general support topics. (click)

Our Support programs:

Q&A with Qlik
Live sessions with Qlik Experts in which we focus on your questions).

Techspert Talks
Techspert Talks is a free webinar to facilitate knowledge sharing held on a monthly basis.

Qlik Fix
Qlik Fix is a series of short video with helpful solutions for Qlik customers and partners.

The Qlik Forums

• Quick, convenient, 24/7 availability
• Monitored by Qlik Experts
• New releases publicly announced within Qlik Community forums (click)
• Local language groups available (click)

Ideation

Suggest an idea, and influence the next generation of Qlik features!

Search & Submit Ideas
Ideation Guidelines

How to create a Qlik ID

Get the full value of the community.

Register a Qlik ID:

1. Go to: qlikid.qlik.com/register
2. You must enter your company name exactly as it appears on your license or there will be significant delays in getting access.
3. You will receive a system-generated email with an activation link for your new account. NOTE, this link will expire after 24 hours.
   
   If you need additional details, see: Additional guidance on registering for a Qlik account
   If you encounter problems with your Qlik ID, contact us through Live Chat!

2. Chat

Incidents are supported through our Chat, by clicking Contact Support on any Support Page across Qlik Community.

To raise a new issue, all you need to do is chat with us. With this, we can:

• Answer common questions instantly through our chatbot
• Have a live agent troubleshoot in real time
• With items that will take further investigating, we will create a case on your behalf with step-by-step intake questions

To create a case using chat:

1. Log in to the community with your business account prior to requesting a case to be logged
2. Open chat
3. Type Create a case 
4. When prompted, choose A Support Issue or Question 
5. Choose how you would classify your question:
   • Account, Access, or License related
   • Data Analytics product related
   • Data Integration product related
   • or Qlik Cloud product related
6. Choose if you would prefer to speak to a Live Agent or Create a Case
7. Enter your business email associated with your Qlik Support Portal
8. Choose the Qlik Product your query is about
9. Follow any additional prompts
10. Choose your Severity (General Inquiry/Assistance or Major functionality issue)
11. Summarize and describe the issue in as much detail as possible.
12. The case will be created and you will receive an email confirming the case number. You can immediately review and modify the case in our Case Management Portal.

How to create a case using chat

3. Qlik Support Case Portal

Log in to manage and track your active cases in Manage Cases. (click)

​Your advantages:​

• ​Self-service access to all incidents so that you can track progress​
• Option to upload documentation and troubleshooting files
• Option to include additional stakeholders and watchers to view active cases​
• Follow-up conversations ​​

Escalate a Support Case

If you require a support case escalation, you have two options:

1. Request to escalate within the case, mentioning the business reasons.
   
   To escalate a support incident successfully, mention your intention to escalate in the open support case. This will begin the escalation process.
   
   
2. Contact your Regional Support Manager
   
   If more attention is required, contact your regional support manager. You can find a full list of regional support managers in the How to escalate a support case article.

Resources

A collection of useful links.

Qlik Cloud Status Page
Keep up to date with Qlik Cloud's status.

Support Policy
Review our Service Level Agreements and License Agreements.

Live Chat and Case Portal
Your one stop to contact us.

Due a product defect, users deleted in mid-March 2023 might still keep a license assigned to them.

Environment

• Qlik Cloud 

Resolution

The issue was solved on March 21st, and deleting users correctly deallocates licenses.

Qlik is working on finding a solution for removing licenses still allocated to users that were deleted during this period for both Qlik Sense Enterprise and Qlik Sense Business subscriptions.
To speed up things, customers on Qlik Sense Enterprise can import and run the attached automation.

March 14th 2023: You may have upgraded Qlik Sense and located a warning banner in your Management Console stating that this version of PostgreSQL is not supported. If you are running a standalone PostgreSQL database later than 9.6, this message can be disregarded. We are working on resolving the underlying cause. 

In this article, we walk you through the requirements and process of how to upgrade an existing Qlik Sense Repository Database from PostgreSQL 9.6 to PostgreSQL 12.5 (see supported scenarios) or install a brand new Repository based on PostgreSQL 12.5.

We will use the Qlik PostgreSQL Installer (QPI).

For a manual method, see: How to manually upgrade the bundled Qlik Sense PostgreSQL version to 12.5 version 

PostgreSQL 9.6 has reached End of Life Reference: PostgreSQL Versioning Policy.

Index

• Supported Scenarios
• Considerations
• Installing anew Qlik Sense Repository Database using PostgreSQL 12.5
• Qlik PostgreSQL Installer - Download Link
• Upgrading anexisting QRD to PostgreSQL 12.5
• The Upgrade:
• Finalizing the Upgrade/Uninstalling the old Database Service:
• Compatibility with PostgreSQL installers
• Troubleshooting
• Related Content

Supported Scenarios

• Upgrades: Before using the Qlik PostgreSQL Installer, upgrade to a supported version of Qlik Sense Enterprise on Windows. Then use the Qlik PostgreSQL Installer to upgrade PostgreSQL.
  
  We tested and validated Qlik Sense Enterprise on Windows from February 2022 to February 2023. Note that November 2022 and later do not support 9.6, and a warning will be displayed during the Sense upgrade.
  
  
• New installs: The Qlik PostgreSQL Installer supports installing a new Qlik Sense Repository Database cluster on a new server, setting up a new environment or migrating an existing Database to a separate host.

Considerations

• This installer will not detect a standalone PostgreSQL database installed by any other means, other than through an official Qlik installer package, installed on the standard folders in the C drive. 
• The installer itself does not provide a rollback feature. This is described below. 
• The user who runs the installer has sufficient permissions to execute it and install services 
• The user who runs the installer has sufficient permissions to create folders and files in the backup destination 
• The backup destination has sufficient free disk space to dump the existing database  
• The backup destination is not a network path or virtual storage folder. It is recommended the backup is stored on the main drive 
• There will be downtime during this operation, please plan accordingly 

Installing a new Qlik Sense Repository Database using PostgreSQL 12.5

1. Run the Qlik PostgreSQL Installer as an administrator 
   
   
2. Click on Install 
   
   
3. Accept the Qlik Customer Agreement 
   
   
4. Set your Local database settings and click Next. You will use these details to connect other nodes to the same cluster. 
   
   
5. Set your Database superuser password and click Next
   
   
6. Set the database installation folder, standard: C:\Program Files\PostgreSQL\12
   
   
7. Set the database data folder, standard: C:\Program Files\PostgreSQL\12\data
   
   
8. Review your settings and click Install, then click Finish
   
   
9. Start installing Qlik Sense Enterprise Client Managed. Choose Join Cluster option.
   
   The Qlik PostgreSQL Installer has already seeded the databases for you and has created the users and permissions. No further configuration is needed.
   
   
10. The tool will display information on the actions being performed. Once installation is finished, you can close the installer.  
    
    If you are migrating your existing databases to a new host, please remember to reconfigure your nodes to connect to the correct host. How to configure Qlik Sense to use a dedicated PostgreSQL database 
    

Qlik PostgreSQL Installer - Download Link

Download the installer here.

Qlik PostgreSQL installer version 1.2.1 Release Notes

Upgrading an existing QRD to PostgreSQL 12.5

Before using the Qlik PostgreSQL Installer, upgrade to a supported version of Qlik Sense Enterprise on Windows. Then use the Qlik PostgreSQL Installer to upgrade PostgreSQL.

We tested and validated Qlik Sense Enterprise on Windows from February 2022 to February 2023. Note that November 2022 and later do not support 9.6, and a warning will be displayed during the Sense upgrade.

Qlik Sense Enterprise on Windows installations other than in C:\Program Files\Qlik\Sense are currently not supported. 

The Upgrade:

1. Stop all services on rim nodes 
   
   
2. On your Central Node, stop all services except the Qlik Sense Repository Database 
   
   
   
   
3. Run the Qlik PostgreSQL Installer. An existing Database will be detected. 
   
   
   
   
4. Highlight the database and click Upgrade 
   
5. Read and confirm the (a) Installer Instructions as well as the Qlik Customer Agreement, then click (b) Next.
   
   
   
   
6. Provide your existing Database superuser password and click Next.
   
   
7. Define your Database backup path and click Next.
   
   
   
   
8. Define your Install Location (default is prefilled) and click Next.
   
   
   
   
9. Define your database data path (default is prefilled) and click Next.
   
   
    
10. Review all properties and click Upgrade.
    
    
    
    
11. The upgrade is completed. Click Close.
    
    
     
12. Open the Windows Services Console and locate the Qlik Sense Enterprise on Windows services.
    
    You will find that the Qlik Sense Repository Database service has been set to manual. Do not change the startup method. 
    
    
    
    You will also find a new postgresql-x64-12 service. Do not rename this service. 
    
    
    
    
13. Start all services except the Qlik Sense Repository Database service. 
    
    
14. Start all services on your rim nodes.
    
    
15. Validate that all services and nodes are operating as expected.

If the upgrade was unsuccessful and you are missing data in the Qlik Management Console or elsewhere, contact Qlik Support.  

Finalizing the Upgrade/Uninstalling the old Database Service:

No further steps are needed unless you plan to upgrade Qlik Sense Enterprise on Windows to the next major release. If you plan to upgrade to, for example, November 2022, the old Qlik Sense Repository Database service must be removed from the server.

Perform the following steps to delete the Qlik Sense Repository Database Service:

1. Open a command prompt and run the command:
   cd "C:\ProgramData\Package Cache"
2. From there, run:
   c:\ProgramData\Package Cache\dir /s PostgreSQL.msi
3. The folder containing PostgreSQL.msi will be revealed.
4. Right-click on the PostgreSQL.msi file and select uninstall from the menu.

Compatibility with PostgreSQL installers

This version of the upgrade tool is fully compatible with the official PostgreSQL installers from https://www.enterprisedb.com/downloads/postgres-postgresql-downloads.

If you need to upgrade to a higher release than Qlik provides, you can install the same minor PostgreSQL release 12.x.

Troubleshooting

1. If the installation crashes, the server reboots unexpectedly during this process, or there is a power outage, the new database may not be in a serviceable state. Installation/upgrade logs are available in the location of your temporary files, for example:
   
   C:\Users\Username\AppData\Local\Temp\2
   
   A backup of the original database contents is available in your chosen location, or by default in:
   
   C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\backup\9.6
   
   The original database data folder has been renamed to:
   
   C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\9.6_deprecated
   
   
2. Upgrading Qlik Sense after upgrading PostgreSQL with the QPI tool fails with:
   
   This version of Qlik Sense requires a 'SenseServices' database for multi cloud capabilities. Ensure that you have created a 'SenseService' database in your cluster before upgrading. For more information see Installing and configuring PostgreSQL.
   
   See Qlik Sense Upgrade fails with: This version of Qlik Sense requires a _ database for _.
   
   To resolve this, start the postgresql-x64-12 service.

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. The video in this article was recorded in a earlier version of QPI, some screens might differ a little bit.

Related Content

Qlik PostgreSQL installer version 1.2.1 Release Notes  
Techspert Talks - Upgrading Qlik Sense Repository Service
Backup and Restore Qlik Sense Enterprise documentation
Migrating Like a Boss
Optimizing Performance for Qlik Sense Enterprise
Qlik Sense Enterprise on Windows: How To Upgrade Standalone PostgreSQL
How-to reset forgotten PostgreSQL password in Qlik Sense
How to configure Qlik Sense to use a dedicated PostgreSQL database
Troubleshooting Qlik Sense Upgrades

Qlik Sense offers a range of Monitoring Applications that come pre-installed with the product.  This article aims to provide information on where to find information about them or where to download them.

Table of Contents:

• Entitlement Analyzer for Qlik Cloud
• App Analyzer for Qlik Cloud
• Reload Analyzer for Qlik Cloud
• Access Evaluator for Qlik Cloud
• OEM Dashboard for Qlik Cloud
• Qlik Application Automation Monitoring App
• Monitoring Apps for Qlik Sense Enterprise on Windows
• The Monitoring & Administration Topic Group

Environment

• Qlik Sense Enterprise on Windows 
• Qlik Cloud 
• Qlik Sense Enterprise on Windows 

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.

Entitlement Analyzer for Qlik Cloud

How can I track the usage of my Tenant over time? How are my entitled users using the Tenant? 
How can I better understand the usage of Analyzer Capacity vs. Analyzer & Professional Entitlements? 

These are a couple of the questions we frequently hear. To enable you to find better answers for those, we are happy to share with you the new Entitlement Analyzer for Qlik Sense Enterprise SaaS! 

For more information and to download the app and usage instructions, see The Entitlement Analyzer for Qlik Sense Enterprise SaaS customers is available NOW! 

App Analyzer for Qlik Cloud

These are a couple of the questions that you can answer with the App Analyzer.

For more information and to download the app and usage instructions, see The App Analyzer for Qlik SaaS customers is available NOW! 

Reload Analyzer for Qlik Cloud

“How can I monitor reloads across the tenant?”
“How can I see what data connections and files are being used?” 
“How can I view reload concurrency and peak reload RAM over time?” 

These are a few of the questions we frequently hear. To enable you to find better answers for those, we are happy to share with you the new Reload Analyzer for Qlik SaaS! 

For more information and to download the app and usage instructions, see The Reload Analyzer for Qlik SaaS customers is available NOW! 

Access Evaluator for Qlik Cloud

“What users and groups have access to space <X>?”

“What users and groups have access to app <X>?”

“How does a user have access to app <X>; via direct assignment, group, or app share?”

“Are there redundancies in policies? E.g., does a user have the same access to a space via a direct assignment as well as a group?”

“Who has what roles across the tenant?”

These are a few of the questions we frequently hear. To enable you to find better answers for those, we are happy to share with you the new Access Evaluator for Qlik SaaS! 

For more information and to download the app and usage instructions, see New Monitoring App for Qlik Cloud: Access Evaluator

OEM Dashboard for Qlik Cloud

The OEM Dashboard is an application for Qlik Cloud designed for OEM partners to centrally monitor data across their customers’ tenants. It provides a single pane to review numerous dimensions and measures, compare trends, and quickly spot issues across many different areas—which would otherwise be a tedious process. This application includes data from the App Analyzer, Entitlement Analyzer, and the Reload Analyzer, all of which are other monitoring applications for Qlik Cloud that provide deep levels of detail on their respective areas. Together, a complete picture can be formed which is crucial to the successful management of an OEM environment.

For more information and to download the app and usage instructions, see OEM Dashboard - Qlik Cloud Application.

Qlik Application Automation Monitoring App

This monitoring app presents various information on the Qlik Application Automation usage in the current tenant.

For more information and to download the app and usage instructions, see How to: automation monitoring app for tenant admins with Qlik Application Automation 

Monitoring Apps for Qlik Sense Enterprise on Windows

Operations Monitor and License Monitor

The Operations Monitor loads service logs to populate charts covering performance history of hardware utilization, active users, app sessions, results of reload tasks, and errors and warnings. It also tracks changes made in the QMC that affect the Operations Monitor.

The License Monitor loads service logs to populate charts and tables covering token allocation, usage of login and user passes, and errors and warnings.

For a more detailed description of the sheets and visualizations in both apps, visit the story About the License Monitor or About the Operations Monitor that is available from the app overview page, under Stories.

Basic information can be found here:

The License Monitor 
The Operations Monitor 

Both apps come pre-installed with Qlik Sense. 

If a direct download is required: Sense License Monitor | Sense Operations Monitor. Note that Support can only be provided for Apps pre-installed with your latest version of Qlik Sense Enterprise on Windows. 

App Metadata Analyzer

The App Metadata Analyzer app provides a dashboard to analyze Qlik Sense application metadata across your Qlik Sense Enterprise deployment. It gives you a holistic view of all your Qlik Sense apps, including granular level detail of an app's data model and its resource utilization.

Basic information can be found here: 

App Metadata Analyzer (help.qlik.com)

For more details and best practices, see: 

App Metadata Analyzer (Admin Playbook)

The app comes pre-installed with Qlik Sense.

The Monitoring & Administration Topic Group

Looking to discuss the Monitoring Applications? Here we share key versions of the Sense Monitor Apps and the latest QV Governance Dashboard as well as discuss best practices, post video tutorials, and ask questions.

Monitoring & Administration 

Other Apps

System Performance Analyzer 
Sessions Monitor, Reloads-Monitor, Log-Monitor 
Connectors Log Analyzer 

Qlik Replicate tasks error out, and tables are suspended.

RetCode: SQL_ERROR  SqlState: 22007 NativeError: 100035 Message: Timestamp '0000-00-00 00:00:00.000000' is not recognized Failed (retcode -1) to execute statement: 'INSERT  INTO "XXXXX_CTRL"."public_refer__ct"

Environment:

Qlik Replicate 
Snowflake Endpoint

Resolution:

'0000-00-00 00:00:00' is not a valid timestamp in Snowflake. A transformation will need to be added to change this to your desired value.

Here is an example, in this case we are replacing the timestamp to '1970-01-01 00:00:00':

coalesce(
CASE WHEN substr($AR_M_SOURCE_COLUMN_DATA,1,4) = '0000'
THEN '1970-01-01 00:00:00'
WHEN substr($AR_M_SOURCE_COLUMN_DATA,1,4) = ''
THEN '1970-01-01 00:00:00'
ELSE
$AR_M_SOURCE_COLUMN_DATA
END
,$AR_M_SOURCE_COLUMN_DATA)

Update operations to the Nvarchar(max) data types will cause the values to become 'NULL' values when the target is Microsoft Azure SQL Database.

Environment

Qlik Replicate 2021.11.0.165
Microsoft Azure SQL Database

Resolution

The behavior was resolved in Replicate 2022.11.0.475

Upgrade to Qlik Replicate sp03-2022.11.0.475 or later.

Internal Investigation ID(s) 

Case 00072614

Working with an Amazon RDS for Oracle endpoint as a source, we might encounter an issue where CDC doesn't start and fails with the following error:

Cannot create Oracle directory name 'ATTUREP_XXXXXX_XXX' with path '/XXXXX/log/arch'

Resolution

This is because of undocumented access request required which is not available in the User Guide yet. We have to execute the following grant statements to provide read only access to Qlik user to the online and archive redo logs:

grant read on directory ONLINELOG_DIR to qlik; 

grant read on directory ARCHIVELOG_DIR to qlik;

or

exec rdsadmin.rdsadmin_util.grant_sys_object('ONLINELOG_DIR','QLIK','READ');
exec rdsadmin.rdsadmin_util.grant_sys_object('ARCHIVELOG_DIR','QLIK','READ');

Where qlik/QLIK is the user specified in the source endpoint connection.

Environment

Qlik Replicate 

The Apply Exceptions table is a Qlik Replicate Control Table created on the target endpoint when the corresponding table is selected in the Control Tables tab.

You may notice that you cannot turn off the Apply Exceptions in the Qlik Replicate control table settings. The option to do so is greyed out and cannot be unchecked.  See img 01.

img 1

Change Processing errors are recorded in the attrep_apply_exceptions table. The data in this table is never deleted. For more information on the Apply Exceptions table please review attrep_apply_exceptions.

Additional tables and data take up space and resources in the database, so some people prefer to opt out of having this table for a Replicate task. This can be done with some additional configuration.

Disabling the Apply Exceptions table

1. Stop the Replicate task and then export a JSON of the task with the Export Task option under the Designer tab
   
   
   
   
2. Open the JSON exported and add the following line of information to the common_settings object and save it.
   
   "exception_table_enabled": false,
   
   You may find that your task JSON contains the following line of information. In this case, the word true can be changed to false without needing to add the information a second time.
   
   "exception_table_enabled": true,
   
   Before change:
   

   "common_settings":	{
   						"support_lobs":	false,
   						"change_table_settings":	{
   							"handle_ddl":	false,
   							"header_columns_settings":	{
   							}
   						},
   						"full_load_enabled":	false,
   						"audit_table_settings":	{
   						},
   						"dr_settings":	{
   						},
   						"statistics_table_settings":	{
   						},
   						"bidi_table_settings":	{
   						},
   						"task_uuid":	"c24fe2e3-9d04-334c-80c4-35f4b349f9e4",
   						"status_table_settings":	{
   						},
   						"status_table_enabled":	true,
   						"suspended_tables_table_settings":	{
   						},
   						"suspended_tables_table_enabled":	true,
   						"history_table_settings":	{
   						},
   						"history_table_enabled":	true,
   						"exception_table_settings":	{
   						},
   						"recovery_table_settings":	{
   						},
   						"data_batching_settings":	{
   						},
   						"data_batching_table_settings":	{
   						},
   						"log_stream_settings_depricated":	{
   						},
   						"ddl_history_table_settings":	{
   						},
   						"customized_charset_settings":	{
   							"validation":	{
   								"sub_char":	0
   							}
   						}
   					}
   				},

   
   After change:
   

   "common_settings":	{
                           "exception_table_enabled": false,
   						"support_lobs":	false,
   						"change_table_settings":	{
   							"handle_ddl":	false,
   							"header_columns_settings":	{
   							}
   						},
   						"full_load_enabled":	false,
   						"audit_table_settings":	{
   						},
   						"dr_settings":	{
   						},
   						"statistics_table_settings":	{
   						},
   						"bidi_table_settings":	{
   						},
   						"task_uuid":	"c24fe2e3-9d04-334c-80c4-35f4b349f9e4",
   						"status_table_settings":	{
   						},
   						"status_table_enabled":	true,
   						"suspended_tables_table_settings":	{
   						},
   						"suspended_tables_table_enabled":	true,
   						"history_table_settings":	{
   						},
   						"history_table_enabled":	true,
   						"exception_table_settings":	{
   						},
   						"recovery_table_settings":	{
   						},
   						"data_batching_settings":	{
   						},
   						"data_batching_table_settings":	{
   						},
   						"log_stream_settings_depricated":	{
   						},
   						"ddl_history_table_settings":	{
   						},
   						"customized_charset_settings":	{
   							"validation":	{
   								"sub_char":	0
   							}
   						}
   					}
   				},

   
   Notes: Each object within the common_settings is separated by a comma. The last object does not end with a comma. In this scenario, the extra line of information to be added is added as the first object. The order of the objects does not matter so this line of information can be placed in any order as long as the objects are separated by commas in the correct syntax format. Spacing does need to be kept in its original format.
   
   
3. Import the task JSON that was saved and resume the task. If the attrep_apply_exceptions table was already created previously, you may drop the table. The new settings in the task import will prevent the task from creating an attrep_apply_exceptions table. This is not reflected in the UI, but will continue to be reflected in the task JSON with the line of information stating  "exception_table_enabled": false, 
   

Environment

• Qlik Replicate 

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.

Getting data out of Qlik Sense Enterprise SaaS, and distributing it to different users in formatted Excel, has been a manual task until now.

Thanks to the release of Qlik Application Automation, it is now possible to automate this workflow by leveraging the connectors for Office 365 - specifically Microsoft SharePoint and Microsoft Excel. 

Here I share two example Qlik Application Automation workspaces that you can use and modify to suit your requirements. 

Video:

Considerations

• This example is built on distributing a SharePoint link. It is also possible to use attachments with the Mail block (see Reporting).
• Qlik Application Automation has a limit of 100,000 rows when getting data out of a Qlik Sense straight table object.
• The On-Demand example uses an extension in QSE SaaS to send data to the Automation. An update to the Qlik Sense Button object is expected soon, which will provide a native way to pass selections to an Automation.

Example 1: Scheduled Reports

1. Download the 'Scheduled Report.json' file attached to this document.
2. Create a new Automation in QSE SaaS, give it a name, and then upload the workspace you just downloaded by right clicking in the editor canvas, and selecting 'Upload workspace'.
3. Select the 'Create Binary File (Personal One Drive)' block, select 'Connection' in the block configurator to the right, and then create your connection to Microsoft SharePoint.
4. Select the 'Get Straight Table Data' block. Under 'Inputs' in the block configurator, lookup your the App Id, Sheet Id, and Object Id for the relevant QSE SaaS table you wish to output.
5. Select the 'Create Excel Table With Headers' block, select 'Connection' in the block configurator, and then create your connection to Microsoft Excel.
6. Select the 'Send Mail' block. Under 'Inputs' in the block configurator update the 'To' to reflect the addresses you wish to deliver to.
7. With the 'Send Mail' block still selected, select 'Connection' in the block configurator and add your Sender details.
8. To test, Save and then Run the Automation
9. If you receive any warnings or errors, navigate to the relevant blocks and ensure your Connection is selected in the block configurator. 
10. Select the 'Start' block. Under 'Inputs' in the block configurator, change Run Mode to Scheduled and define your required schedule. 

Example 2: On-Demand Reports

Note - These instructions assume you have already created connections as required in Example 1.

1. Download the 'On-Demand Report v3.json' file attached to this document.
2. Download and install the 'qlik-blends' extension. See: 
   https://github.com/rileymd88/qlik-blends/files/6378232/qlik-blends.zip
3. Create a new Automation in QSE SaaS, give it a name, and then upload the workspace you just downloaded by right-clicking in the editor canvas, and selecting 'Upload workspace'.
4. Ensure your Connections are selected in the block configurator for each of the following blocks, 'Create Binary File (Personal One Drive)', 'Create Excel Table With Headers', 'Add Rows To Excel Worksheet Table (Batch)', 'Create Sharing Link', and 'Send Mail'.  Save the Automation.
5. Select the 'Start' block and ensure Run Mode is set to Triggered. Make note of the of URL and Execution Token shown in the POST example. 
6. Open your chosen QSE SaaS application, and Edit the Sheet where you wish to add a Button to trigger an On-Demand report. 
7. Under 'Custom Objects' look for 'qlik-blends' from the Extensions menu and drag this into your Sheet.
8. Under the 'Blend' properties to the right, add-in your POST webhook URL and Token as noted in Step 5.
9. We will now add three measures to the 'qlik-blends' object. It is important you add them in the order described.  Add the first measure, using the following function in the expression editor: GetCurrentSelections()
10. Add the second measure, using the following function DocumentName()
11. The final measure will be the Object ID of the table you wish to use. To find the Object ID, select 'Done Editing'.  Then right click on the table, select 'Share', select 'Embed', then look for the Object ID under the preview. Copy this value, go back into Editing mode and paste this as your third measure value. 
12. With the 'qlik-blends' object selected, under Form select 'Add items'. For 'Item type' select Text. Under default value you can choose to add a default email address. For 'Label' and 'Reference'  type 'Email'. It is critical that Reference is updated to 'Email'.  Turn 'Required input' on. 
13. You can change the Appearance properties to suit your preferences, such as updating the Button label and message, enabling Dialog, and changing the Color under Theme.
14. Back in the Automation, under the Start Block. Set  'Run asynchronously' = yes to allow multiple requests to run at the same time (This will also increase the max run time from 1min to 60min)
15. Once happy, test the On-Demand report by entering an email and clicking the button.

This On-Demand Report Automation can be used across multiple apps and tables.  Simply copy the extension object between apps & sheets, and update the Object ID (Measure 3) for each instance. 

Environment

• Qlik Application Automation 
• Qlik Cloud 
• Microsoft Office 365

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.

The Qlik Replicate server service in Windows used to be named Attunity Replicate Server. 

This name has changed to Qlik Replicate Server. The change was introduced in the 2022.11 release.

If you are running a Windows Cluster and are monitoring Qlik Replicate through it, or if you have deployed third-party applications monitoring the service uptime, these applications must be modified to look for the correct service name. 

Environment

2021.11 and later

All on-premise Qlik Products can be downloaded from Qlik's Product Download Site.

To access the Download Site, you need an active QlikID. You will be able to see all products your account is eligible for.

If you encounter issues with the download site, start a chat with us and we will be able to help you right away.

You can access the Download Page directly here, or navigate to it from the Community Home page:

1. Open the Qlik Community
2. Click on Support
3. Under  Product News
4. Select  Product Downloads 
   
   If you do not see Product Downloads, please log in to the community.
   
   
   

This shows the download page with the Latest release and patch preselected.

1. Choose a different filter in Release Assets if you are looking for older product versions. By default, only the Latest release and patch will be displayed. 
   
   
   
   
2. From here:
   
   
   1. choose your Category (Qlik Data Analytics, Qlik Data Integration, Search All),
   2. your Product,
   3. your Release,
   4. and Release Number.
   5. Then click the Download Link
      
      
      
      
      

Alternatively, instead of selecting your product directly, you can also search all available columns:

1. Click the Magnifying Glass
2. Begin typing your search
3. Select the result
4. Confirm the result
   
   

Click here for video transcript