Import behaviors
When importing packages using the import/export functionality, the behavior of the imported elements might vary according to their type.
Export profiles
The following table describes the merge behaviors when importing export profiles.
| Exported export profile | Behavior |
|---|---|
| Duplicated profile | The profile is overwritten. |
| New profile | The profile is created. |
| Existing profile | The profile remains unchanged |
Settings
The following table indicates the overwritten settings when importing them using an export package.
| Setting | Overwritten |
|---|---|
| Users | Yes |
| Renditions | Yes |
| Composite assets | Yes |
| Chili | Yes |
| Portal configuration | No |
| Drafts | Yes |
| Integration | Yes |
| Excel import/export | Yes |
| DRM | Yes |
| System-owned settings | No |
Option lists
The option lists imported from the export package overwrite the option lists in the import instance.
Taxonomies
The id number of an exported taxonomy remains the same in both source (export) and destination (import) environments. However, the id of taxonomy elements in the destination environment are different from those in the source environment.
In the following example, you can see that in the source, Province-Leinster has an id of 9690, but after the import into the destination, it has an id of 9735.
| Taxonomy element Id before import | Taxonomy element Id after import |
|---|---|
The following table describes the merge behaviors when importing taxonomies.
| If the imported taxonomy | Merge behavior |
|---|---|
| Does not exist in the destination instance. | The new taxonomy is created. |
| Exists in the destination instance, but has different children elements than the existing taxonomy. | The children elements are combined. |
| Exists in the destination instance, and has a child element identical to the existing taxonomy, but different or no grand-children elements. | The imported taxonomy element overwrites the existing one. |
Can we improve this article ? Provide feedback