RFCoupler_RFCouplerPort

There are two versions of this relationship:

RFCoupler_RFCouplerPort for the as-built representation.
RFCoupler_RFCouplerPort_D for the in-design representation.

As stated in the previous topic Relationships, this topic contains step-by-step instructions on how to create the relationships in ArcCatalog. Subsequent relationship topics only include the relevant properties to choose while building the relationship.

In ArcCatalog, right-click the DHFC geodatabase and choose New > Relationship Class.
For Name, type RFCoupler_RFCouplerPort.
For Origin table/feature class, choose RFCoupler.
For Destination table/feature class, choose RFCouplerPort.
Click Next.
For Relationship Type, choose Simple, then click Next.
Regarding the Forward Label, it must match the label in the Schema.xml. If using the default values:
1. For the Forward Label, type RFCouplerPort
2. For the Backward Label, type RFCoupler
3. For the Message Direction, choose None (no message propagated)
  IMPORTANT: The Forward Label you type while creating the relationship must match the EsriBuiltName entry in the Schema.xml file for this component:
```
<Relationship CoaxName="RFCouplerPortData" EsriDesignName="SECom.ARCFM.RFCouplerPort" EsriBuiltName="RFCouplerPort" />
```
  See the topic Relationship Labels and the Schema.xml for more information.
4. Click Next.
For Cardinality, choose 1–M (one to many), then click Next.
For Relationship Attributes, choose No, I do not want to add attributes to this relationship class, then click Next.

IMPORTANT: RFCoupler_RFCouplerPort does not require an attributed relationship, but other relationships do. Each feature’s relationship help topic notes whether or not to choose attributed and which fields to add to the relationship table.
For the Primary Key, choose NetworkId.
For the Foreign Key, choose CouplerId.
Click Next.
Review the summary, then click Finish.

IMPORTANT: With the as-built relationship complete, you can repeat the steps to create the in-design relationship. Ensure you relate the in-design components together (the ones with the suffix _D) and ensure you change the Forward label to match the Schema.xml, as described in the steps below.
In ArcCatalog, right-click the DHFC geodatabase and choose New > Relationship Class.
For Name, type RFCoupler_RFCouplerPort_D.
For Origin table/feature class, choose RFCoupler_D.
For Destination table/feature class, choose RFCouplerPort_D.
Click Next.
For Relationship Type, choose Simple, then click Next.
Regarding the Forward Label, it must match the label in the Schema.xml. If using the default values:
1. For the Forward Label, type SECom.ARCFM.RFCouplerPort
2. For the Backward Label, type SECom.ARCFM.RFCoupler
3. For the Message Direction, choose None (no message propagated)
  IMPORTANT: The Forward Label you type while creating the relationship must match the EsriDesignName entry in the Schema.xml file for this component:
```
<Relationship CoaxName="RFCouplerPortData" EsriDesignName="SECom.ARCFM.RFCouplerPort" EsriBuiltName="RFCouplerPort" />
```
  See the topic Relationship Labels and the Schema.xml for more information.
4. Click Next.
For Cardinality, choose 1–M (one to many), then click Next.
For Relationship Attributes, choose No, I do not want to add attributes to this relationship class, then click Next.

IMPORTANT: RFCoupler_RFCouplerPort_D does not require an attributed relationship, but other relationships do. Each feature’s relationship help topic notes whether or not to choose attributed and which fields to add to the relationship table.
For the Primary Key, choose NetworkId.
For the Foreign Key, choose CouplerId.
Click Next.
Review the summary, then click Finish.