Common dependencies between objects
Any Content Engine object that you can add to the export manifest in Enterprise Manager is dependent on the class definition, properties, and property templates that were used to create the object. This dependency means that the class definition and property template must exist in the destination environment for the object to be functional.
Typically, a dependent object references the object it requires by ID rather than by name. Therefore, when you import the required object you must ensure that it has the same object ID in the destination environment. It is not sufficient for the required object to be in the same folder path and have the same content and property values if the ID is different.
Use one of the following strategies to ensure the successful import of a dependent object:
- Have the required object in the destination object store before you begin the import operation for the dependent object.
- Use the same import operation to import both objects, but ensure that the required object is processed before the dependent object. Look at the export files to determine the order in which the objects will be imported. The manifest file lists the export files in the order they will be processed. Each export file lists the objects in the order they will be processed.
- When you run Import Helper, select the Retry Failed Imports option. If the dependent object is processed first, Enterprise Manager generates a “required object does not exist” error, but continues processing and at some point creates the required object. On the second pass, Enterprise Manager creates the dependent object and generates a “duplicate object error” for the required object. You can ignore both errors.