Reporting Conflicting Revisions in a Model Version Hierarchy

You can generate a Conflicting Revisions in Model Version Hierarchy report to identify instances where two different revisions of the same model version exist in the model version hierarchy.

Note: The Conflicting Revisions in Model Version Hierarchy report is generated by scanning the model version hierarchy from the selected model version revision downwards. It cannot identify instances where the selected model version revision also exists at a higher level in a model version hierarchy.

Required access roles:

  • App-specific: Defect Engineer
  • Baseline: Owner

Before you begin: Open the Model Version Hierarchy page for the model version. See Model Version Hierarchy Page.
See Also
Importing a DesignSync Module Hierarchy as a Model Version Hierarchy
Creating a Hierarchical Reference
About Model Version Revision Hierarchies
From the toolbar, select Actions > Report Conflicting Revisions.
  • If there are no conflicting revisions, the message No conflicting revisions found in model version Hierarchy is displayed. Click OK to close the message.
  • If there are conflicting revisions, for example if there were two different versions of RAM used in the CPU and the ALU, the Conflicting Revisions in Model Version Hierarchy window opens.
    Column NameDescription
    Path to Conflicting RevisionThe path to the conflicting revision.
    First Found AtThe location where the first instance of the conflicting revision was found

The conflict report runs from the selected model version revision downwards through the model version hierarchy. It does not scan up the hierarchy. For example, a model version PACKAGE could reference CHIP A and could also reference RAM C. When generated for CHIP A, the Conflicting Revisions report will not find a conflict.