Completing your app after conversion

QlikView and Qlik Sense are different products and conversion is not exact, which means that there will be work to do in Qlik Sense before you can deploy a Qlik Sense app equivalent to the original QlikView document.

After you have created the app in the converter tool, there are a number of things to do:

• Adapt the data load script. This could include re-applying section access code, changing path references to data connections.
• If you have data connections, you will need to re-create them and then check the app.

• Recreate unconverted objects (as shown in the converter tool Unconverted objects tab).

• Create sheets to contain the visualizations from the QlikView document objects you are converting.

You should duplicate the converted app and make changes in the copy, to avoid overwriting work during a later conversion.

Adapting the data load script in Qlik Sense

Qlik Sense and QlikView data load scripts are compatible in general, but there are some differences, which means you may have to adapt the script in the data load editor in your Qlik Sense app before you can reload data.

Re-apply section access code

If you removed section access code in your QlikView document before it was converted, you can re-apply it in the Qlik Sense app. There are some differences that you may need to take account for:

• User authentication is different in Qlik Sense. The USERID field is used to authenticate all users, and the NTNAME and PASSWORD fields are not supported.
• If you have access to the script, but not to the data, you can open the app without data and edit the script, including the section access.
• Section access is applied using strict exclusion in Qlik Sense. This means that you can only see data that you have been specifically granted access to.

Changing file path references to data connections

QlikView uses absolute or relative file paths which are not supported in Qlik Sense standard mode, so you need to use folder data connections to point to file locations instead.

Do the following:

1. Create folder data connections for all file paths that are used in the data load script.

   Connecting to data sources

   You need to check statements and functions that refer to files. LOAD statements are the most common ones, but there is a complete list available.

   File system access restriction

2. Replace all references to absolute or relative file paths in the script with lib:// references to the data connections you created.

   Examples

   Original script in QlikView	Adapted Qlik Sense script
   LOAD * FROM [C:\data\Tutorials source\Sales rep.csv];	LOAD * FROM [lib://Tutorials source/Sales rep.csv]; In this case, the Tutorials source folder data connection should be pointing to C:\data\Tutorials source\, or where the data is located if you have moved the app to another computer or a Qlik Sense server.
   FileSize('C:\data\Tutorials source\Sales rep.csv')	FileSize('lib://Tutorials source/Sales rep.csv')
   for each Dir in dirlist ('C:\data\Tutorials source\*' )	for each Dir in dirlist ('lib://Tutorials source/*' ) For each..next

Features not supported in Qlik Sense

If you did not analyze the data load script in the QlikView document for features in QlikView that are not supported or recommended in Qlik Sense, you can check the data load editor in the Qlik Sense app.

• Input fields
• Message boxes
• Bundle and Info load
• ALL qualifier

We recommend that you adapt the data load script according to the recommendations.

QlikView functions and statements not supported in Qlik Sense

QlikView functions and statements not recommended in Qlik Sense

Installing custom connectors

If your QlikView document uses custom connectors to access data, you should be able to use them to load data in Qlik Sense as well without having to change the script. This requires that the same connector is installed on the Qlik Sense server.

Using apps that are created in other Qlik Sense products

You can use apps that you create in different Qlik Sense products. For example, you can use an app created in Qlik Sense Enterprise in Qlik Sense Desktop, or Qlik Sense SaaS.

For Qlik Sense Enterprise, the converter tool saves apps as a binary files in the Qlik Sense repository. You can export a binary file to a QVF file using the Qlik Sense QMC, and then upload the app to Qlik Sense Desktop or Qlik Sense SaaS.

For Qlik Sense Desktop, the converter tool saves apps as QVF files here: C:\Users\User\Documents\Qlik\Sense\Apps.

The app can be imported into Qlik Sense Enterprise using Qlik Sense QMC, or uploaded to Qlik Sense SaaS.

Typically, you will need to re-create any data connections in the new location.