Restrictions for propagating hierarchies
Use the hierarchy propagation restrictions to ensure that your data model is propagated successfully.
Hierarchies reference other entities such as scripts within their definitions. When you propagate any type of hierarchy addition or change that contains entity references, the entities are not automatically propagated and you must manually ensure that any necessary entities are propagated.
- Adding hierarchies
- Modifying hierarchy definition is supported if the hierarchy is
not associated with a catalog.
If you try to modify a hierarchy that is associated with a catalog, the import fails and you do not receive an error message to inform you of the failure.
- Deleting a hierarchy if the hierarchy is not associated with a
catalog. Deleting a hierarchy can be propagated only through deleting
import jobs through the in the user interface.
If you try to delete a hierarchy that is associated with a catalog, the import fails and you do not receive an error message to inform you of the failure.
Renaming a hierarchy is not supported.
- Adding a category is automatically propagated.
- Deleting a category, but any items that are assigned to only this category becomes unassigned.
Renaming a category is not supported.