topic Re: Update subnetwork and de-energized equipment in Electric Questions

Update subnetwork and de-energized equipment

EdwardBlair — Wed, 18 Feb 2026 21:35:02 GMT

Hi -

Here's the utility network scenario: I open a fuse protecting a single phase tap on feeder ABC123. I validate and save the edit, stop editing an update the subnetwork for ABC123. The features I de-energized by opening the fuse still have a subnetwork name of ABC123, even though they are currently not part of any feeder.

What am I missing here? Or what other steps do I need to take to have the de-energized features be assigned a subnetwork of 'Unknown'.

Thanks in advance for any info.

Re: Update subnetwork and de-energized equipment

LynnMoeEsri — Wed, 18 Feb 2026 23:26:57 GMT

Hi Ed - I wonder if you are running Update Subnetwork in a version. If so, try posting your version and running Update Subnetwork in default and see if 'Unknown' is then listed in the subnetwork name field.

Re: Update subnetwork and de-energized equipment

EdwardBlair — Wed, 18 Feb 2026 23:47:35 GMT

Hi Lynn -

I *am* running Update Subnetwork in a version. I'll give the post and update in Default a try. Thanks for the suggestion!

Re: Update subnetwork and de-energized equipment

DamienPyne — Thu, 19 Feb 2026 21:09:59 GMT

We have seen this, and raised to Esri. We had been advised this is "as expected". Our workflow advises the user to use the subnetwork line to review for the update.

You should see these features IsConnected value updated, and when you run IsConnected the subnetwork should then update to unknown.

Re: Update subnetwork and de-energized equipment

EdwardBlair — Sun, 22 Feb 2026 11:56:53 GMT

This is "as expected"? Really?? Pretty confusing. I'll try the IsConnected.

Thanks much Damien for the reply.

Re: Update subnetwork and de-energized equipment

DamienPyne — Sun, 22 Feb 2026 22:36:58 GMT

I guess its similar to a load shift. You have subnetwork 1 and subnetwork 2. To update the changes of the shift where SN1 is now part of the old SN1, you need to update both SN1 and SN2. If you only update SN2, then there is a section not yet updated.

Same theory here. You have a section of network not part of that update (ie your deenergised features), and the IsConnected will clear the SN value and flag these as isconnected = False. Ie they are isolated network objects.

Re: Update subnetwork and de-energized equipment

gis_KIWI4 — Sun, 22 Feb 2026 22:46:00 GMT

@EdwardBlair - I am noticing the opposite of what you have suggested.
I have opened up a fuse. After the subnetwork update -
The fuse has the SUBNETWORKNAME field populated but all assets downstream of it have the SUBNETWORKNAME blanked out.

After "closing" the fuse and updating the subnetwork you can see the subnetwork name restored. (Ignore the "::" that an unrelated issue )

Re: Update subnetwork and de-energized equipment

MikeMillerGIS — Mon, 23 Feb 2026 19:55:07 GMT

This is as expected in a version with eventing off. This is caused by how Branch versioning works. In a version, a row only exist if it was modify. So take Eds example

1: Create Version - At this point, there are zero records with that branch ID

2: Open Fuse - This edit adds a new record to the device table with the updated attributes. The Branch ID of that row references this active version

3: Save/Validate/Update Subnetwork- Since there is only one row with this versions branch ID, this is the only record that can be updated. If Update Subnetwork were to update the affected down stream features, those edits would show up in default.

Hopefully this helps. Running a subnetwork trace will display the correct results.

Re: Update subnetwork and de-energized equipment

EdwardBlair — Mon, 23 Feb 2026 20:28:09 GMT

Mike -

Thanks for the explanation.

As you mentioned, in our experience (so far) the subnetwork trace returns expected results. Unfortunately this is also, at least initially, another source of confusion. I've got a trace telling me one thing and subnetwork name values telling me another.

Re: Update subnetwork and de-energized equipment

EdwardBlair — Mon, 23 Feb 2026 20:34:22 GMT

Well... that's what we would want. Mike Miller stated that what we see is expected behavior *in a version with eventing off*. Is it possible that you are performing the update subnetwork in SDE.Default? Or that you have eventing enabled?

Thanks for the reply!

Re: Update subnetwork and de-energized equipment

EdwardBlair — Mon, 23 Feb 2026 21:21:15 GMT

Hi @DamienPyne -

It seems like enabling "eventing" might enable the responsiveness to device status changes we now see with ArcFM Feeder Manager (in 10.x) . But it also seems there are pros and cons to this. Have you purposefully avoided enabling "eventing"?

Thx,

Re: Update subnetwork and de-energized equipment

DamienPyne — Mon, 23 Feb 2026 21:39:01 GMT

I had to go digging to confirm. Yes we have eventing off. This was not an option with UNM v3 which is where we started. Its one of those options and enhancements we did not go to when we uplifted to v6.

Re: Update subnetwork and de-energized equipment

EdwardBlair — Tue, 24 Feb 2026 00:07:39 GMT

Thank you very much.. we will have to dig into eventing and see if it will help us. Your feedback has been really helpful.