Define Relationships

Features and objects can relate to other features and objects. In Table 2 on the worksheet, identify the relationships your feature will have with other features. Note whether the feature you're currently creating is the parent (origin) or child (destination) or both (in the case of multiple relationships). If your feature or object is the parent in one or more relationships, review the Settings for Parent Features and Objects section below. For all features and objects that participate in a relationship (as parent or child), review the relationship settings section at the bottom of this page.

The image below depicts how a feature can be only a parent (FiberOpticCable), both a parent and a child (F_BufferTube) or only a child (F_Fiber).

Settings for Parent Features and Objects

Use these settings if your feature or object class acts as a parent to another (FiberOpticCable and F_BufferTube in the example above).

TIP: Using this table
  • The Example Field Name, Data Type, and Default Value columns contain values entered while creating the object. If using the worksheet, record these values in Table 5.

  • The Field Model Name column contains a value entered in the ArcFM Properties Manager on the Field Model Names tab. If using the worksheet, record the value in Table 5.

  • The Class Model Name column contains values entered in the ArcFM Properties Manager on the Model Names tab. If using the worksheet, record these values in Table 4.

Function

Settings

 

Example Field Name

Data Type

Default Value

Field Model Name

Class Model Name

One child relationship

e.g., FiberOpticCable to F_BufferTube

FiberChildClassModelName

(This is also a required field. If this field already exists, simply add the default value.)

Text

 Class model name of the child object

e.g., F_BufferTube

FIBERCHILDCLASSMODELNAME

 

Multiple child relationships

e.g., a PatchPanelCard having both FrontSidePorts and BackSidePorts

       

FIBERMULTICONTAINER

*A feature that contains connectable objects

       

FIBERDATATABLESOURCE

*Fiber Data Table Source Object

The FIBERDATATABLESOURCE model name defines the place in the hierarchy at which Connection Manager starts creating data tables. Assume, for example, you have the following relationship hierarchy. The Fiber and PretendFiber objects are both related to the BufferTube.

  • FiberOpticCable (24 count)

  • BufferTube (2 buffer tubes in each FiberOpticCable)

  • Fiber (12 fibers in each BufferTube),  PretendFiber (12 PretendFibers in each BufferTube)

If the FIBERDATATABLESOURCE model name is assigned to the FiberOpticCable, Connection Manager will create two data tables: one for all fibers under the cable and one for all PretendFibers under the cable. Now, if you move the model name to the BufferTube, you'll get the following four tables in Connection Manager.

  • BufferTube #1, Fiber

  • BufferTube #1, PretendFiber

  • BufferTube #2, Fiber

  • BufferTube #2, PretendFiber

This provides a means to logically group connectable objects under a single object in the hierarchy. If you have more than one connectable object class related to the FIBERDATATABLESOURCE object, then you will get more data tables.

The FIBERDATATABLESOURCE model name can be assigned to only ONE object in the hierarchy. It is recommended that you assign this model name to the object that contains the connectable objects.

Settings for Relationships

Use these settings if your feature or object class acts as a child to another (F_BufferTube and F_Fiber in the example above).

TIP: Using this table

The Relationship Autoupdater column contains the autoupdaters entered in the ArcFM Properties Manager tool on the Relationship Class Options tab. The Relationship Properties Fields column lists the properties that use the autoupdater. If using the worksheet, record both these values in Table 2.

Settings

 

Example Field Name

Data Type

Field Model Name

 

FiberParent

GUID

FIBERPARENT

   

FiberParentClassModelName

Text

FIBERPARENTCLASSMODELNAME

   

Function

Settings

 

Relationship Autoupdater

Relationship Properties Field

For any relationship:

The ArcFM Update Fiber Parent autoupdater uses the information stored in the ThisFiberClassModelName (on the parent and child) and the FiberParentClassModelName (on the child) fields to determine the GlobalID that needs to be placed in the FiberParent field (on the child). The FiberParent field is used as the foreign key for the relationship between the parent and child objects.

ArcFM Update Fiber Parent Field

On Relationship Created

QR Code is a registered trademark of DENSO WAVE INCORPORATED in Japan and other countries.

Was this helpful?