Feeder Sync Tool

Feeder Manager 2.0 leverages joined tables to track feeder information, which greatly enhances performance. However, this means the feeder information is not directly stored with the feature classes themselves, and this could inhibit your company’s third-party integrations that use those feeder fields to perform their functions. One resolution to this issue would be to run both Feeder Managers simultaneously; however, that means you would not get the performance benefit of Feeder Manager 2.0. Thus, the Feeder Sync tool is a recommended solution to both improve performance and update the Feeder Manager 1.0 fields.

The Feeder Sync tool enables you to use the functions of Feeder Manager 2.0 while continuing to update the FeederID, FeederID2, FeederInfo, and ParentCircuitSourceID fields after a user has finished editing data interactively. The tool works with both single parent sources and subsources. If there are subsources, the ParentCircuitSourceID field on the downstream features update with the CircuitSourceID field from the subsource.

IMPORTANT: Feeder Sync does not read the SubFeederID to update the ParentCircuitSourceID field on post, instead it reads the CircuitSourceID field value. SubFeederIDs and ParentCircuitSourceID are two different data types, String and Long Integer data types respectively, thus data cannot be synced across these two fields.

The Feeder Sync tool works by storing a list of edited features in the MM_EDITED_FEATURES table, and then allowing you to choose when the Feeder Manager 1.0 fields should be updated. The application can be configured to update the Feeder Manager 1.0 fields when the session is posted with a Geodatabase Manager action handler or by developing a custom feeder sync module. For a developer sample, visit the myArcFM page Synchronize Feeder Information.

IMPORTANT: If you have not already done so, you need to run Create/Update ArcFM Solution System Tables tool on your database before completing further tasks. (The tool is found on the ArcFM right-click context menu in ArcCatalog.) The Create/Update ArcFM Solution System Tables tool creates the MM_EDITED_FEATURES table that the Feeder Sync Tool uses. The MM_EDITED_FEATURES table requires the following permissions:

Table	Role	Privileges
MM_EDITED_FEATURES	MM_ADMIN	SELECT, INSERT, UPDATE, DELETE
MM_EDITED_FEATURES	MM_USER	SELECT, INSERT, UPDATE, DELETE