You will need to analyze your QlikView documents and prepare them for conversion. The amount of work you have to do depends on the complexity of the QlikView documents you want to convert, and the type of objects they contain. If you have already prepared your QlikView documents, you can create your Qlik Sense apps.
Preparing the QlikView document
QlikView documents and Qlik Sense apps derives from different products and work in different ways, so, depending on how the QlikView document is constructed, you will have to prepare the QlikView document (QVW) for conversion.
Disable Always One Selected Value
If the QlikView document contains list boxes or multi boxes, you must disable the Always One Selected Value property for each of these objects, where set. This is in order to clear selections in the Qlik Sense app.
Converting hidden script tabs
If your QlikView document contains hidden script, you need to adapt the document before you convert it. Otherwise, when a QlikView document with hidden script is converted, the hidden script part will be disregarded and not included in the Qlik Sense script.
If you want to convert the entire script, do the following before converting the document. This requires that you have access to the hidden script in the QlikView document.
- Open the document in QlikView Script Editor.
- Copy the code from the hidden script tabs and paste it into regular script tabs.
- Save the document.
Removing section access code
A QlikView document with section access cannot be directly imported to Qlik Sense, as there are differences in format and supported functionality.
To convert a QlikView document that has section access, before converting the document, open the document, and in the QlikView Script Editor, remove section access. This requires that you have full access to the script of the document.
After you have removed the section access from the Script Editor, you must reload the document for section access to be completely disabled. Then you also must open the document properties and deselect the Initial reduction... item.
You can then re-apply section access in the Qlik Sense app when you have created the app.
Handling features not supported in Qlik Sense
There are some features in QlikView that are not supported or recommended in Qlik Sense:
- Input fields
- Message boxes
- Bundle and Info load
- ALL qualifier
- If you convert you document in order to use it in Qlik Sense Cloud, then ODBC/OLEDB connections are not supported
Before you start the conversion, we recommend that you check your script code against these lists of statements and functions that are not supported or recommended, and adapt the code according to recommendations. It is also possible do adapt the script in the data load editor in the Qlik Sense app after conversion.
QlikView variables excluded from export
A number of variables are not exported from a QlikView document (QVW) as they are only relevant for QlikView or is handled differently in Qlik Sense.
The following variables are not exported from a QlikView document:
- All variables starting with CD
- All variables starting with FLOPPY
Analyze the QlikView document
A convenient way to test whether or not visualizations and other objects can be converted is to process the QlikView document by opening it in the converter tool. All objects that were converted will be shown in the Visualizations, Dimensions, Measures, and Variables tabs in the tool. Objects that cannot be converted, will be shown in the Unconverted objects tab.
After you have gathered this information, you can determine if you want to recreate the unconverted objects in Qlik Sense.
Bearing this in mind, check your document for objects that will not be converted, for example:
Changing language in Qlik Sense for supported languages in Qlik Sense (opens in a new browser tab).
- Custom on non-standard fonts
- Non-standard colors, such as corporate colors