Restrictions for propagating attribute collections
Use the attribute collection propagation restrictions to ensure that your data model is propagated successfully.
Attribute collections are groups of item or category attributes that, in a context, are associated and behave the same way.
When you propagate attribute collection changes, be aware of any additional attributes or specs that are dependant of primary or secondary spec changes and ensure that the primary or secondary spec changes are propagated at the same time.
Primary or secondary specs that have identical attribute collections on both the source and target instances are automatically propagated.
Primary or secondary specs that do not have identical attribute collections on both the source and target instances, the source and target instances are not synchronized because the target instance receives objects that did not exist before propagation. For objects that have the same names as objects that exist in the target instance, the import fails.
- Adding an attribute collection
- Modifying attribute collection attributes
- Deleting an attribute collection if the attribute collection is not associated to a catalog or collaboration area. Deleting an attribute can be propagated only through deleting import jobs through the in the user interface.
If you try to delete an attribute collection that is linked to a catalog or workflow, the import fails and you do not receive an error message to inform you of the failure.
Attribute renaming is not supported.