topic Re: Update subnetwork not updating supported subnetwork name on a Electric Assembly feature in ArcGIS Utility Network Questions

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

YulissaCamacho — Sun, 18 Jan 2026 21:15:02 GMT

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?

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

RobertKrisher — Sun, 18 Jan 2026 23:37:32 GMT

Are you doing this in a named version or default? What are the edit mode configurations for the subnetwork definition for the subnetwork you're updating?

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

YulissaCamacho — Mon, 19 Jan 2026 00:28:31 GMT

This happend both in default and named version

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

gis_KIWI4 — Mon, 19 Jan 2026 01:03:33 GMT

Are all the contents of the assembly correctly updated to Unknown after disconnecting? Just wondering if there is some content that might stopping it from updating.

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

YulissaCamacho — Mon, 19 Jan 2026 01:14:47 GMT

Yes, the transformer devices that are content and the pole that is attached are updated to Unknown

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

RobertKrisher — Mon, 19 Jan 2026 14:28:37 GMT

Please log an issue with support. If your subnetworks are configured to populate the subnetworkname field on assemblies, then it should also set it to unknown when their content is no longer supported.

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

RobertKrisher — Wed, 25 Feb 2026 14:47:37 GMT

Following up on this. It turns out it was a bug.

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

JordanScupien — Thu, 30 Apr 2026 20:45:09 GMT

Robert,

Is there a workaround for this bug? Im experiencing this in Gas and water isolation traces

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

RobertKrisher — Thu, 30 Apr 2026 20:50:20 GMT

The bug only occurs on update subnetwork, so I'm not sure it applies to isolation traces. Can you explain?

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

JordanScupien — Fri, 01 May 2026 14:03:12 GMT

I have 2 different issues Im working on my apologies. The 1st is 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.

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

JordanScupien — Fri, 01 May 2026 14:06:27 GMT

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.

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

RobertKrisher — Fri, 01 May 2026 16:17:52 GMT

@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).