Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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.
When replicating to Oracle target, in some cases you may get ORA-12899 error.
This error may happen in a situation where your Oracle target has NLS_LENGTH_SEMANTICS set to ‘byte’ and the column being replicated from the source endpoint to the Oracle target endpoint includes at Unicode character/s that is presented by more than one byte. In this case, for example, when you replicate a varchar (10), it will be created as varchar (10 byte). Therefore, if the replicated data in the source endpoint includes a Unicode character that in UTF8 is presented by more than one byte, it could be that although the source is only 10 characters, on target endpoint (where replicate works in utf8), it would require more than 10 bytes for presenting its value. This will result with ORA-12899 error.
In general, when working with Oracle, the NLS_LENGTH_SEMANTICS setting determines how the CHAR and VARCHAR2 columns will be created. i.e., it enables you to create CHAR and VARCHAR2 columns using either byte or character length semantics.
Note:
With February 2018 of Qlik Sense, it is possible to capture granular usage metrics from the Qlik in-memory engine based on configurable thresholds. This provides the ability to capture CPU and RAM utilization of individual chart objects, CPU and RAM utilization of reload tasks, and more.
Also see Telemetry logging for Qlik Sense Administrators in Qlik's Help site.
Click here for Video Transcript
In the Qlik Sense Management Console, navigate to Engines > choose an engine > Logging > QIX Performance log level. Choose a value:
[Settings 7]
ErrorPeakMemory=2147483648
WarningPeakMemory=1073741824
ErrorProcessTimeMs=60000
WarningProcessTimeMs=30000
Note that it is possible to track only process time or peak memory. It is not required to track both metrics. However, if you set ErrorPeakMemory, you must set WarningPeakMemory. If you set ErrorProcessTimeMs, you must set WarningProcessTimeMs.
Note: Currently telemetry is only written to log files. It does not yet leverage the centralized logging to database capabilities.
Note: for more info on the common fields found in the logs please see help.qlik.com.
The Method column details each engine operation and are too numerous to completely detail. The most relevent methods to investigate are as follows and will be the most common methods that show up in the logs if a Warning or Error log entry is written.
Method | Description |
Global::OpenApp | Opening an application |
Doc::DoReload, Doc::DoReloadEx | Reloading an application |
Doc::DoSave | Saving an application |
GenericObject::GetLayout | Calculating a hypercube (i.e., chart object) |
Once the logs mentioned above are created, the Telemetry Dashboard for Qlik Sense can be downloaded and installed to read the log files and analyze the information.
The Telemetry Dashboard provides the ability to capture CPU and RAM utilization of individual chart objects, CPU and RAM utilization of reload tasks, and more.
For additional information including installation and demo videos see Telemetry Dashboard - Admin Playbook
The dashboard installer can be downloaded at: https://github.com/eapowertools/qs-telemetry-dashboard/wiki. NOTE: The dashboard itself is not supported by Qlik Support directly, see the Frequently Asked Questions about the dashboard, to report issues with the dashboard, do so on the "issues" webpage.
1. Right-click installer file and use "Run as Administrator". The files will be installed at C:\Program Files\Qlik\Sense
2. Once installed, you will see 2 new tasks, 2 data connections and 1 new app in the QMC.
3. In QMC Change the ownership of the application to yourself, or the user you want to open the app with.
4. Click on the 'Tasks' section in the QMC, click once on 'TelemetryDashboard-1-Generate-Metadata', then click 'Start' at the bottom. This task will run, and automatically reload the app upon completion.
5. Use the application from the hub to browse the information by sheets
Sometimes we need to store column's before-image data in the target table. This is useful if we want to store both of the before-image and after-image of the columns values in the target table for downstream apps usage.
Under Apply Changes mode (Store changes mode is turn off), in the table setting by adding a new column in transformation (name it as "prevenient_salary" in this sample), the variable expression is like $BI__<columnName> where $BI__ is a mandatory prefix (which instructs Replicate to capture the before-image data) and <columnName> is the original table column. For example if the original table column name is SALARY then $BI__SALARY is the column before-image data:
If the column SALARY value is updated from 22 to 33 in source side, then before the UPDATE the target table row looks like:
after the UPDATE is applied to target table the row looks like:
In this sample the before-image value is 22, the after-image value is 33.
before-image data can be used in filer also, see sample here .
Scenario:
! Note that the code is provided as is and will need to be modified to suit specific needs. For assistance, please contact the original creators of Qlik-Cli.
Connect-Qlik -computername "QlikSenseServer.company.com" # This will export the custom security rules and output them as secrules.json Get-QlikRule -filter "type eq 'Custom' and category eq 'security'" -full -raw | ConvertTo-Json | Out-File secrules.json # This will import secrules.json into a Sense site # The ideal use case would be to move the developedsecurity rules from one environment to another, so connecting to another Sense site would likely be needed here Get-Content -raw .\secrules.json |% {$_ -replace '.*"id":.*','' } | ConvertFrom-Json | Import-QlikObject
Qlik Sense Enterprise on Windows , all versions
Where can I find the installed version or service release of my Qlik Sense Enterprise on a Windows server?
You can locate the Qlik Sense Enterprise on Windows version in three locations:
Qlik Cloud Analytics does not list versions as the cloud version is always identical and current across the platform.
With the release of shared automations in Qlik Automate, it is now possible to run an automation in a Shared Space for users other than the owner. The automation will run using the owner’s Qlik account and any third-party connections as they were configured by the owner.
When an automation is run by another user, it is possible to retrieve this user’s information during the automation run. This article outlines how this is done.
This is only supported when the automation is run from the console or API. It is not supported for triggered automations when they are run from the trigger URL or webhook automations when they are run from the webhook event. The reason for this is that in these cases, no user subject is sent to the automation (triggered executions use the execution token instead of a user token, and webhook automations have no user involved when they are run by the webhook event).
However, if triggered or webhook automations are run manually or over API, it will be possible to retrieve the user's info.
When an automation is run by any user, it is possible to retrieve the user id and user info for the user who executed the automation during the automation run.
Unable to use data profiling to achieve Pattern Frequency Statistic on DB2.
As of R2025-06, the Pattern Frequency Statistic feature in Qlik Talend Studio > Data Profiling is not supported for DB2 databases.
Export the data in CSV format, define a file-delimited metadata type based on the CSV file, and then perform the profiling on that data.
For more information, see Pattern frequency statistics.
An active Idea has been logged to support this feature for DB2. To vote on the idea, log in to Ideation before going to #495364 Talend Studio Data Profiling (DQ) support db2 Pattern Frequency Statistics indicators.
A Talend Snowflake Job is failing at the t<DB>Connection component when acquiring the connection to execute sql.
The following error looks like below:
Getting the "Session no longer exists. New login required to access the service."
Comparing both Timeout settings within Talend Studio and Snowflake
The Snowflake or Talend Studio Snowflake component Login Timeout may have been set too low for what was required
If unable to access TAC using default credential (security@company.com/admin), you have forgotten your password.
You can reset it by following these steps:
UPDATE 'user' set 'password'=0x21232F297A57A5A743894A0E4A801FC3 where id =<userID>;
Change the default password used to configure the TAC database
The Talend Remote Engine Service fails to start, and systemd commands do not work as expected, resulting in the following error messages in the system logs:
Subject: Unit process exited
Defined-By: systemd
Support: https://access.redhat.com/support
An ExecStart= process belonging to unit talend-remote-engine.service has exited.
The process' exit code is 'exited' and its exit status is 126.
Jun 19 14:10:13 cmips-etl-ate-talend systemd[1]: talend-remote-engine.service: Failed with result 'exit-code'.
Subject: Unit failed
Defined-By: systemd
Support: https://access.redhat.com/support
The unit talend-remote-engine.service has entered the 'failed' state with result 'exit-code'.
Jun 19 14:10:13 cmips-etl-ate-talend systemd[1]: Failed to start karaf.
Subject: A start job for unit talend-remote-engine.service has failed
Defined-By: systemd
Support: https://access.redhat.com/support
A start job for unit talend-remote-engine.service has finished with a failure.
The job identifier is [Job Number] and the job result is failed.
Jun 19 14:17:50 cmips-etl-ate-talend systemd[1]: Starting karaf...
Subject: A start job for unit talend-remote-engine.service has begun execution
Defined-By: systemd
Support: https://access.redhat.com/support
A start job for unit talend-remote-engine.service has begun execution.
cd /path/to/Talend-RemoteEngine/binIf the engine starts successfully, the problem is with the systemd wrapper or permissions, not the engine itself.
chmod +x /path/to/Talend-RemoteEngine/bin/trun.sh
chmod +x /path/to/Talend-RemoteEngine/bin/talend-remote-engine-wrapper
chmod +x /path/to/Talend-RemoteEngine/bin/talend-remote-engine-service
Also, verify that the files are readable by the intended user and, if necessary, by the systemd process.
sudo setenforce 0Then, retry starting the service. If the service starts successfully, SELinux is the cause.
SELINUX=disabledReboot the server for the change to take effect.
SELINUX=permissiveReboot the server for the change to take effect.
Disabling SELinux reduces system security. Consider creating a custom SELinux policy to allow execution if you must keep SELinux enabled.
Exit status 126 in systemd indicates that the command was found but is not executable. This typically points to a permission issue on the script or binary that systemd is attempting to launch.
In this context of Talend Remote Engine, this is often caused by:
Cause A
Incorrect file permissions on the service wrapper scripts or binaries.
Cause B
SELinux policies prevents execution of the wrapper script or service file.
Scheduled task executions fail with the following error message:
Connection parameters were not received in time.
A possible cause for this error is that communication is disrupted, and the transferring of artifacts and parameters is retried but not completed in time.
If the delay is minor, you can increase the timeout so that the engine will wait longer at times of latency and not cause failures.
You can set the connection.parameters.timeout setting in <Remote Engine Install>/etc/org.talend.ipaas.rt.deployment.agent.cfg.
For example:
wait.for.connection.parameters.timeout = 600The following release notes cover the Qlik PostgreSQL installer (QPI) version 1.2.0 to 2.0.0.
Content
Improvement / Defect | Details |
SHEND-2273 |
|
QCB-28706 |
Upgraded PostgreSQL version to 14.17 to address the pg_dump vulnerability (CVE-2024-7348). |
SUPPORT-335 | Upgraded PostgreSQL version to 14.17 to address the libcurl vulnerability (CVE-2024-7264). |
QB-24990 | Fixed an issue with upgrades of PostgreSQL if Qlik Sense was installed in a custom directory, such as D:\Sense. |
Improvement / Defect | Details |
SHEND-1359, QB-15164: Add support for encoding special characters for Postgres password in QPI | If the super user password is set to have certain special characters, QPI did not allow upgrading PostgreSQL using this password. The workaround was to set a different password, use QPI to upgrade the PostgreSQL database and then reset the password after the upgrade. This workaround is not required anymore with 1.4.0 QPI, as 1.4.0 supports encoded passwords. |
SHEND-1408: Qlik Sense services were not started again by QPI after the upgrade | QPI failed to restart Qlik services after upgrading the PostgreSQL database. This has been fixed now. |
SHEND-1511: Upgrade not working from 9.6 database | In QPI 1.3.0, upgrade from PostgreSQL 9.6 version to 14.8 was failing. This issue is fixed in QPI 1.4.0 version. |
QB-21082: Upgrade from May 23 Patch 3 to August 23 RC3 fails when QPI is used before attempting upgrade. QB-20581: May 2023 installer breaks QRS if QPI was used with a patch before. |
Using QPI on a patched Qlik Sense version caused issues in the earlier version. This is now supported. |
A QlikView reload or Distribution task fails error message
System.IO.IOException: The process cannot access the file because it is being used by another process.
The task log will shows a successful reload but indicates the reloaded document can not be saved:
Information: Reload finished successfully
Information: Start saving document
Error: The sourcedocument failed to save.. Exception=System.IO.IOException: The process cannot access the file because it is being used by another process.
Error: at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
Error: at System.IO.File.InternalReplace(String sourceFileName, String destinationFileName, String destinationBackupFileName, Boolean ignoreMetadataErrors)
Error: at QVBWrapper.Document.ReplaceSourceFile(ILogBucket logBucket, String replaceFromFileName, String replaceToFilename)
Error: at QVBWrapper.Document.Save(ILogBucket i_LogBucket, String i_SaveAsFileName)
After a successful reload of a QlikView Application (QVW) file, the old file is removed and replaced with a new file containing the new data. The error message indicates either that the old file could not be removed, or that file access is too slow to process the request.
To identify if file access is too slow due to network latency, or due to disk read/write delays, review QlikView and its backend File Share System for details on the importance of fast file access, and how to monitor file shares.
In addition.
In the case of file locks caused by processes locking the original file, the most common processes include:
The recommendation is to exclude QlikView folders from anti-virus scan. See What QlikView folder/files to exclude for anti-virus scanning for more details.
Backup of QVW files must be planned and scheduled so that they do not interfere with QlikView tasks, to avoid file access conflicts.
The issue in general can only be resolved by identifying the process that is locking the file. See Process Monitoring - How to find locked files and the processes locking them for more details on how to identify the process that locks the QVW file.
The file was previously corrupted.
You may be expericing some performance issues related to the task execution time or resuming file takes large storage problem. It is possible to reduce the resuming and recovery Logs in JobServer to solve them.
As the -Drecovery.enabled parameter is primarily used to control the creation and use of the recovery file, Setting it to false disables the feature and meaning no resuming file will be generated or used. If you want to use recovery, you would leave this parameter enabled or set it to true (which is the default behavior)
This article briefly introuduces how to reduce job's resuming file if resuming file takes large storage
set MY_JVM_ARGS= -Drecovery.enabled=false The default behavior is true
In this article, we walk you through the requirements and process of how to upgrade and unbundle an existing Qlik Sense Repository Database (see supported scenarios) as well as how to install a brand new Repository based on PostgreSQL. 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.
Using the Qlik Postgres Installer not only upgrades PostgreSQL; it also unbundles PostgreSQL from your Qlik Sense Enterprise on Windows install. This allows for direct control of your PostgreSQL instance and facilitates maintenance without a dependency on Qlik Sense. Further Database upgrades can then be performed independently and in accordance with your corporate security policy when needed, as long as you remain within the supported PostgreSQL versions. See How To Upgrade Standalone PostgreSQL.
Index
Video Walkthrough
Video chapters:
The following versions have been tested and verified to work with QPI (1.4.0):
Qlik Sense February 2022 to Qlik Sense November 2023.
If you are on a Qlik Sense version prior to these, upgrade to at least February 2022 before you begin.
Qlik Sense November 2022 and later do not support 9.6, and a warning will be displayed during the upgrade. From Qlik Sense August 2023 a upgrade with a 9.6 database is blocked.
The Qlik PostgreSQL Installer supports installing a new standalone PostgreSQL database with the configurations required for connecting to a Qlik Sense server. This allows setting up a new environment or migrating an existing database to a separate host.
Using the Qlik PostgreSQL Installer on a patched Qlik Sense version can lead to unexpected results. If you have a patch installed, either:
Do not use the standard Qlik Sense folders, such as C:\Program Files\Qlik\Sense\Repository\PostgreSQL\ and C:\Programdata\Qlik\Sense\Repository\PostgreSQL\.
Do not use the standard Qlik Sense folders, such as C:\Program Files\Qlik\Sense\Repository\PostgreSQL\ and C:\Programdata\Qlik\Sense\Repository\PostgreSQL\.
Download the installer here.
Qlik PostgreSQL installer Release Notes
The following versions have been tested and verified to work with QPI (1.4.0):
February 2022 to November 2023.
If you are on any version prior to these, upgrade to at least February 2022 before you begin.
Qlik Sense November 2022 and later do not support 9.6, and a warning will be displayed during the upgrade. From Qlik Sense August 2023 a 9.6 update is blocked.
Uninstall the old Qlik Sense Repository Database service.
This step is required. Failing to remove the old service will lead the upgrade or patching issues.
Failing to reinstall the binaries will lead to errors when executing any number of service configuration scripts.If you do not immediately upgrade:
If the upgrade was unsuccessful and you are missing data in the Qlik Management Console or elsewhere, contact Qlik Support.
Now that your PostgreSQL instance is no longer connected to the Qlik Sense Enterprise on Windows services, all future updates of PostgreSQL are performed independently of Qlik Sense. This allows you to act in accordance with your corporate security policy when needed, as long as you remain within the supported PostgreSQL versions.
Your PostgreSQL database is fully compatible with the official PostgreSQL installers from https://www.enterprisedb.com/downloads/postgres-postgresql-downloads.
See How To Upgrade Standalone PostgreSQL, which documents the upgrade procedure for either a minor version upgrade (example: 14.5 to 14.8) or a major version upgrade (example: 12 to 14). Further information on PostgreSQL upgrades or updates can be obtained from Postgre directly.
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.
Qlik PostgreSQL installer version 1.3.0 Release Notes
Techspert Talks - Upgrading PostgreSQL Repository Troubleshooting
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 allows for Data Encryption for Qlik Sense Apps (QVF) and Data (QVD) Files.
Qlik Sense Engine can encrypt data by using a data encryption key (DEK), which is generated from a certificate-based key encryption key (KEK). The DEK is unique to each encrypted file and is stored alongside the encrypted data (inside the QVF and QVD files) in an encrypted format using RSA. The industry standard AES-256 GCM is used as the data encryption algorithm. Decryption requires access to the same certificate as used during encryption, which mean that the KEK certificate thumbprint in the certificate store must match the thumbprint used for the DEK generation.
Data encryption can be enabled in the Service Cluster configuration of the Qlik Sense Management Console. See the Online Help at Qlik Sense Enterprise on Windows > Administer Qlik Sense Enterprise on Windows > Managing a Qlik Sense Enterprise on Windows site > QMC resources overview > Service cluster > Data encryption
This is a simple example of how to explore data encryption in Qlik Sense Enterprise on Windows.
ASCII: Load if(RecNo()>=65 and RecNo()<=90,RecNo()-64) as Num, Chr(RecNo()) as AsciiAlpha, RecNo() as AsciiNum autogenerate 255 Where (RecNo()>=32 and RecNo()<=126) or RecNo()>=160 ;
STORE ASCII INTO [lib://MyData (domain_administrator)/ascii.qvd] (QVD);
Doing this with the correct account is crucial to make the generated certificate available to the service account.
New-SelfSignedCertificate -Subject "QlikSenseDataEncrytion" ` -KeyAlgorithm RSA ` -KeyLength 4096 ` -Provider "Microsoft Software Key Storage Provider" ` -KeyExportPolicy ExportableEncrypted ` -CertStoreLocation "cert:\CurrentUser\My"
New-SelfSignedCertificate -DnsName "QlikSenseDataEncrytion" ` -CertStoreLocation "cert:\CurrentUser\My"
Files remain encrypted after disabling encryption until the next following app reload or QVD generation.
Compare the unencrypted and encrypted files to validate successful encryption
Qlik Sense app (.qvf) file is a binary file, which makes it harder to visually confirm the encryption effect.
Encrypted app files have multiple references to ciphertext, which in turn refers to secrets used for the encryption.
App file without encryption has no such references. The cypher text portion of QVF represents the data encryption key (DEK) used to encrypt the app data and bookmarks.
Encrypted data (.qvd) files has "Encryption Info" defined, which includes the data encryption (DEK) references.
Data part is also significantly different, even though both version have exactly the same static data content.
Qlik Sense on Windows: Data Encryption Key Rotation
Using Server Certificates for Data Encryption
This video will demonstrate how to install and configure Qlik-CLI for SaaS editions of Qlik Sense.
Content:
get-command qlik
choco install qlik-cli
if ( -not (Test-Path $PROFILE) ) {
echo "" > $PROFILE
}
qlik completion ps > "./qlik_completion.ps1" # Create a file containing the powershell completion.
. ./qlik_completion.ps1 # Source the completion.
Advanced and additional instructions as seen in the video can be found at Qlik-CLI on Qlik.Dev. Begin with Get Started.
After adding a Global Rule to rename the target Schema (example: from PUBLIC to QLIK_TEST), the task may fail with an error indicating it was still trying to use the previous (example: PUBLIC) schema.
Reviewing the task JSON file to check the Global Rule definition shows no issues.
However, messages in the task logs indicate the table being created in the PUBLIC schema is not a task table. The table is an attrep change table:
00002308: 2024-03-25T16:51:38 [METADATA_MANAGE ]E: Failed (retcode -1) to execute statement: 'create or replace file format "PUBLIC"."ATTREP_FF_DEV_OS_STG_c1a25c9f_deef_f647_817b_db90dadf622b"
Since the table mentioned in the error is not the actual target table, but a control table the resolution is to configure the control tables screen to also use the new schema (example: QLIK_TEST).
Screen Shot of the Control Tables Settings after setting schema to QLIK_TEST:
When attempting to publish a standard DI job to Talend Management Console or an external artifact repository (regardless of if using Talend Studio or Talend CICD), you may be encountering the following error:
Caused by: org.talend.ipaas.services.inventory.InventoryException: workspace-service: failed to create artifact - Cannot publish artifact with the job type='data_service' because in one or more workspaces exists the same artifact with the different job type.
Other jobs may be able to publish to the same locations, even in the same project, without any specific issues.
Two suggested solutions
<additionalProperties xmi:id="_AVcxxO-mEe-Txxx_U4MkQ" key="BUILD_TYPE" value="OSGI"/>
Do not forget to re-publish your job at last
The issue, in many cases, may be an invalid entry within the job properties file, which still lists the job type as "Talend Runtime(OSGI)".
For this concurrent DI job, perhaps it was saved or exported at that time when there was a ESB component inside (Automatic Detective for build type). That’s why the job properties file had this line:
<additionalProperties xmi:id="_AVcxxO-mEe-Txxx_U4MkQ" key="BUILD_TYPE" value="OSGI"/>
During the publish-to-cloud via Talend studio or Talend CICD, the JobType will be set to “data_service” due to this wrongly set of BUILD_TYPE in the job properties file. With that invalid entry, the job cannot be used as a standalone job or microservice.
Currently, in Qlik Application Automation it is not possible to export more than 100,000 cells using the Get Straight Table Data block.
Content:
To overcome this limit, the workaround is to export records in batches from the Qlik Sense straight table to the cloud storage platform of your choice. The prerequisite is to have a unique numerical field in your dataset. If you don't have the unique field in your dataset, you can add it using RowNo() function in the load script as shown below. This counts the rows in the dataset.
In this example, we will export data from the Qlik Sense straight table to Dropbox as a CSV file.
You can also find an exported version of this automation and application attached to this article. More information on importing automation can be found here.
Automation Part 1
Automation Part 2
Automation Part 3