Re-adding diagram to the Repository without losing EDD

There are situations where a diagram needs to be removed and re-added to the same Repository. For example, to fix a corrupted Repository entry, rename the diagram, or resolve a persistent check-in failure. The steps differ depending on whether the diagram uses an Enterprise Data Dictionary (EDD) or not.

• If no EDD is used: Doing a Save As + Add Diagram is all that is needed.
• With EDD: The EDD already exists in the Repository, so it must be bound (not re-created) when adding the diagram back, and bindings must be restored via Compare and Merge.

Case 1 – Re-adding a Diagram with No EDD

This is the straightforward case. The diagram uses only a Local Data Dictionary (or no Data Dictionary at all).

Steps

1. Retrieve a local copy of the dm1 file from the Repository or use an existing local copy.
2. Go to File > Save As and save the file to a new name and/or location. Filenames must be unique in the Repository, so don’t reuse the same name if adding back to the same Repo.
3. Make sure you are logged in to the Repository.
4. Go to Repository > Add Diagram and add the newly saved dm1 file.
5. Complete the Add Diagram dialog as normal.

The diagram is now re-added. No additional steps are required.

Case 2 – Re-adding a Diagram That Uses an Enterprise Data Dictionary (EDD)

The EDD already exists in the Repository from a previous diagram. The goal is to re-add this diagram and bind it to that existing EDD not create a new one then restore all the object bindings (attachments, domains, etc.) via Compare and Merge.

Steps

Prepare the file

1. Retrieve a copy of the dm1 file from the Repository or update your local copy with the latest version.
2. Go to File > Save As and save the file to a new name and/or location. Do not overwrite the original. It will be needed in later steps as the merge source. Note: The Save As will remove all EDD objects and their bindings to model objects. Those bindings will be restored later in these steps.

Add the diagram and bind the EDD to it

1. Make sure you are logged in to the Repository.
2. Go to Repository > Add Diagram to open the Add Diagram dialog.
3. In the Bind Enterprise Data Dictionary section of the dialog, select the existing EDD.
4. Complete the Add Diagram dialog to finish adding the diagram.

Restore bindings via Compare and Merge

1. Once the file is added, check out:
   • The Diagram
   • The Enterprise Data Dictionary
   • The Local Data Dictionary
2. Switch to the Logical Main Model and open the Compare/Merge wizard.
3. On Page 1, choose Compare against another model in a DM1.
4. Click the ‘...‘ button and select the original dm1 file from Step 1 (the backup copy, not the Save As copy).
5. Click Next and select the Logical Main Model on the following page.Note: The application may warn that the target model is not checked out. Ignore these warnings — you are reading from the original file, not modifying it.
6. Click through the wizard to the results page and review the differences. Since this is the same model, the only differences should be bindings to Data Dictionary objects (attachments, domains, etc.).
7. Click Merge All into Current, then Finish to apply the bindings to the new copy of the diagram.
8. Verify a couple objects to make sure they are correctly bound to objects in the Enterprise Data Dictionary.
9. Repeat steps 8–14 for each Physical model in the dm1 file, selecting that physical model instead of the Logical Main Model when starting the Compare/Merge and on page 2 when selecting from the original model.

Check in

1. Check in the Diagram.Note: The data dictionaries should not have changed during this process. After checking in the diagram you can undo the check out of the data dictionaries.

The diagram is now re-added to the same Repository with the EDD bound and all bindings restored.

Important Notes

• Always Save As before proceeding. The original dm1 file is used as the merge source in Case 2. Overwriting it before the merge will make it impossible to restore the bindings.
• Check out all three objects (Diagram, EDD, Local DD) before running Compare and Merge. Attempting the merge without checkout will result in warnings and the merge may not apply cleanly.
• Repeat Compare/Merge for every physical model. Bindings exist at the physical model level as well as the logical level. Missing a physical model will leave column-level bindings (e.g., domain assignments) unrestored.
• If the original diagram had objects in both a Local DD and an EDD, verify after the merge that local DD objects have not been unintentionally merged into the EDD. Additional cleanup may be needed in that case.

Where This Differs from EDD Migration