Handling Missing Attributes of Assets When Importing
It is possible that an asset type definition in the source registry is different from an asset type definition with the same name in the target registry. for example, this may happen when the asset type in the target registry represents an updated version of the asset type with different attribute definitions. If an asset type has an attribute that is required in the target registry but not in the source registry, then a mismatch occurs.
CentraSite handles this situation on the target registry depending on the attribute type, that is:
If the attribute type is one that has a default value, such as
slot or
classification,
CentraSite assigns the default value to the attribute when the asset is imported.
If the attribute type is one that does not have a default value, for example, an attribute type that represents a file name or relationship, an error occurs during the import of the archive because the target registry requires a value for the attribute. Hence, the affected asset is not imported and the import log contains appropriate error messages. In such cases, you need to ensure that a value is supplied for the attribute before the asset is exported from the source registry.
