Page Comparison

...

An App Import Profile tells to inProcess App Operations which applications Qlik Applications it should upload and how they should be named in the target Qlik Sense Server or Qlik Cloud Tennant.

All App Import Profiles should be stored inside the AppImportProfiles node:

...

The AppImportProfiles attributes are:

• ProfileName
  (Required) Name of the App Import Profile. The ProfileName must be unique.
  This name is required and must be used during Bulk Import Apps Command commands.

• QVFSourceFolder
  (Optional) Folder where QVF files are stored.

• AppListJsonFileName
  (Optional) Full file name of stored list of exported Qlik Applications.
  FileName property will replace QVFSourceFolder parameter.
  When using AppList.json, we can use the AppNamePattern property to define how the QVF files will be renamed at the target Qlik Sense Server.
  For more details: https://ipc-global.atlassian.net/wiki/spaces/IAO/pages/14696939569/Bulk+Export+Apps#The-AppList.json-file

• SkipConfirmation
  (Required) (true|false) Skip Confirmation message. Set to true for Scheduled Tasks.

• AppNamePattern
  (Optional) Defines the name pattern of the Qlik Application to be created.
  Important: when AppNamePattern or AppListJsonFileName is blank, the App name will be the QVF file name.
  Pattern segments:
  {id}: The ID of the Qlik Application
  {app}: The Name of the Qlik Application
  {stream}: The Stream of the Published Qlik Application
  {year}: The export Year (yyyy)
  {month}: The export Month (MM)
  {day}: The export Day (dd)
  {hour}: The export Hour (HH)
  {minute}: The export Minute (mm)
  {second}: The export Second (ss)
  {ownerId}: The Qlik GUID Owner ID
  {ownerUserId}: The Qlik Owner User ID
  {ownerUserDirectory}: The Qlik Owner User Directory
  {ownerName}: The Qlik Owner User Name

...