Select to view content in your preferred language

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

578
11
Jump to solution
01-18-2026 01:15 PM
YulissaCamacho
Emerging Contributor

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?

0 Kudos
1 Solution

Accepted Solutions
RobertKrisher
Esri Regular Contributor

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

View solution in original post

0 Kudos
11 Replies
RobertKrisher
Esri Regular Contributor

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?

0 Kudos
YulissaCamacho
Emerging Contributor

This happend both in default and named version

YulissaCamacho_0-1768782470408.png

 

0 Kudos
gis_KIWI4
MVP Regular Contributor

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. 

0 Kudos
YulissaCamacho
Emerging Contributor

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

0 Kudos
RobertKrisher
Esri Regular Contributor

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.

0 Kudos
RobertKrisher
Esri Regular Contributor

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

0 Kudos
JordanScupien
Emerging Contributor

Robert,

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

 

0 Kudos
RobertKrisher
Esri Regular Contributor

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

0 Kudos
JordanScupien
Emerging Contributor

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.

0 Kudos