You can export Data Studio objects (such as Workflows, Views or Functions) from one Space to another, either in the same or different Environment.
The following objects can be exported from one Space and imported (or synchronized) into another:
To export data from a Space:
By default only published objects are displayed in the export list. However, drafts can also be chosen by selecting Use draft versions. Draft versions can be imported into another Space but can't be synchronized.
Where an object has both a published and a draft version, the Use draft versions checkbox also determines which version is selected for export. If Allow draft versions is switched off, the published version will always be selected.
Metadata objects in Data Studio often have dependencies. For example, a Workflow uses a View as a source but that View is based on a Dataset loaded from an External system using a specific credential.
Any dependencies between objects selected for export will be highlighted on the metadata export screen. However, you don't have to export these dependent objects and they aren't automatically selected because they may already exist in the target Space or you might want map them to new objects.
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. Objects are imported to the target Space as drafts (whatever their status in the source Space) and version history is not retained.
Common use cases are to:
Set up a new Space that's a copy of an existing one when you don'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 the source and target Spaces. This means that future synchronization between the two Spaces can keep these objects in sync as they're modified over time. The source and target Spaces have to be in different Environments and only published versions of objects can be used.
Common use cases are to:
Promote changes to objects between development, test, and production Environments.
Keep two Environments in sync when changes are being made to objects shared by both, and to retain the version history.
To import or synchronize a metadata package into a Space: