Skip to main content Skip to complementary content

In-app reporting with exported or migrated apps

In-app reporting is available for apps that have been exported and uploaded into Qlik Cloud Analytics.

After uploading an exported or migrated app, you need to add the required data sources to the space, update the app's load script as needed, and build the remaining reporting assets in the app.

There are a number of scenarios in which you might need to work with exported apps:

  • Apps that are migrated (exported) from Client-Managed Qlik Sense or Qlik Sense Desktop to Qlik Cloud.

  • Apps that are exported from Qlik Cloud and re-uploaded into the same or a different Qlik Cloud environment.

The following sections outline the required processes for working with exported and migrated apps.

Exported apps from Qlik Cloud

When a Qlik Sense app is exported from Qlik Cloud, it can re-uploaded into the same or another Qlik Cloud environment. This is common, for example, when sharing apps with other users. You can use in-app reporting with these apps.

Some of the reporting assets will need to be recreated in an uploaded app. The following table outlines what you will need to recreate.

Which reporting assets are preserved when I export and re-upload an app into Qlik Cloud?
App export option Report tasks Report filters Recipients Groups Templates
With data Not preserved Preserved Preserved Preserved Not preserved
Without data Not preserved Preserved

Preserved if compatible data sources exist in space

Information noteThe app also needs to be reloaded.

Preserved if compatible data sources exist in space

Information noteThe app also needs to be reloaded.
Not preserved

Apps migrated or exported from Client-Managed Qlik Sense or Qlik Sense Desktop

You can use in-app reporting with apps that were created with Client-Managed Qlik Sense or Qlik Sense Desktop.

Here is a general workflow for using in-app reporting with apps from Client-Managed Qlik Sense and Qlik Sense Desktop:

  1. If you are manually migrating the app, export the app from the environment in which it is located, and then upload it into a personal or shared space in Qlik Cloud.

  2. Comprehensive tools are also available to facilitate the migration process for apps created in Client-Managed Qlik Sense. Apps migrated to Qlik Cloud using these tools can be used for in-app reporting. For more information about the process, see Migrating from Client-Managed Qlik Sense.

  3. In the space where you uploaded the app, add the data sources used by the app.

  4. Modify the load script in the newly uploaded app. The script needs to use syntax and functions that are compatible with Qlik Cloud.

    For example, the load script might reference a data source location named AttachedFiles. In Qlik Cloud, this location is instead named DataFiles, in addition to referencing the space location.

  5. For apps from Client-Managed Qlik Sense with Excel templates created for Qlik NPrinting, you can migrate the templates for compatibility with Qlik Cloud reporting.

    For a full guide, see Exporting Excel report templates from Qlik NPrinting to Qlik Cloud.

  6. If you are instead creating report templates from scratch, you can start creating the templates after the app has been uploaded into Qlik Cloud.

  7. In the app, build the remaining reporting assets and add all required templates.

Apps published or distributed from Client-Managed Qlik Sense

In-app reporting is not available for apps published or distributed from Client-Managed Qlik Sense (including multi-cloud deployments) to Qlik Cloud. To use in-app reporting with these apps, migrate the app to Qlik Cloud using the migration tools (see Setting up the Qlik Cloud migration tools), or manually export the app and re-upload it into Qlik Cloud.

To learn more about using in-app reporting with migrated and exported apps, refer to Apps migrated or exported from Client-Managed Qlik Sense or Qlik Sense Desktop.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!