Creating a report of incomplete relationships in the loaded as-built data - HxGN SDx - Update 61 - Help - Hexagon

After you have loaded the as-built handover data and before you can start project work, you need to check for dangling relationships. A dangling relationship is where the object on one end of the relationship was loaded, but the object on the other end of the relationship can't be found. This can happen for a number of reasons, such as:

• An error occurred in SDx that prevented the missing object from being published properly from Smart 3D.

• The missing object was not included in the Smart 3D database and was, therefore, not published.

• The mapping between the object in Smart 3D and SDx was incorrect.

If the dangling relationships are not resolved before the project work begins, you could encounter issues with claiming, releasing claimed objects, and merging data.

The following section explains how to create a report of dangling relationships.

Generating the Missing Relationships report

The report, created using the following steps, allows you to view all the dangling relationships found in a plant, a project, or a change action. Once the information is gathered in the report, you can use the information to correct the issues in Smart 3D and update SDx or delete the relationship completely.

1. Find the plant, project, or change action you want to create a report for:

   • From the System Administration feature set, click Plant Breakdown Structure, and query for the plant.

   • From the Business Administration feature set, click Projects, and query for the project.

   • From the Change Management feature set, click Change Action and query for the change action.

2. From the plant, project, or change action, click Actions > View Missing Relationships.

You can use the Export to Excel option to transfer the data results of the report to a Microsoft Excel spreadsheet to make it easier to share with others.

Understanding the Missing Relationships report

The report that results from the steps above includes information to help you investigate the issue:

• The name of the End 1 object.

• The name of the End 2 object.

• The name of the type of relationship that should exist between those two objects.

• An Indicator to let you know which object is missing (End 1 or End 2).

• The domain that the relationship belongs to.

• The SDx configuration where the objects and relationship should exist.

• The change action that the relationship belongs to (when the report is run from a change action only).

This report supports filtering and sorting like other list views in SDx.