Update Subnetwork GP Tool showing Subnetworks that aren't dirty

JakeJacobs

I'm wondering if this is as-designed or if there's an existing bug for this.

When using the Update Subnetwork GP tool in ArcGIS Pro 3.3.5 with UN 7 (Enterprise 11.3), I noticed that there were subnetworks listed in the drop-down as available to be updated that weren't actually dirty.  When I checked what the query was in the Monitor, it was DOMAINNETWORKNAME = N'Pipeline' AND TIERNAME = N'Isolation' AND ISDIRTY = 1.  Checking, I realized that the listed subnetworks had Subnetwork Controllers that had been deleted and has ISDIRTY = 1. The current subnetwork controllers for those subnetworks were all ISDIRTY  = 0

Would it make more sense for this drop-down to ignore subnetworkcontrollers that are deleted?

I've been letting all the deleted subnetwork controllers just hang out in the subnetwork table. Is there a recommendation about how often to "clean them up"? The only way to do that is through the export subnetwork tool, correct?

Thanks, 
Jake

 

GIS_kiwi4

@JakeJacobsAVA  - Good point.
I wouldn't really think of this as a bug as you rightly pointed out these are "dirty" subnetworks as the subnetwork controller has been deleted. There is also another good reason why these appear in the drop  down of the Update Subnetwork Tool (below in bold)

The reason the deleted&dirty subnetworks do not show up in the Find Subnetworks window is because they do not have any geometries (subnet lines) associated with them. By default it only shows the ones within extent (which will exclude all deleted lines)

As for cleaning them up - you are right. The export subnetwork tool is the only way.
But you cannot use this tool on dirty subnetworks (deleted or otherwise) so you will need to update these subnetworks. This is the reason why they are available in the Update subnetwork tool so you can clean these and the export these.

Note - Tool to have the acknowledge flag set to true and the tool needs to be run on the default version, not the editors versions. 

How often? 
We try and clear them during the GIS update process. Delete the subnetwork controller, clear it from Subnetwork Table and then create the new controller. 

Having them sitting in the subnetwork table isn't too bad. 
You might want to keep the subnetworks table clean if you are using subnetwork table and automated subnetwork exports to feed into other enterprise systems (ADMS, etc) but other than that they do not really interfere anywhere else. They are hidden away in the subnetwork table and don't really get in the way.