2.7.3.9. Merge Leaf Clusters

Purpose

They merge the parts of a populated sheet cluster with another populated sheet cluster if both describe the same grouping. After its parts have been transferred, the source sheet is removed; the destination sheet remains as the updated result.

Requirements

Log in using "clustering-view" and "clustering-edit".
Open a completed, saved clustering with two different leaf clusters. The intended target must already contain some parts.
Make sure that no part from the source sheet is in the "Clipboard" and that its parts are not locked by another editing operation .

Procedure

In the cluster tree, drag a source leaf node onto another, populated destination leaf node to start the merge. This drop action within the tree means merging, not reassigning. The source leaf is the cluster that is removed; the destination leaf remains intact. The merge dialog describes the transfer of parts and the deletion process before any changes are applied.

The source leaf [1] and the filled destination leaf in the tree [3] are the two nodes used when inserting an element into the tree.

In the confirmation dialog, specify the name of the destination. The description indicates which source is being removed and which destination will receive its parts. The default is the destination's current name.

The dialog box displays the source and destination, shows the editable name of the destination [1], and offers the options "Merge" [2] and "Cancel" [3].

After the merge, the application reloads the relevant result and selects the resulting target. The target map, tree, and "Overview" show the changed distribution of the clusters.

The target cluster obtained [1], the selected node in the tree [2], and the updated “Overview” [3] form the context for the next decision.

Options and Decisions in Operations

Merge Sheets – Source, Destination, and Confirmation

Control element or State	Operating Instructions
Source leaf node in the cluster tree	Drag this leaf node onto the target leaf node. It will release all of its parts and be removed upon completion; use it only if it is no longer needed as a separate cluster.
Filled target leaf node in the cluster tree	The target of the drop operation retains its position in the hierarchy and receives the parts from the source. It must be another filled leaf, because dropping onto an empty node is a reallocation within the structure, not a merge.
Name of the merged cluster	The default is the current name of the destination. Keep it if it still works; replace it if the merged parts need a clearer name . A changed value renames the resulting destination after the parts have been transferred and the source has been deleted .
"Merge"	Perform the process in this order: Transfer parts of the source, remove the source sheet, and, if specified, apply the changed name of the destination.
"Cancel"	Closes the confirmation without transferring any parts, deleting the source, or changing the name of the destination .
"Clipboard"	Merging is disabled if "Clipboard" contains a part from the source sheet. Release these parts or assign them before attempting to merge again.
Tree, Target Card, and "Overview"	Display the newly loaded, saved result. This shows you which sheet remains selected, which parts the target contains, and how many clusters there are now.
Error during merging	Specify the step that could not be completed. If a previous step has already modified data, the workspace reloads the server state before displaying the error, so that further work is based on the current result.

Result

The target sheet retains its position in the hierarchy and contains the parts from both clusters. The source sheet no longer exists after the merge. The name of the resulting target represents the merged group during subsequent reviews, status updates, exports, and further maintenance of the tree.

Tips and Troubleshooting

A source sheet whose parts are in the "Clipboard" cannot be merged. First, resolve the parts that are being held back.
Merging sheets requires editing permissions. Users without the "clustering-edit" permission can view the result but cannot perform this structural change.
If the parts of the source have been moved, but a subsequent step to delete or rename them fails, check the newly loaded result and the reported error before deciding on further cleanup.

Prev	Up	Next
2.7.3.8.3. Delete Nodes and Remove Layers	Home	2.7.3.10. Simultaneous Editing and Recovery Check