Hello,
I have a hierarchical List & Vocabulary structure where items were originally assigned identifiers (idno) based on their position in the tree:
item_1
item_1_1
item_1_1_1
item_1_1_2
item_2
I need to relocate item_1_1 so it becomes a child of item_2. Moving this element will naturally relocate its entire sub-tree (item_1_1_1, item_1_1_2, etc.) along with it.
To keep the identifier naming convention consistent with the new hierarchy, I want to update the idno of the parent element (from item_1_1 to item_2_1) and sequentially rename its children (item_2_1_1, item_2_1_2, etc.).
When editing the idno, Providence shows the standard warning: "Changing this value may break parts of the system configuration."
I suppose I could create the new elements under item_2 and then delete the former and transfer references to the new elements. However, this may be slow and risky.
Since internal relationships (like cataloged objects linked to these list items) rely on internal item_id primary keys rather than the idno string, I would like to clarify:
- As long as these specific
idno strings are not hardcoded in any XML user interface screens, installation profile settings, or display templates, is it completely safe to rename the idno for the entire relocated branch?
- Is directly renaming each
idno in the branch the best approach, or is there any risk to search indexing/caching that requires running a CLI command like reindex or clear-cache afterwards?
Thanks in advance for your help!
