Export and Publish Content
| Content exchange is an experimental feature: it is currently available only in selected environments and might change in future releases. |
Create a content package from selected assets and publish it to designated environments for import. This is a key step in content exchange as it lets you control not only what gets exported but also where it can be imported.
Prerequisites
-
Review how content exchange works.
-
You have the following identity provider roles:
-
contentorchestrator-export-operator: Required for creating exports.
-
contentorchestrator-promotion-publisher: Required for publishing packages to other environments.
-
-
You have prepared the environments between which you want to promote assets, as described in Set Up Content Exchange.
Create an export
To create an export from the source environment:
-
Go to Global settings > Content exchange > Exports.
To access Global settings, select the Ataccama logo. -
Select New export.
-
Enter a Name for the export.
-
Under Assets to promote, select which area of the platform to export from. Currently, only Reference data is available.
-
Select the Apply mode: Draft or Published. For the Draft mode, also select the Promotion scope: Structure or Data.
-
Select which assets to export.
-
Select all tables that apply. For each table, select also Structure and Data as applicable.
-
Select all hierarchies that apply. This is available only if the Published apply mode is used.
-
-
Select Next.
-
Configure how conflicts are resolved on import. See Conflict handling for reference data.
-
Select Next.
-
Review your selection and select Export to create the content package.
In Eligible target environments, you can see which environments the package can be later published to, based on the current promotion settings.
The package is built in the background. Track its progress on the Recent exports tab. For details about what each status means, see Export statuses.
Apply modes for reference data
The exported content is always the published state of the assets. The apply mode determines the state in which they are imported into the target environment:
-
Draft: All assets are imported as drafts and need to be reviewed and approved for publishing in the target environment. In this case, you also need to select the Promotion scope: Structure or Data, as a draft package can carry only one content type.
-
Published: All assets are imported as published in the target environment, with no additional approval needed. A published package can carry any combination of content types.
Effective dates are not available for export in the Draft mode because enabling them is part of publishing.
Conflict handling for reference data
The apply settings define what happens when the package meets existing assets in a target environment. They are stored in the package and cannot be changed at import time.
When importing a package into a target environment, assets are handled as follows:
-
New assets (those that don’t exist in the target environment) are always imported.
-
Assets that already exist in the target environment are left as they are. Whether an asset already exists is decided by its identifier, not by its name or values. See How assets are matched.
You can choose how conflicts are handled for each asset category.
Structure changes
The incoming table structure is applied as follows:
-
Overwrite: Create missing definitions and update changed ones. The structure is fully matched. Attribute names and data types are updated to match the package, attributes and relationships that exist only in the target environment are removed, and the remaining columns are reordered to match the package.
-
Additive: Create missing definitions and leave existing ones untouched, including their names and data types. New attributes are appended after the existing ones, and no column is reordered.
Table names are not updated in either mode. A table renamed in the source environment keeps its current name in the target environment.
Data changes
When the target’s published records differ from the incoming ones, conflicts are handled as follows:
-
Overwrite: Update the matching target records with the incoming ones. In the Draft mode, the data is imported in the draft state instead.
-
Skip: Keep the published target data.
Target-only data
Records that are published in the target environment but are not in the package are handled as follows:
-
Keep: Leave them unchanged. Any new records are imported as usual.
-
Delete: Remove them from the target environment. This covers every record that the source table didn’t have at the time of export, including ones added directly in the target environment or loaded from a file. In the Draft mode, assets are imported as drafts marked for deletion instead.
This setting applies only to records that are missing from the package. Records the package adds are always imported, and records that appear in both the package and the target table follow the Data changes setting.
Relationships that can’t be resolved
Plan the package so that every promoted relationship can be resolved in the target environment. An import is not blocked when a relationship can’t be resolved, and the rest of the package is applied either way:
-
If the referenced table or column is missing in the target environment, or exists only as a draft, the relationship fails and the import reports as Failed.
-
If a referencing value has no match in the referenced table, the record is imported with an empty reference cell and the import still succeeds.
Export statuses
The Recent exports tab shows each export with its current status:
-
Exporting: The selected assets are being exported.
-
Packaging: The content package is being built from the exported assets.
-
Ready: The package is ready and can be published to other environments.
-
Cleaning: The export failed and its temporary data is being cleaned up.
-
Failed: The export failed and no package was produced. Create a new export to try again.
Publish a package to an environment
Publishing makes a content package available for import into other environments within your organization. You can only publish exports in the Ready status.
To publish a package:
-
Go to Global settings > Content exchange > Exports.
-
In the three-dot menu of the export, select Publish to environment.
-
In Available for, select the environments where the package can be imported. Only environments whose promotion settings are compatible with this package are shown.
-
Select Publish.
You can now import the package into another environment. See Import Content.
Withdraw a package from an environment
Withdrawing a package makes it unavailable for import in a specific environment. The package itself is not deleted and stays available to the other selected environments.
To withdraw a package, from the export three-dot menu, select Publish to environment. In Available for, clear the environments as needed and select Publish.
Next steps
-
Import Content — Import the published package in the target environment.
Was this page useful?