Update subnetwork not updating supported subnetwork name on a Electric Assembly feature

[YulissaCamacho]

Hi. Our team find a problem with a electric utility network that we are using, when we de-energized some part of a subnet, everything downstream change the subnetwork name to "Unknown" but no the transformer bank that we set as a Electric Assembly. After running update subnetwork the supported subnetwork field keep the name of the subnet, even though the transformer electric device and the pole that the bank has associated with don't have subnetwork name.

We have the  Include Containers in the trace configuration options check with the Include Structure Network Containers and Include Domain Network Containers in the tier's subnetwork definition.

Any ideas?

[JordanScupien]

I am exporting subnetwork controllers from a oracle database to a SQL database.  After importing the controllers all the water subnetworks come in perfectly---but once I use the update the subnetworks tool the pressure subnetworks disappear and come in as unknown.  The controllers and linework are the same in both databases.

[RobertKrisher]

@JordanScupien this is a completely different issue and should really be its own thread. If my advice here doesn't solve your problem, please start a separate discussion. I'm not sure how you got your DATA from one environment to the other, but it sounds like the lines aren't connected to the correct terminals on your subnetwork controllers. The only way you will not get ANY pressure line features in your subnetwork is if there aren't any lines connected to the terminal of your subnetwork controller. If you only get the first line, then there is a problem with your condition barriers (on either your controller or the device).