Cutting and Pasting Nodes
Procedure
You can also use the Cut, Copy and Paste commands to move, copy and merge nodes in the hierarchy tree. The conditions listed in the table below must be met in order to use the cut and paste operations.
When you use the Cut and Copy commands, MDM places a blinking highlight around the nodes that have been cut or copied.
Sibling nodes in a tree cannot have the same name. When you cut-and-paste a node to move it in the tree, MDM automatically renames it to Node Name (n) and when you copy-and-paste a node to copy it in the tree, MDM automatically renames it to Copy (n) of Node Name if its name would be the same as that of an existing sibling node in the new location (where ‘n’ is the first available numeric value that will avoid a conflict).
Operation |
Constraints |
Cut Node |
· Must be in Hierarchy or Taxonomy mode · Tree must have focus · Exactly one node must be selected · Root node cannot be cut |
Copy Node |
· Must be in Hierarchy or Taxonomy mode · Tree must have focus · Exactly one node must be selected · Root node cannot be copied |
Paste as Sibling |
· Must be in Hierarchy or Taxonomy mode · Tree must have focus · A node must already have been cut or copied · Exactly one node must be selected · Root node cannot have siblings · Sibling nodes cannot have the same name |
Paste as Child |
· Must be in Hierarchy or Taxonomy mode · Tree must have focus · A node must already have been cut or copied · Exactly one node must be selected · Destination node cannot be an alias · Destination node cannot have an alias · Destination node cannot have a matching set · Destination node value cannot currently be assigned to a lookup field · Sibling nodes cannot have the same name |
Paste as Merge |
· Must be in Hierarchy or Taxonomy mode · Tree must have focus · A node must already have been cut or copied · Exactly one node must be selected · Destination node cannot be the root · Destination and source node cannot be the same · Destination and source node cannot have children · Destination and source node cannot be an alias · Destination and source node cannot have a matching set · 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 node until after you attempt to perform the operation. As a result, the Paste as Child menu item is available even if the destination node has records assigned to it, even though this would make the node into a non-leaf node. If you choose Paste as Child in this situation, MDM does not permit the paste and instead displays the error dialog.