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.
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
1. Stop R.E
2. Update below cfg files
i.<RE>/etc/org.talend.remote.jobserver.server.cfg
Update value of below parameter to new location
org.talend.remote.jobserver.commons.config.JobServerConfiguration.ROOT_PATH= <new_location>/TalendJobServersFiles
ii. <RE>/etc/org.ops4j.pax.logging.cfg
Update value of below parameter to new location
log4j2.appender.flowexecution.routes.route1.rolling.fileName = <new_location>/TalendJobServersFiles/jobexecutions/logs/$\\{ctx:flowID\\}/$\\{ctx:flowExecutionId\\}.log
log4j2.appender.flowexecution.routes.route1.rolling.filePattern = <new_location>/TalendJobServersFiles/jobexecutions/logs/$\\{ctx:flowID\\}/$\\{ctx:flowExecutionId\\}.log.%i
3. Restart R.E after modifying any cfg files
After R.E restart, when new jobs are deployed from TMC you can see execution logs in new location
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.
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.
The steps below are for an example test setup of SAML authentication using auth0 as Identity Provider with Qlik Sense Enterprise on Windows.
This customization is provided as is. Qlik Support cannot provide continued support of the solution. For assistance, reach out to our Professional Services or engage in our active Integrations forum.
Note: These steps assume an auth0 "Developer" account has already been created
{
"groups": [
"Everyone"
]
}
function (user, context, callback) {
if((user.user_metadata || {} ).groups){
context.idToken['https://qlik.com/groups'] = user.user_metadata.groups;
}
callback(null, user, context);
}
function (user, context, callback) {
context.idToken['https://qlik.com/sub'] = user.email;
callback(null, user, context);
}
Description | SAML_auth0 | An appropriate description |
Prefix | auth0 | This will be the prefix used when accessing Qlik Sense via URL |
Session cookie header name | X-Qlik-Session-auth0 | Needs to differ for every Virtual Proxy |
Authentication method | SAML | The authentication enabled via auth0 |
SAML host URI | https:// | The Qlik Sense Server |
SAML entity ID | https://.auth0.com | This can be found in the metadata file downloaded from auth0 under entityID |
SAML IdP metadata | Choose File: This is the xml file downloaded from Auth0 | The IdP metadata file downloaded from auth0 |
SAML attribute for user ID | See Claim Types (learn.microsoft) | This is also found in the metadata file from auth0 |
SAML attribute for user directory | [Auth0] | Directory name |
SAML signing algorithm | SHA-1 | Used by auth0 |
A Qlik Account is required to access Qlik portals, software downloads and full access to Qlik.com site resources.
To connect your account to your corporation (accessing product downloads, etc.) the email address domain must match the corporate domain.
The email address cannot be changed after account creation.
A confirmation code has been sent to your email address. You will need the code in the final step.
From R2024-05, Java 17 will become the only supported version to start most Talend modules, enforcing the improved security of Java 17 and eliminating concerns about Java's end-of-support for older versions. In 2025, Java 17 will become the only supported version for all operations in Talend modules.
Starting from v2.13, Talend Remote Engine requires Java 17 to run. If some of your artifacts, such as Big Data Jobs, require other Java versions, see Specifying a Java version to run Jobs or Microservices.
Content
Qlik Talend Module | Patch Level and Version |
Studio | Supported from R2023-10 onwards |
Remote Engine | 2.13 or later |
Runtime | 8.0.1-R2023-10 or later |
For Windows users, please follow the JDK installation guide (docs.oracle.com).
For Linux users, please follow the JDK installation guide (docs.oracle.com).
For MAC OS users, please follow the JDK installation guide (docs.oracle.com).
When working with software that supports multiple versions of Java, it's important to be able to specify the exact Java version you want to use. This ensures compatibility and consistent behavior across your applications. Here is how you can specify a specific Java version on the following products (such as build servers, shared application server, and similar):
For Studio users who are using multiple JDKs, please follow the appropriate instructions listed above and follow the proceeding additional steps:
-vm
<JDK17 HOME>\bin\server\jvm.dll
For Remote Engine (RE) users who are using multiple JDKs, please follow the appropriate instructions listed above and follow the proceeding additional steps.
For Runtime users who are using multiple JDKs, please follow the appropriate instructions listed above and follow the proceeding additional steps.
If Runtime is not running as a service:
With the Enable Java 17 compatibility option activated, any Job built by Talend Studio cannot be executed with Java 8. For this reason, verify the Java environment on your Job execution servers before activating the option.
To use Talend Administration Center with Java 17, you need to open the <tac_installation_folder>/apache-tomcat/bin/setenv.sh file and add the following commands:
# export modules export JAVA_OPTS="$JAVA_OPTS --add-opens=java.base/sun.security.x509=ALL-UNNAMED --add-opens=java.base/sun.security.pkcs=ALL-UNNAMED"
Windows users use <tac_installation_folder>\apache-tomcat\bin\setenv.bat
Follow the steps below to configure the JobServer to use the new Java version.
Navigate to the JobServer Configuration:
Go to the <JobServerRootDir>\conf directory, where <JobServerRootDir> is the path to your Talend JobServer installation.
Open the Configuration File for Editing:
Locate the TalendJobServer.properties file and open it with a text editor of your choice.
Set the Java 17 Executable Path:
Find the line dedicated to the Job launcher path within the file. You will modify this line to point to the Java 17 executable.
org.talend.remote.jobserver.commons.config.JobServerConfiguration.JOB_LAUNCHER_PATH="C:\\Program Files\\Java\\jdk-17\\bin\\java.exe"
org.talend.remote.jobserver.commons.config.JobServerConfiguration.JOB_LAUNCHER_PATH=/usr/lib/jvm/java-17-openjdk/bin/java
Replace the example paths with the actual path where Java 17 is installed on your system. Ensure to point directly to the Java executable within the bin directory of your JDK installation.
Save Your Changes:
After editing, save the TalendJobServer.properties file.
Restart Talend JobServer:
For the changes to take effect, restart your Talend JobServer.
After completing these steps, Talend JobServer will utilize Java 17 for executing Jobs, ensuring compatibility with the latest Java version supported by Talend modules.
For Java 17 users, Talend CICD process requires the following Maven options:
set "MAVEN_OPTS=%MAVEN_OPTS% --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/sun.security.x509=ALL-UNNAMED --add-opens=java.base/sun.security.pkcs=ALL-UNNAMED"
For Java 17 users, Talend CICD process requires the following Maven options:
export MAVEN_OPTS="$MAVEN_OPTS \ --add-opens=java.base/java.net=ALL-UNNAMED \ --add-opens=java.base/sun.security.x509=ALL-UNNAMED \ --add-opens=java.base/sun.security.pkcs=ALL-UNNAMED"
<name>TALEND_CI_RUN_CONFIG</name> <description>Define the Maven parameters to be used by the product execution, such as: - Studio location - debug flags These parameters will be put to maven 'mavenOpts'. If Jenkins is using Java 17, add: --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/sun.security.x509=ALL-UNNAMED --add-opens=java.base/sun.security.pkcs=ALL-UNNAMED </description>
Overview
Enable your Remote Engine to run Jobs or Microservices using a specific Java version.
By default, a Remote Engine uses the Java version of its environment to execute Jobs or Microservices. With Remote Engine v2.13 and onwards, Java 17 is mandatory for engine startup. However, when it comes to running Jobs or Microservices, you can specify a different Java version. This feature allows you to use a newer engine version to run the artifacts designed with older Java versions, without the need to rebuild these artifacts, such as the Big Data Jobs, which reply on Java 8 only.
When developing new Jobs or Microservices that do not exclusively rely on Java 8, that is to say, they are not Big Data Jobs, consider building them with the add-opens option to ensure compatibility with Java 17. This option opens the necessary packages for Java 17 compatibility, making your Jobs or Microservices directly runnable on the newer Remote Engine version, without having to go through the procedure explained in this section for defining a specific Java version. For further information about how to use this add-opens option and its limitation, see Setting up Java in Talend Studio.
Procedure
c:\\Program\ Files\\Java\\jdk11.0.18_10\\bin\\java.exe
org.talend.remote.jobserver.commons.config.JobServerConfiguration.JOB_LAUNCHER_PATH=c:\\jdks\\jdk11.0.18_10\\bin\\java.exe
ms.custom.jre.path=C\:/Java/jdk/binMake this modification before deploying your Microservices to ensure that these changes are correctly taken into account.
For Java Option Command --add-opens, using SPACE or = depends on OS, JDK version or the place where you setup, there are 3 cases:
1. support both SPACE and =
2. support SPACE only
3. support = only
Example:
--add-opens=java.base/java.net=ALL-UNNAMED
--add-opens java.base/java.net=ALL-UNNAMED
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.
This is a Python example to call the Qlik Sense Engine API.
Here is a simple script using the websocket-client module to call the Engine API. Note that the Qlik Sense virtual proxy is set to header authentication.
import websocket import ssl import json header_user = {'header_user': 'user1'} ws = websocket.create_connection("wss://qlikserver1.domain.local/hdr/app/", sslopt={"cert_reqs": ssl.CERT_NONE},header=header_user) ws.send(json.dumps({ "handle": -1, "method": "GetDocList", "params": [], "outKey": -1, "id": 1 })) result = ws.recv() while result: result=ws.recv() y = json.loads(result) print(y) ws.close()
Example of results:
{'jsonrpc': '2.0', 'method': 'OnConnected', 'params': {'qSessionState': 'SESSION_CREATED'}} {'jsonrpc': '2.0', 'id': 1, 'result': {'qDocList': [{'qDocName': 'test1', 'qConnectedUsers': 0, 'qFileTime': 0, 'qFileSize': 176418, 'qDocId': '9b428869-0fba-4ba5-9f94-901ae2fdf041', 'qMeta': {'createdDate': '2018-11-29T09:28:40.588Z', 'modifiedDate': '2018-12-17T15:13:56.860Z', 'published': True, 'publishTime': '2018-12-17T15:13:56.782Z', 'privileges': ['read', 'offlineaccess'], 'description': '', 'dynamicColor': '', 'create': None, 'stream': {'id': 'aaec8d41-5201-43ab-809f-3063750dfafd', 'name': 'Everyone'}, 'canCreateDataConnections': False}, 'qLastReloadTime': '2018-11-29T09:30:42.121Z', 'qTitle': 'test1', 'qThumbnail': {}}]}}
In certain scenarios, it is necessary to create additional Windows local accounts for Qlik Replicate and Qlik Enterprise Manager to provide a user the minimum required access level.
This article outlines the steps to add a Windows local account in the built-in Guests group.
#00048742
Gold Client BW is a versatile solution designed to streamline day to day business activities. Gold Client BW helps reduce the need of full system refreshes, provides the ability to copy queries and hierarchies to non-Production systems, and aids in troubleshooting production support issues. The Gold Client BW tool will save time, reduce manual effort, and allows users focus on what matters most.
Usage examples of Gold Client BW are listed below: