Qlik Community

Support Knowledge Base

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Announcements
Coming your way, the Qlik Data Revolution Virtual Summit. October 27-29. REGISTER

How to reload data after using the QlikView Converter tool

Digital Support
Digital Support

How to reload data after using the QlikView Converter tool

This video demonstrates how to reload data after migrating a QlikView document to Qlik Sense using the QlikView Converter tool in DevHub.

Video Transcript:

Hi and Welcome to Qlik Fix
This video demonstrates how to reload a recently converted QlikView document in Qlik Sense.

When converting a QlikView document to a Qlik Sense app using the QlikView Converter tool, the load script connection string remains unchanged.
The connection string format is specific to QlikView load script, which allows for absolute and relative paths as well as for connection string parameters to be stated directly in the script.
So when attempting to reload the app with the original connection string, the error seen here will be displayed:
"CONNECTs other than LIB CONNECT are not available in this script mode"
In Qlik Sense, Legacy (QlikView) mode can be enabled by disabling Standard mode under the Engine's configuration in QMC.
However, this is not a recommended practice due to security considerations.
Also, Legacy mode is not supported in Qlik Sense SaaS editions.
In Qlik Sense, connection string information is stored in the Qlik Sense Reporsitory postgres database (QSR). These connections are then listed in the QMC under Data Connections.
In this example, we see that the QlikView ODBC Connector Package SQL driver is used to connect to a SQL database.
However, this issue is observed regardless of the source database type, and even if Windows ODBC Data Sources Names (DSN) are used.
In order to correct the issue a new Data Connection record that contains this connection string information needs to be created and used instead.
The Qlik Sense Installation includes by default the QVOdbcConnectorPackage drivers so the Microsoft SQL Connector can be selected.
In another scenario where an ODBC DSN is used instead, the first step would be to create an ODBC System DSN using the Windows ODBC Data Source Administrator on all Qlik Sense Server nodes used for reloading the data.
Then, select this new DSN when creating the new ODBC Data Connection.
Next, simply click on the "Insert connection string" button for the Data Connection created
Make sure to remove or comment out the old connection string.
You can alternatively re-select the data that is needed by the app and then insert the Load script.
The reload of the app should now succeed and future reloads may be scheduled via Tasks.
If the app is uploaded to Qlik Sense SaaS, a new connection will need to be created as well accordingly.
Note that in SaaS, the Data Connections are stored within Spaces.
If the application is moved to another Space, and the user scheduling or running app reloads does not have access to the original Space, then re-creating the Data Connection in the new Space is necessary.
Under the Space Data Sources click on "Add connection" and configure the connection.
Thanks for watching!

Related Content:

Labels (2)
Version history
Revision #:
2 of 2
Last update:
‎2020-08-31 08:31 AM
Updated by: