F_DevicePoint_Device

Commonly, a device is related to a patch location. In addition, a device may also be related to a device feature class. In other words, there can be a feature class called device which has a geography on the map, and that feature class has a related device in it. To differentiate between the two, the sample data uses the name “DevicePoint” for the feature class and the name “F_Device” for the object table. The way the application understands the difference is by the model name assignments: device feature classes need the class model name ENDDEVICEPOINT, while device object tables need the class model name ENDDEVICE.

Thus, this is the relationship for the feature class (DevicePoint) to object table (F_Device).

You can find existing relationships and create new ones in ArcCatalog. Almost all relationships are found at the geodatabase level, as opposed to the dataset level. Below is an image of the final properties for this relationship. For more information about these settings, see the relationship topic Summary of Recommendations.

Because this is a parent/child relationship, it requires the following autoupdater set at the relationship itself:

  • On Relationship Created: ArcFM Update Fiber Parent Field

  • On Relationship Deleted: <None>

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

Was this helpful?