Merge objects

Note: The Merge option is only available for Sources and Hierarchies. Sources and Hierarchies are part of the Repository metadata type. You can merge Repository and Saved Expression objects targeting the same source and same target space selection in one merge workflow.

Caution:

Merge and its features (for Compare and Merge) must be enabled at an account level. The default setting for Merge is disabled for all users. Work with your system administrator for more information.

Merge compares the prod repositories for each space, if you merge from one space to another without publishing new changes, you will not see the merge reflected in compare.

Merge does not copy any data from source space to target space. Extraction of data and publishing are required.

After comparing your objects, select the check box next to each item you would like to merge from the source to the target.
The selected item and dependent objects are displayed on the Merge List. Merge automatically identifies one level of dependencies but a second and third level of dependency analysis can be run for more complex models. This ensures that you can identify all the dependencies. To check if a specific object has additional dependencies, click the Load Additional Dependencies button for the object you want to analyze from the list.
Click Create Merge Workflow. A new workflow is created.
From Orchestration, you can click Actions to Run Workflow or use Scheduling to schedule the workflow. Workflows created through the merge action can't be modified to add or remove tasks or steps. Only the name and description of the workflow can be edited.

Note: You can select a merge workflow in Orchestration to display the Merge List panel and view the objects included in the merge workflow.