The subnetwork name field (the UN equivalent of feeder id) isn't automatically updated, much like with feeder manager 2.0 you must run a separate command to populate the field. In this case you must run update subnetwork.
In addition to this, many customers configure their subnetworks to not update the field when in a named version (for performance reasons). You should be able to verify that the features are energized by running a subnetwork trace. The subnetwork name field (feederid) will become populated once the version is posted to SDE.Default and update subnetwork is run on SDE.Default.
