Conduit Manager Step 3: Create Relationship Classes

The following relationship classes must be created in your geodatabase as part of Conduit Manager's minimum configuration requirements.

Conduit_CrossSectionAnnotation

Origin table	Conduit feature class
Destination table:	Cross Section Annotation feature class
Relationship type:	Composite (when conduit is deleted, associated annotation is deleted)
Notification:	None (no generated messages)
Cardinality:	One to Many
Primary Key:	ObjectID of the Conduit
Foreign Key:	FeatureID

Conduit_Conductors

Create a relationship between each conductor (or cable) class and the conduit feature class. For example, Conduit_PriUGElectricLineSegment.

Origin table:	Conduit feature class
Destination table:	Conductor (Cable) feature class
Relationship type:	Simple
Cardinality:	Many to Many
Attributed Relationship
Add fields:	ULS_Position (long integer), PhaseDesignation (long integer)
Origin (Conduit) Primary Key:	ObjectID
Destination (Conductor/Cable) Primary Key:	ObjectID
Conduit Foreign Key:	ULSObjectID
Conductor (Cable) Foreign Key:	UGObjectID

Currently the ULS_Position and PhaseDesignation fields must be named exactly as shown here. Model Name support is not available for attributed relationships. The Conduit Foreign Key and Conductor (Cable) Foreign Key fields must also be entered exactly as show above. Failure to enter this as documented will result in errors.