Skip to main content
All CollectionsScenarios
How to Update Your Scenarios Metamodel With Your Mainline Metamodel
How to Update Your Scenarios Metamodel With Your Mainline Metamodel

Learn how to keep your scenario metamodel current with the mainline metamodel so that your changes can be merged to mainline.

Kristine Marhilevica avatar
Written by Kristine Marhilevica
Updated over a week ago

In the event that your scenario metamodel is out of sync with the mainline metamodel, you will be prompted to apply the changes to your scenario metamodel.

It is necessary that your metamodels are compatible in order to:

Follow the steps below to update your scenario metamodel so it matches the mainline's. It is currently not possible to make changes to a scenario metamodel. Hence, it is not possible to update the mainline metamodel with a scenario metamodel.

To learn how to update your scenario with mainline data such as new components, references, and tags, and vice versa, follow the steps in the Scenarios data merge workflow.

Table of contents:


How To Sync Your Scenario and Mainline Metamodels

1. Open the scenario you need to update

Navigate to the Home page > Scenarios to open your scenario. You can use the search bar on the top right corner of your screen to quickly find the relevant scenario.

ardoq scenario

2. Start the merge workflow wizard

In your scenario, click on the 'Open merge workflow' button located at the top of the workspaces navigator menu. Select 'From Mainline to Scenario' to start the merge workflow wizard.

ardoq merge workflow

3. Follow the steps in the merge workflow wizard

The Metamodel merge workflow is the first step in the merge workflow. It will take you through a series of steps to replicate your mainline metamodel structure, component types, reference types, and fields in your scenario metamodel.

The merge workflow shows you where your scenario and mainline metamodels and data differ so it's easy to spot which parts of your scenario metamodel and data you need to update. 💫

In this article, we'll explain what the Metamodel merge workflow steps are. Head over here to find out more about the Data merge workflow.

ardoq reference types

Structure

The Structure step in the Metamodel merge workflow allows you to update your scenario metamodel to flexible in case your rigid mainline metamodel was converted to a flexible one.

Component Types

  • Delete component types

    In this step you will be able to delete component types in your scenario that do not longer exist in the mainline. If the component type to be deleted in your scenario is in use, it will not be possible to delete. To do so, exit the merge workflow wizard and change the component type on the components that currently have that type assigned.

    Ardoq delete component types
  • Create component types

    Bring the component types recently created in the mainline into your scenario. Please note that you will have to create the selected component types in order to continue. This is to ensure that the new components created in the Data merge workflow have the necessary types available.

    Ardoq create component types
  • Update component types

    In this step, you can choose which property value to keep for your scenario component type.

    You can choose to update the properties of your different components types with:

    • the current mainline value or

    • the current scenario value

    Ardoq update component types

    The 'Original Value' column shows the value of the element at the time you created your scenario or your last completed merge. The 'Status' column shows if there’s a conflict between the values in the mainline and the scenario. A red dot means there is a conflict because the same value changed in both the mainline and the scenario. A green dot means there is no conflict.

    You can override the preselection by either selecting everything from the mainline or from the scenario or cherry-pick the changes you want.

Reference Types

  • Delete reference types

    Remove the reference types in your scenario that no longer exist in the mainline. Similar to the process of deleting component types, the to-be deleted reference types need to be unused by your scenario components in order to delete them. In case they are in use, exit the Merge workflow and change the reference type of your scenario components to a different one.

    Ardoq delete reference types
  • Create reference types

    Select the reference types that you wish to create in your scenario and click on the 'Create selected reference types' button. It is required that the new reference types are created in advance to make sure the new references that can be created in the Data merge workflow have the necessary types available.

    Ardoq create reference types
  • Update reference types

    Choose which property value to keep for your scenario reference type.

    You can choose to update the properties of your different reference types with:

    • the original value the property had when the scenario was created or last merged or

    • the current mainline value or

    • the current scenario value

    Ardoq update reference types

    If only the source or the target has changed, the status is green, and the changed value is preselected. If both source and target have changed, the status is red, and there is no preselection. You can override the preselection by either selecting everything from the mainline or from the scenario, or cherrypick the changes you want.

Fields

  • Delete fields

    When merging fields, you can choose which fields deleted in the mainline you would like to keep, or also delete in your scenario.

    Ardoq delete fields

    Please note that if you choose to delete a field in your scenario that is already deleted in the mainline, the field and all changes made to it in your scenario will be permanently deleted.

  • Create fields

    Select the fields that you want to create in your scenarios and click on the 'Create selected fields' to proceed.

    Ardoq create fields
  • Update fields

    Choose which property value to keep for your scenario fields.

    You can choose to update the properties of your different fields with:

    • the original value the property had when the scenario was created or last merged or

    • the current mainline value or

    • the current scenario value

    Ardoq update fields

Next Steps: Sync Your Scenarios And Mainline Data

Now that your scenario and mainline metamodels are in sync, you can proceed to update your scenario with mainline data. Alternatively, if you are happy with the changes modelled in your scenario, now is time to bring your Scenarios data to the mainline. 💪 🎉

Whichever the case, the next step in the merge workflow wizard is the way to go! Learn how the Scenarios Data merge workflow works.


If you have any questions, please don't hesitate to reach out by using the in-app chat or at support@ardoq.com.

Did this answer your question?