You can export all the objects that you create within a Space (such as Workflows, Views, or Functions), and then bring them into another Space, either in the same Environment or a different one.

The following objects can be exported from a Space, and imported (or synchronized) to another Space:

  • Workflows.
  • Views.
  • Functions.
  • User-defined Function categories.
  • Datasets.
  • Data held in Datasets.
  • Schedules.
  • Step Settings (for example Find duplicates rules and blocking keys).
  • External systems.
  • External system credentials. For security reasons, passwords and permissions used by credentials are not exported.
  • Custom events.
  • Notifications.
  • Training datasets for tags, and associated Tags. There is a limit of 250 tag training datasets for any particular export. Consider removing unused training datasets if the datasets you require are not being exported.

Export from a Space

To export data from a Space:

  1. Go to System > Spaces.
  2. Click the Options menu for the Space you want to export from.
  3. Select the Export option.
  4. Select the objects you would like to export.
  5. Select Download in browser to download a Data Studio metadata exchange (.dmx) file to you browser's downloads folder. If you also choose to export the data held in one or more selected Datasets, the downloaded file will have a .dmxd extension.

By default only Workflows, Views and Functions that have been published are displayed in the export list, but drafts can also be selected by checking the Use draft versions option. Draft versions can be imported into another space but cannot be synchronized.

Where an object has both a published version and a draft version, the Use draft versions checkbox also determines which version is selected for export. If Allow draft versions is switch off, the Published version will always be selected.

Export objects with dependencies

Metadata objects in Data Studio often have dependencies: For example, a Workflow uses a View as a source, that View is based on a Dataset, and the Dataset was loaded from an External System using a specific Credential.

Any dependencies between objects you select for export will be highlighted on the metadata export screen. However you do not need to export these dependent objects, and they are not automatically selected. These objects may already exist in the target environment, or you may be planning to map the dependencies to new objects.

Import or Synchronize into a Space

There are two ways to bring your exported data and metadata into another Space:

  • Import. Importing into a Space will create new copies of objects in the target Space. No link is maintained between the objects in the source Space and the target, so importing is typically a one-off process. Common use cases for Import are to:
    • Set up a new Space that's a copy of an existing one, but where you won't need to keep the two Spaces in sync.
    • Bring useful Functions or Views from a standard package into a new environment to avoid the need to re-implement them.
  • Synchronize. Synchronizing into a Space maintains a link between objects in a source and target Spaces. This means that future Synchronizes between the two spaces can keep these objects in sync as they are modified over time. Common use cases for Synchronize are to:
    • Promote changes to Workflows, Functions etc. between development, test, and production environments.
    • Keep two environments in sync when changes are being made to Functions shared by both, and retain the version history.

To import or synchronize a metadata package into a Space:

  1. Go to System > Spaces.
  2. Click the Options menu for the Space you want to populate.
  3. Select the Import or Synchronize option as appropriate.
  4. Select the .dmx or .dmxd file containing the objects you're importing and click Next.
  5. Select the objects you would like to bring into the Space.
  6. Click Import

Import

Objects are imported to the target Space as drafts (whatever their status in the source Space) and version history is not retained.

Synchronize

The source and target Spaces have to be in different Environments and only published versions of objects can be used.