Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Search our knowledge base, curated by global Support, for answers ranging from account questions to troubleshooting error messages.
Qlik offers a wide range of channels to assist you in troubleshooting, answering frequently asked questions, and getting in touch with our technical 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:
We're happy to help! Here's a breakdown of resources for each type of need.
Support | Professional Services (*) | |
Reactively fixes technical issues as well as answers narrowly defined specific questions. Handles administrative issues to keep the product up-to-date and functioning. | Proactively accelerates projects, reduces risk, and achieves optimal configurations. Delivers expert help for training, planning, implementation, and performance improvement. | |
|
|
(*) reach out to your Account Manager or Customer Success Manager
Your first line of support: https://community.qlik.com/
Looking for content? Type your question into our global search bar:
Leverage the enhanced and continuously updated Knowledge Base to find solutions to your questions and best practice guides. Bookmark this page for quick access!
Subscribe to maximize your Qlik experience!
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)
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)
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.
Technical Adoption Workshops
Our in depth, hands-on workshops allow new Qlik Cloud Admins to build alongside Qlik Experts.
Qlik Fix
Qlik Fix is a series of short video with helpful solutions for Qlik customers and partners.
Suggest an idea, and influence the next generation of Qlik features!
Search & Submit Ideas
Ideation Guidelines
Get the full value of the community.
Register a Qlik ID:
Incidents are supported through our Chat, by clicking Chat Now 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:
Log in to manage and track your active cases in the Case Portal. (click)
Please note: to create a new case, it is easiest to do so via our chat (see above). Our chat will log your case through a series of guided intake questions.
When creating a case, you will be prompted to enter problem type and issue level. Definitions shared below:
Select Account Related for issues with your account, licenses, downloads, or payment.
Select Product Related for technical issues with Qlik products and platforms.
If your issue is account related, you will be asked to select a Priority level:
Select Medium/Low if the system is accessible, but there are some functional limitations that are not critical in the daily operation.
Select High if there are significant impacts on normal work or performance.
Select Urgent if there are major impacts on business-critical work or performance.
If your issue is product related, you will be asked to select a Severity level:
Severity 1: Qlik production software is down or not available, but not because of scheduled maintenance and/or upgrades.
Severity 2: Major functionality is not working in accordance with the technical specifications in documentation or significant performance degradation is experienced so that critical business operations cannot be performed.
Severity 3: Any error that is not Severity 1 Error or Severity 2 Issue. For more information, visit our Qlik Support Policy.
If you require a support case escalation, you have two options:
When other Support Channels are down for maintenance, please contact us via phone for high severity production-down concerns.
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.
After a Qlik NPrinting upgrade, some cells are blocked out with black color.
Example:
This is a known Vizlib extension defect. Verify that a Vizlip extension is in use and contact Vizlib support for further support.
Uncheck Keep Source Formatting in the template editor.
QB-22744
The Fast Change button may stop working after a QlikView upgrade. The button appears not to respond after being clicked.
By default, 'straight table' cannot be used as a fast change option if the table is a linked object. To confirm if a 'straight table' is in use:
Set RestrictLinkedTypeChanges at the below path:
Set the value as either RestrictLinkedTypeChanges=-1 or RestrictLinkedTypeChanges=<greater than the number of linked objects> (Stop the QVS service before making this changes) The other options is to unlink the objects (right click on the chart, and click 'linked objects>unlink this object)
The settings.ini may have been adjusted to allow this. These changes were reset to default after an upgrade. The settings.ini must be backed up and reviewed after an upgrade to ensure all custom settings remain intact.
Jira QV-25359
This article describes how to import Qlik Sense apps by using an automation. There are 2 possible approaches:
The difference between this approach and the Copy App block in the Qlik Cloud Services connector is that you can specify whether or not to include the data that's in the app. This can be done by setting the "No Data" parameter.
Example automation:
Blocks:
Export app
This approach allows you to import an app from a file. First, use the Export App To Base 64 Encoded File block in combination with the Cloud Storage connector to create the file on any of the supported destinations. In the below example, Dropbox is used.
Import app
To import the file again, use the Open File & Read Data From File blocks from the Cloud Storage connector and use the output from the read block as input for the Import App From Base 64 Encoded File block from the Qlik Cloud Services connector.
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.
Due to an issue with MySQL ODBC Driver 8.0.027 to 8.0.033, empty TEXT columns may not be replicated correctly during Full Load.
Qlik Replicate
MySQL ODBC Driver 8.0.027 to 8.0.033
Empty TEXT columns may not be replicated correctly during Full Load. For example, if one table row contains a TEXT column with a value and the same column in the next row contains an empty value (but not NULL), both rows will display the value of the first row on the target. See Limitations and considerations | Qlik Replicate Help.
When the source table has a text column that is blank (not null) the data from the previous row that had data is duplicated.
As an example if have the following 3 rows:
1 'SOME DATA'
2 null
3 '' <---empty string not null
The the output rows will have the following:
1 'SOME DATA'
2 null
3 'SOME DATA'
To resolve the issue, downgrade to MySQL ODBC 8.0.026.
The ODBC parameter no_ssps can also be used to resolve the issue.
Set it to no_ssps=1;
Until MySQL resolved the issue, the parameter should be set on Full Load ODBC connections. See 5.2 Connector/ODBC Connection Parameters | dev.mysql.com.
Applying a transformation on a column and clicking Save does not save the changes. The transformation cannot be applied.
Resolution
This is fixed in the Qlik Replicate 2024.5 SP1 kit and later releases of Qlik Replicate.
Qlik Replicate 2024.5 SP01
Public share: https://files.qlik.com/url/qr2024050247sp01 (expires 9/30/2024)
Qlik Enterprise Manager 2024.5 SP01
Public share: https://files.qlik.com/url/qem2024050249sp01 (expires 9/30/2024)
QB-27669
While accessing the DB2z 13.1 as the source database, the IBM DB2 for z/OS source endpoint reports a warning message during the task startup.
The warning message in task log file:
[ASSERTION ]W: Replicate has not been certified to work with DB2 z/OS version '13.01.0000', and therefore any issues you may encounter with this version are not covered by your license agreement (db2z_ifi_api.c:880)
Upgrade Qlik Replicate to 2023.5 SP02, or higher versions such as 2023.11/2024.5.
Qlik Replicate is certified to support DB2 z/OS version 13 from Qlik Replicate 2023.5 SP02.
#00175112, #00173433
By default, Talend Remote Engine creates job execution logs in a directory below:
TalendRemoteEngineInstallationDirectory\TalendJobServersFiles\jobexecutions\logs
Is there any way we can change the default location of these logs?
This article aims at How to change default location of execution Logs for Remote Engine (R.E)
To change the location of Talend Jobserver files, Please follow below steps
After R.E restart, when new jobs are deployed from TMC you can see execution logs in new location
In a Windows multi-node deployment, the App Distribution Service (ADS) distributes apps from Qlik Sense Enterprise on Windows to Qlik Sense Enterprise SaaS. The service is installed on every node. However, Qlik Sense does not have load balancing for ADS, meaning if not all nodes have access to the apps, distribution may fail. See App Distribution from Qlik Sense Enterprise to Qlik Cloud fails when distributed from RIM NODE.
If you wish to disable app distribution from certain nodes:
[appdistributionservice]
Disabled=true
Identity=Qlik.app-distribution-service
DisplayName=App Distribution Service
ExePath=dotnet\dotnet.exe
UseScript=false
[hybriddeploymentservice]
Disabled=true
Identity=Qlik.hybrid-deployment-service
DisplayName=Hybrid Deployment Service
ExePath=dotnet\dotnet.exe
UseScript=false
A QlikView Server administrator can follow these steps to remove an application from a QlikView Server/Publisher environment. In this example, we will remove the Test 1.qvf application.
This helps preempt orphaned documents and folders to be displayed in the QlikView Management Console, as documented in How To Remove Orphaned QlikView Apps and What does Orphans folder in Source Documents mean?
Highlight Test 1.qvf, listing all associated tasks
Qlik Replicate is set to apply prefix replacement to archived redo logs only and specifies file-level access to archive location, yet continues to use the online redo logs and may fail a task as per the following error:
The settings are done correctly, with only Replicate has file-level access to the new archive location checked:
000014626, 00164729
An escalation is a request from a customer concerning a specific case that is currently under
investigation by Qlik Support. The customer has a case that has business-critical impact without a workaround provided and requires a faster resolution than what is provided in the standard resolution process.
The Escalation Management process aims to bring order, structure, focused management attention and additional resources to those customer situations which could otherwise result in a high level of customer dissatisfaction. Any Qlik® customer or partner with a valid maintenance contract may initiate an escalation on an existing support case. Escalations are intended for existing cases. Please do not report new issues through Escalation Management. New issues should be raised through the Qlik Support portal.
Escalations can occur for several reasons. Having a defined process allows Qlik to identify, track, monitor and manage situations that require increased awareness and quick action.
Please note that for an issue to be escalated, a support case must first be created (we will not accept escalations solely based on communications via email). If a case has been worked through our standard support processes and with our teams and you are not satisfied with the level or timeliness of service you received, you can escalate accordingly. See Escalation Triggers for more information.
Americas |
Qlik Data Analytics ProductsGiuseppe Novello Akshesh Patel Qlik Data IntegrationJayashree Guin Robert Kittles Christian Tan Lori Wittal Evan Teitelbaum TalendChristian Tan |
EMEA |
Qlik Data Analytics ProductsAlbert Candelario Benoit Canal Patrick Vanotti Qlik Data IntegrationAnne Arnoult Fabio Cunha TalendAnne Arnoult |
APAC |
Qlik Data Analytics ProductsKiran Shankar Ayaka Hanazono Yasser Ahmed Kahn Sankar Reddy K Qlik Data IntegrationJohn Wang Ravi Chintam Robin Patel Shaona Zhang TalendRobin Patel
|
Global Customer Support |
Qlik Customer Support / Talend Customer CareSuresh Kumar |
Americas | Hien Le hien.le@qlik.com |
EMEA | Réginald de Visscher reginald.devisscher@qlik.com |
APAC |
Vineet Chopra |
Global | Daniel Coullet daniel.coullet@qlik.com |
The direct export of QVD files stored on a Tenant is not currently supported.
In order to export a QVD from a Tenant it is necessary to use an external storage solution. This is achieved using one of the available Qlik Web Storage Provider Connectors.
This needs to be included in the Data Load script:
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 Unified Hub functionality allows for links to QlikView documents (hosted via AccessPoint) to be published in Qlik Sense Hub.
This article covers the steps on how to deploy it in a QlikView and Qlik Sense Enterprise on Windows environment.
For publishing QlikView documents to Qlik Sense SaaS editions via the Multi-Cloud solution, see How to configure QlikView Multi-Cloud deployment and App distribution
Qlik Sense Enterprise on Windows, all versions
QlikView, 12.0 and newer
Note: The steps below illustrates and further details the main configuration steps mentioned in the video above.
In order for the server running QlikView Distribution Service (Publisher or QDS) to connect to the Qlik Sense machine, three settings need to be changed on the Qlik Sense server:
Note: This setting may have only been needed on earlier versions of the Unified Hub deployments and may not be needed in newer versions of Qlik Sense and QlikView.
Starting with all Qlik Sense services in a stopped state, complete these steps:
5. Save the file
6. Start Qlik Sense services
The next step will be to configure the appropriate security rule in order to allow users to view the documents which will be published.
The next step will be to export a set of certificates from Qlik Sense for use by the Publisher machine for use in establishing trust for the distribution.
4. Navigate to the client.pfx file and import it
5. Repeat the import steps for the server.pfx file
6. Now select the Trusted Root Certification Authorities section and import the root.cer certificate
7. Once all the certificates are installed, go back to the QlikClient certificate in the Personal section and double click on it. This will open the properties of the certificate.
8. Now go to the Details tab and scroll to the thumbprint. Copy this value to a notepad window
At this point the distribution should complete successfully and now you should validate that things appear as expected on the Qlik Sense side. Assuming that you’ve distributed the document to at least the user account that you are using then you should see the document appear in the QlikView documents section of the Hub which should have magically appeared:
If you are encountering further issues, then contact Qlik Support for a deeper level of troubleshooting.
The information and script in this article are provided as is. For further customization and assistance, engage with our active QlikView or Qlik Sense app-building boards.
If you have a group of fields that are related, or if fields carry information that can be broken up into smaller parts that are relevant when creating dimensions or measures, you can create field definitions that can be used to generate derived fields. One example is a date field, from which you can derive several attributes, such as year, month, week number, or day name. All these attributes can be calculated in a dimension expression using Qlik Sense date functions, but an alternative is to create a calendar definition that is common for all fields of date type. Field definitions are stored in the data load script.
Note in case that you need to change the format / to customize the date you need to do it from the script, and most probably drill down to all levels, depending of course the object and what you want to accomplish.
Here is such an example of an autocalendar that can be used in any case:
[autoCalendar]:
DECLARE FIELD DEFINITION Tagged ('$date')
FIELDS
Dual(Year($1), YearStart($1)) AS [Year] Tagged ('$axis', '$year'),
Dual('Q'&Num(Ceil(Num(Month($1))/3)),Num(Ceil(NUM(Month($1))/3),00)) AS [Quarter] Tagged ('$quarter', '$cyclic'),
Dual(Year($1)&'-Q'&Num(Ceil(Num(Month($1))/3)),QuarterStart($1)) AS [YearQuarter] Tagged ('$yearquarter', '$qualified'),
Dual('Q'&Num(Ceil(Num(Month($1))/3)),QuarterStart($1)) AS [_YearQuarter] Tagged ('$yearquarter', '$hidden', '$simplified'),
Month($1) AS [Month] Tagged ('$month', '$cyclic'),
Dual(Year($1)&'-'&Month($1), monthstart($1)) AS [YearMonth] Tagged ('$axis', '$yearmonth', '$qualified'),
Dual(Month($1), monthstart($1)) AS [_YearMonth] Tagged ('$axis', '$yearmonth', '$simplified', '$hidden'),
Dual('W'&Num(Week($1),00), Num(Week($1),00)) AS [Week] Tagged ('$weeknumber', '$cyclic'),
Date(Floor($1)) AS [Date] Tagged ('$axis', '$date', '$qualified'),
Date(Floor($1), 'D') AS [_Date] Tagged ('$axis', '$date', '$hidden', '$simplified'),
If (DayNumberOfYear($1) <= DayNumberOfYear(Today()), 1, 0) AS [InYTD] ,
Year(Today())-Year($1) AS [YearsAgo] ,
If (DayNumberOfQuarter($1) <= DayNumberOfQuarter(Today()),1,0) AS [InQTD] ,
4*Year(Today())+Ceil(Month(Today())/3)-4*Year($1)-Ceil(Month($1)/3) AS [QuartersAgo] ,
Ceil(Month(Today())/3)-Ceil(Month($1)/3) AS [QuarterRelNo] ,
If(Day($1)<=Day(Today()),1,0) AS [InMTD] ,
12*Year(Today())+Month(Today())-12*Year($1)-Month($1) AS [MonthsAgo] ,
Month(Today())-Month($1) AS [MonthRelNo] ,
If(WeekDay($1)<=WeekDay(Today()),1,0) AS [InWTD] ,
(WeekStart(Today())-WeekStart($1))/7 AS [WeeksAgo] ,
Week(Today())-Week($1) AS [WeekRelNo] ;
DERIVE FIELDS FROM FIELDS [Date] USING [autoCalendar] ;
A variable definition (which is created in qvw document under Setting -> Variable Overview -> Add) disappears after distribution. This behavior is working as designed. During reload and distribution the document is opened without data - for optimization reasons. During that time variables defined in the document are not available.
Conditions:
Create and define a variable in the script, not in the document.
e.g.
SET Variable1=today();
Uncheck [+] checkbox in the Variable Overview.
Product Defect ID: QV-25116
A Qlik Replicate task fails and stops with the error:
[INFRASTRUCTURE ]E: Json doesn't start with '{' [1003001] (at_cjson.c:1790)
Resuming the task may lead to this error message as the last saved file was improperly saved.
Restart the task from a timestamp instead of resuming the task to regenerate the file:
If the target system uses files, such as ADLS or Databricks), a network disconnect occurring while a file is being pushed to the target can lead to an incomplete file being saved on the Qlik Replicate server. When the file is saved improperly, the task will not be able to use it to resume the task.
Regeneration of the last file will be needed.