Adding a Node 

Procedure

To add a new sibling or child node to the hierarchy tree:

       1.      In the hierarchy tree, select the node either: (1) after which you want the new node to appear as a sibling; or (2) under which you want the new node to appear as a child.

       2.      Right-click on the node and choose from the context menu, or choose Tree from the main menu and choose from the main menu, as follows:

¡        Add Sibling

¡        Add Child

       3.      In the Record Detail pane, enter information for the new node.

       4.      Press SHIFT + ENTERor right-click and choose Save Recordto save the details of the new node.

       5.      MDM adds the new node either: (1) as a sibling of and just after the selected node in the hierarchy tree; or (2) as the last child of the selected node in the hierarchy tree.

MDM does not add the new node to the tree until you have saved its details in the Record Detail pane.

Operation	Constraints
Add Sibling	·        Must be in Hierarchy or Taxonomy mode ·        Tree must have focus ·        Exactly one node must be selected ·        Root node cannot have siblings ·        Sibling nodes cannot have the same name
Add Child	·        Must be in Hierarchy or Taxonomy mode ·        Tree must have focus ·        Exactly one node must be selected ·        Node cannot be an alias ·        Node cannot have an alias ·        Node cannot have a matching set ·        Node value cannot currently be assigned to a lookup field ·        Sibling nodes cannot have the same name

For proper organization of the records within an MDM repository, a hierarchy lookup field can normally be assigned only to the value of a leaf node in the hierarchy table, which can sometimes prevent a tree operation that would otherwise turn a leaf node into a parent node. However, MDM does not detect if records have already been assigned to a leaf node value until after you attempt to perform the operation. As a result, the Add Child menu item is available even if the selected node value has records assigned to it, even though this would turn it into a non-leaf node. If you choose Add Child in this situation, MDM does not allow it and instead displays an error dialog.