Update subnetwork and de-energized equipment

[EdwardBlair]

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.

Ed

[EdwardBlair]

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

[MikeMillerGIS]

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.  

[EdwardBlair]

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.

Ed