Importing and Exporting Content as Files

In Deployment, you can create and manage exports and imports of content using .tgz files.

You can export the following:
  • Dimensions
  • Currency tables
  • Roles
  • External connections, including Import Data Connections, Live Data Connections, and Smart Data Integration (SDI) connections
  • Allocation steps and processes
  • Wrangles
  • Legacy value driver trees
  • Data locking
  • Validation rules
  • Data actions
  • Public files, including folders, stories, analytic applications, models, and Digital Boardroom presentations
    For translated stories, the multilingual content is included in your export. For details, see Multilingual Content Support.

Content is exported to a local file that can then be imported.

When you import or export content in Deployment, you name and save the details of the imports and exports as units or delivery units. The units are listed in the Import and Export windows, along with details such as their status, and start and finish times. This allows you to examine and manage your import and export history. For example, you can open a delivery unit to view what content was imported or exported, such as dimensions. You can also open a unit again and reuse a unit, or change its details and export it again if necessary.

You must be assigned a role with Lifecycle MAINTAIN permissions if you want to perform deployment.

It is not recommended to use exports to archive content. Content can only be imported in the same version of the application from which it was exported, or the subsequent version. After your system is upgraded again, you cannot import the content.

For the maximum file sizes, see System Sizing, Tuning, and Limits.