In this step, you'll create the necessary relationships that allow the user to create related objects to the features in the map. Before advancing to this step, you must first create all feature and object classes that participate in relationships. Use table 3 in the worksheet to determine which relationships need to be created.

Relationship autoupdaters are assigned in a later step.

Process

The steps below create a standard Fiber relationship. Your relationship may vary.

Relationship With Fiber Circuit: If you're creating a relationship with the fiber circuit, use the following settings:

Origin: F_Circuit

Destination: Your object class

Type: Simple

No messages propagated.

Cardinality: 1 - M (one to many)

Non-Attributed

Primary Key: GlobalID

Foreign Key: FiberCircuitGlobalID

This relationship does not require any ArcFM autoupdaters.

For all other relationships, follow the steps outlined below.

To create a relationship, right-click the geodatabase and select New > Relationship Class.
Give the relationship a name (e.g., Airblown_Tube) and select the Origin (e.g., Airblown) and Destination (e.g., F_Tube) tables. Click Next.
Most relationships will be Simple. Click Next.
No fiber relationships will propagate messages. Click Next.
Select a cardinality for your relationship. In this example, a single AirBlown feature can contain multiple F_Tube objects for a one-to-many (1 - M) relationship. All fiber relationships are either one-to-many or one-to-one. Many-to-many relationships are not supported. Click Next.
All fiber relationships will be non-attributed. Click Next.
In the Primary Key field, select Global ID.
In the Foreign Key field, select FiberParent. Click Next.

If you're creating a relationship to the Circuit table (e.g., F_Circuit), the foreign key should be FiberCircuitGlobalID.

Review the summary and click Finish.
Repeat these steps for each unique relationship on your worksheets. In the example below, relationships are duplicated on the worksheet because they are shared by two objects. They need to be created only once each.

Example

So far, we've used the example of Air Blown Fiber. Our sample Air Blown Fiber (Airblown) feature contains a tube (F_Tube) and that tube contains fiber strands (F_Strand). This means that AirBlown has a parent relationship with F_Tube (and object class). F_Tube has a child relationship with Airblown and a parent relationship with F_Strand (also an object class). F_Strand has a child relationship with F_Tube.

So, Table 3 for each object may look similar to the following.