Exporting definitions - Data360_DQ+ - Latest

Data360 DQ+ Help

Product type
Product family
Data360 DQ+
Product name
Data360 DQ+
Data360 DQ+ Help
First publish date

If your organization uses Data360 DQ+ across multiple instances, you can use the Export Definitions and Import Definitions functionality to move data stages into and out of the platform.

  1. Select the Pipelines menu at the top of the page.
  2. Select the pipelines or data stages that you want to export.
  3. Click the menu button at the top of the Pipelines browser:

  4. Select Export Definitions.
  5. An Export dialog will ask you if you want to reset the "dirty state" for items being exported.

    The "dirty state" of an item indicates whether the item's definition has changed since the last time it was promoted or exported. In the Pipelines view, you will see that some items have an asterisk to the right of their name. This indicates that the item has a "dirty state", meaning that the item's definition has changed since it was last promoted or exported.

    If you choose to reset the dirty state when exporting, the dirty state of the item will be set to false and the asterisk will disappear in the source environment. The asterisk will be displayed again if the data stage is edited after the export.

    Select Yes or No, as require

    A zip file containing the export definitions will be downloaded, which can be imported into other instances of Data360 DQ+ by an administrator. If you are an administrator, see Administering Pipelines Across Multiple Instances for more information on importing definitions.

What is included in an export?

When you export the definitions of a data stage, you are exporting the behind the scenes rules that define the data stage. Exports do not include any data that is associated with a data stage. For example, if you export a data store and then import it to another instance, the data store will contain all of the fields and settings that you applied to it in its original instance. However, the data store will not contain any data. This means that after importing to a new instance, you will need to reload your data stages with the relevant data.

What should I export?

Although you can export any individual data stage, it is recommended that you export entire pipelines. This is because to properly import a data stage definition, the destination instance must contain the parents of the data stage (its pipeline and path) and any dependencies that the data stage may have.

For example, if you exported an analysis definition and then attempted to import it to another instance, the import would fail because the parent pipeline and path of the analysis do not exist in the new instance and the data stores that the analysis uses do not exist in the new instance. To remedy this, you could bundle the analysis and its data stores into a common pipeline, and then export the entire pipeline definition.