Content ID assignment
When you run an import deployment, you can choose how to assign content IDs for objects in the content store.
Objects in the content store have content IDs that are deleted and replaced with new IDs by default when you run an import deployment and move content to a target environment. However, there may be situations when you must preserve content IDs, for example, when archiving report output to an external report repository. If so, you can choose to preserve content IDs when you run the import. For more information about how to assign IDs when importing objects, see Run an Import.
Preserving content IDs can be applied to a partial deployment or a deployment of the entire content store.
Content ID conflicts
When you retain existing content IDs, conflicts can occur on import. Here are the conflict situations that can occur.
Information |
Details |
---|---|
Description |
When an imported object exists in the target environment in a different location but with an matching content ID, the ID is not preserved on import but replaced with a newly generated ID. The object that exists in the target environment could be another version of the same object or it could be a completely different object. |
Warning |
A warning message will describe that the content was not preserved and, if the security privileges allow, will identify which object in the target environment is in conflict. No information is issued about how to resolve the conflict. |
Resolution |
To resolve any content ID conflicts, you can
|
Information |
Details |
---|---|
Description |
When an imported object exists in the target environment in a same location but with a different content ID, the ID will be preserved on import and will replace the existing ID in the target environment. |
Warning |
No warning message is issued. |
Resolution |
Note that all existing external references to the target content ID, if any, are permanently lost when the content ID is replaced. |