topic Re: Can't edit features after running Update Subnetwork in ArcGIS Utility Network Questions

Can't edit features after running Update Subnetwork

KyleGallagher16 — Thu, 03 Feb 2022 15:52:57 GMT

I am making some minor vertice updates to electric lines from a UN feature service in Pro 2.6.7 and then running Update Subnetwork on a specific Subnetwork Name to ensure end-to-end connectivity. However, after running the tool if I want to move on to the next subnetwork to make edits I am getting the following error:

Modify vertices failed. Layer is not editable. Review errors in the Status dialog or in List by Editing view of Contents pane.

Going to the Status dialog it mentions that Dirty Areas and Electric Subnet Line are noneditable, and all other layers are editable with warnings (using enterprise geodatabase).

My solution is to close and re-open Pro, but this is not sustainable. Thoughts on how to get around this issue?

Thanks!

Kyle

Re: Can't edit features after running Update Subnetwork

SSMIC3038 — Thu, 03 Feb 2022 16:06:57 GMT

Just a shout out that I deal with the exact same problem, alot!

Re: Can't edit features after running Update Subnetwork

GIS_Solutions — Mon, 07 Feb 2022 14:37:55 GMT

Hi,

Opening a new map, add date the feature class again. Try to use them without any symbology adjustments.
If it doesn't give an same error, apply your existing symbologies to your new map.

I had a similar problem and this is how I solved it.

Re: Can't edit features after running Update Subnetwork

KyleGallagher16 — Mon, 07 Feb 2022 14:58:12 GMT

Would you say that takes about as long as closing Pro and reopening?

Re: Can't edit features after running Update Subnetwork

SusanONeill1 — Wed, 15 Jan 2025 21:30:07 GMT

I have the same problem after disabling the Utility Network, adding a Rule, and then Enabling the Utility Network. I close ArcPro and reopen it - and then I can edit. (Right now I'm only working in a file geodatabase in preparation for migrating to the UN, but I've noticed a lot of unpredictable behavior in ArcPro.) Very frustrating.