Qlik DataTransfer Release Notes - August 2022 Initial Release

[suhas_sutariya]

Table of Contents

• What's new in Qlik DataTransfer August 2022
• Resolved Defects
• Improvements
• Known issues and limitations
• Upgrade notes
• System requirements notes

The following release notes cover the versions of Qlik DataTransfer released in August 2022.

What's new in Qlik DataTransfer August 2022

Qlik DataTransfer August 2022 release does not have any new feature, but it has fixes for the issues described below and few other improvements.

Resolved Defects

Qlik DataTransfer August 2022 comes with fixes for the issues described below.

 

August 2022

Upload fails due to tus failed to upload files and copying error.

Jira issue ID: DTB-57

Description: When data files are uploading, it gives errors like "Error copying file to local temp location" and "socket hang up". This is majorly due to parallel uploading of same named files in same space.

QDT Create connection UI hides ODBC System DSN connector when adding additional connectors.

Jira issue ID: DTB-58

Description: After adding SAP connectors as additional connector, it adds up in the connector list and ODBC connector icon is not visible anymore in the UI.

Improvements

Qlik DataTransfer August 2022 comes with below improvements in current features.

Improved upload process by adding validation, configuration and error handling.

Description:

• To avoid the errors coming while parallel upload of a same file in Data Folders, a file will be added in queue. With this mechanism, if a file is generating or updating very frequently, you can add some delay before it actully starts uploading a file. We call it debounce delay. This can be configured through services.conf file under [data-upload-service.parameters] by adding --debounceDelay 5000 (ms) . default is 0 ms. This is not applicable to Data Connections and Qlik Apps. For scheduled  Data Connections and Qlik Apps, if a dataset is already executing or in progress, it will be skipped and execute on next scheduled time.
• In case of poor internet bandwidth, user can lower the chunk upload size. Add --chunkSize 200 ( in mb) in services.conf under [data-upload-service.parameters]
• Added support for reading trusted root certificates from Windows Certificate Store on startup of a service. This will ensure that QDT TLS certificate validation results match other appplications installed on the same system, e.g . MS Edge, Google Chrome, IE.
• Improved error logging for request errors where it was giving pseudo status codes. 

Known issues and limitations

The following issues and limitations were identified at release time. The list is not comprehensive; it does however list all known major issues and limitations.

General

• Qlik DataTransfer only uploads files with size less than 6 GB.
• You can upload a maximum of 200 tables or files per dataset. If your dataset has more than 200 tables or files, only the first 200 are uploaded. For example, if you select more than 200 tables in a data connection or Qlik app, or if you add a data folder with more than 200 files.
• When reloading apps created in Qlik Sense Desktop, Qlik DataTransfer does not support connections to Essbase.
• Files uploaded using Qlik DataTransfer must be manually deleted from SaaS editions of Qlik Sense. Qlik DataTransfer does not delete files from SaaS.
• While Qlik DataTransfer can extract data from any .qvf file, it can only reload the data in that .qvf if it was created using Qlik Sense Desktop and all of the data sources for that .qvf are accessible from the Qlik DataTransfer machine.
• Qlik Sense Desktop cannot be installed on server operating systems. Therefore, if you install Qlik DataTransfer on a server operating system, and wish to use the QVF refresh functionality, you must create the app on a desktop operating system and then copy your QVF files to the server. All data sources that are used in the QVF file must be accessible to the QVF load script when it is run on the server by Qlik DataTransfer.
• Qlik DataTransfer should not be used to upload data from Qlik apps that use section access or have load scripts that control user access to data. Protected data might be exposed to unauthorized users.
• Incremental load is not supported.
  Work around: Use Qlik Sense Desktop to create an app including incremental load logic, and reload it using the Qlik Apps.
• You cannot edit the query or data sources of the Data Connection.
• There is no notification of upload and reload failures for scheduled tasks. To determine if your data has uploaded successfully, please check the last execution details or consult the log files.
• Mapped drives are not supported. You can use a shared path instead: \\<machine-name>\folder.
• If you change the service log on account after configuring Qlik DataTransfer with your tenant, you must reconfigure the tenant and connections.
• QlikView apps are not automatically reloaded by Qlik DataTransfer when data sources in apps are updated with new data. QlikView apps must be manually reloaded and saved for Qlik DataTransfer to upload data to a SaaS edition of Qlik Sense tenant.
• If write access to configured space is revoked, the upload will be failed and results in errors which can be seen in the logs but not in the UI.
• In Data Folder, if unsupported files i.e..png, .bmp, etc. are resided along with supported files and QDT tries to upload them it fails to upload unsupported files. Hence it will show status as ‘Failed’.
• On upgrade from the Oct2020 release or later, if a user chose a different location for storing configuration files or chose different ports to run QDT from configuration file - Service.conf – the installation will override it. The mitigation to this known issue is to backup this file prior to the upgrade and update the Service.conf file with earlier changes after the upgrade completed.
• You changed the configuration folder location from C:\ProgramData\Qlik to some another location in Service.conf file and when you uninstall Qlik DataTransfer, it is not deleting the configuration folder.
• While the Daylight Saving is happened, Qlik DataTransfer changes the scheduled hour. So schedules in Qlik DataTransfer are updated on new DST time.
• Qlik DataTransfer does not support the use of web proxies. If your system uses proxies, you must add a proxy bypass rule specifically for Qlik DataTransfer.
• Special characters from Japanese language are not supported if they are used in the table name or file name or path. Ex. 【】

Upgrade notes

 

Qlik DataTransfer older versions

Backup recommendations:

It is important that you make a backup of the folder C:\ProgramData\Qlik\Sense\DataTransfer  and C:\Program Files\Qlik\DataTransfer\services.conf  before upgrading, to be able to recover the installation if the upgrade fails.

If you are installing or upgrading on machine where Qlik Sense Enterprise for Windows is already installed, please make sure you install/upgrade Qlik DataTransfer using Qlik Sense service(s) user account.

System requirements notes

Please refer to the online help for information about the requirements for Qlik DataTransfer.

System requirements for Qlik DataTransfer

About Qlik

Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.

qlik.com