Replacing apps

You can choose to replace an app either by republishing the app or by importing and replacing an app.

You can choose to replace a published app when you publish an app from the QMC. When you have clicked Publish in the action bar, the option Replace existing app is available in the Publish app window.

When you publish an app from the QMC, the owner's app is moved from the Work folder to the Published folder and is marked with a stream icon (ã) to indicate that it has been published.

When you replace an app by importing an app, you can replace the whole app or import without the data. If you import without the app data, you replace everything in the app but the data and data model. Replacing an app with an imported app requires the following access rights:

  • Update on the app to be replaced.
  • If the app is published, Publish on the app to be replaced and Publish on the stream to which the app has been published.

Replacing an app with an imported file

Haga lo siguiente:

  1. Select Apps on the QMC start page or from the StartS drop-down menu to display the overview.

  2. Click PImport in the action bar.

    The Import app dialog opens.

  3. Select a file to import.

  4. Browse to the app (qvf file) you want to import and click Open.

    Nota: If the app includes an image with a long file name, so that the full path to the image is longer than 260 characters, the import will fail. Reduce the image file name if the path is too long.

    The browse dialog closes and the name of the qvf file is displayed in the App name field in the Import app dialog.

    You can change the name of the app in the App name field. If the App name is not unique, a message is displayed with information on how many apps that already have this name.

    Nota: If the name of a data connection in the imported app is the same as the name of an existing data connection, the data connection will not be imported. This means that the imported app will use the existing data connection with an identical name, not the data connection in the imported app.
  5. Select Replace existing app.
  6. Click App to replace and select the app.
  7. If you want to import without data, select Import without data. Only visualizations will be replaced.
  8. Click Import in the dialog.

    The Ongoing transports dialog opens. Any other transports you have initiated are also displayed in the dialog.

    • A spinner is displayed during the file import.

    • Click E to cancel the import.

      è and Aborted are displayed and the import stops.

    • Click OK to remove a failed item è.

      The item is removed from the Ongoing transports dialog.

    When the app is replaced, m is displayed and the app is added to the Apps overview. When all your transports have finished successfully, the Ongoing transports dialog closes. If there are any failed transports, the dialog is displayed until the overview page is refreshed.

    Nota: When importing an app to a server, or exporting an app from a server, related content that is not stored in the .qvf file, such as images, is also moved. The related content is stored in a separate folder: %ProgramData%\Qlik\Sense\Repository\AppContent\<App ID>. Each app has its own app content folder, with the app ID as the folder name.

Replacing the app content folder

App content that is not stored in the .qvf file, such as images, is stored separately in a folder: %ProgramData%\Qlik\Sense\Repository\AppContent\<App ID>. Each app has its own app content folder, with the app ID as the folder name.

  • Existing files are kept.
  • New files are added.
  • New files replace existing ones with the same name.