Assign Autoupdaters

This step requires that you assign autoupdaters to your feature classes. Autoupdaters are assigned using the Object Info tab of the ArcFM Properties Manager. If the Before Feature Split, On Feature Split, and After Feature Split fields are not visible on the Object Info tab, you are most likely working with Esri objects. Use the ArcFM Solution Object Converter to convert to ArcFM Objects. These fields will then be available.

When a Feeder Manager autoupdater is about to update a large number of features, a confirmation screen may warn the user. This functionality may be set and modified using the Feeder Manager Settings dialog.

This step may not be completed without first completing the Basic ArcFM Configuration. If you haven't yet done this, some necessary autoupdaters will not be available.

NOTE: You may notice that some feature classes have the ArcFM Delete Feeder Object autoupdater assigned and others don't. This is because these classes may affect circuit continuity and can impact the FeederID and energized phases of remaining features when they are deleted.

Autoupdaters and related unit records: Note that autoupdaters that are meant to keep attribute values synchronized between a feature and its related unit records (such as a fuse and fuse unit) must always be assigned in pairs, such that all editing possibilities are covered. While one autoupdater must be assigned to the OnUpdate event for the feature class (or else for the unit object class, if the desired propagation direction is from unit to feature), a second autoupdater must be assigned to the OnRelationshipCreated and OnRelationshipDeleted events on the relationship class that joins the features to their units.

QR code for this page

Was this helpful?