In general, if you did a phase swap and the features were no longer energized, you would have a null feederid. For example, if a set of A-phase features is only energized on the A phase, and you do a phase swap to B phase, they would have a null feederid.
Is this Feeder Manager 2, or Feeder Manager 1?
The Feeder Manager Translator interprets the "ElectricTraceWeight" field, the "FeederInfo" field, and shows the "FeederID" field. However, Feeder Manager 2 does not use the FeederInfo field or the FeederID field (the FM2 field is called "Feeder IDs", plural). So if you are using FM2, the fact that it is showing a value for "FeederID" may not mean very much.
In general, look at the "Energized Phases" field with FM2. It should tell you which phases the feature is energized on. If that is null, you may want to go up to the tap point of the phase swap and see which phases IT is energized on.
Thanks for the reply.
We run 10.0 with Feeder Manager 1. I have performed several tests. In all cases, the phase swap tap point is a fuse off a three or two phase primary. The weird part is that the features trace correctly with ArcFM downstream trace, the Feeder Manager Translator displays the correct Feeder ID, but the attribute editor and the attribute table have null values for those exact same features.
Are there any known issues or problems with using the Phase Swap tool with Feeder Manager 2.0? Does it cause any issues with upstream areas or devices?
The ArcFM Update Feeder Object AU was not assigned to the OH Secondary Conductor feature class.