QlikView Documents
The QlikView Documents tab maps client-managed QlikView documents to be migrated to Qlik Cloud. This includes the option to convert them to Qlik Sense applications upon migration.
Cloud table columns
Status
Displays the current status of the object using visual indicators. One of three possible options:
- Cloud: Object already exists in Qlik Cloud. Hover over the status to see the Qlik Cloud object information.
- Warning: There is a setting that must be configured for a successful migration. Hover over the warning indicator to see the warning(s).
- None: Row can be migrated successfully.
App Name
The name of the app in the Qlik Cloud tenant.
App Owner
The owner of the app in the Qlik Cloud tenant.
Space Configuration
Set the space configuration for the app. This determines where the app will end up when migrated to Qlik Cloud.
When editing the row (see Actions below), two toggles appear: one for determining whether an app will land in a personal space or shared space, and one for determining if the app should be published when running the Publish Applications step. When editing, you can also configure additional managed spaces for publishing.
Export Type
The type of export to perform on the app.
- With Data exports the app with data.
- Without Data exports the app without data.
Converting the QlikView document to a Qlik Sense app requires exporting With Data.
Convert
Controls whether to convert the QlikView document to a Qlik Sense app during migration. If set to No, the document will be migrated directly as a .qvw. For additional information about this option, see Configure QlikView to Qlik Sense Conversion.
Actions
Click Edit to make changes to the row metadata as it will appear in Qlik Cloud. Once complete, either click Save in the Actions column to save changes, or click Cancel to revert to the previous settings.
To update object metadata at scale, select the rows you wish to edit and choose from actions under the Actions button at the top of the table, or apply changes using Excel export and import for bulk editing, advanced transformations, or updates generated outside the tool.