Upgrade Dataset v4 to v5 - Subnetwork field name already exists

[KyleGallagher16]

I am attempting to run Upgrade Dataset on an enterprise electric UN from v4 to v5. Services are turned off, locks and connections are cleared, network topology is disabled, geodatabase version is 10.8.1.2.6, database connection is using the UN owner.

Below is the error I'm receiving, which when going to the error link the solution (https://pro.arcgis.com/en/pro-app/2.8/tool-reference/tool-errors-and-warnings/001001-010000/tool-err...) mentions finding the specific field properties required for the SUBNETWORKNAME field in the Add Tier tool documentation. Is Upgrade Dataset trying to run Add Tier as part of its process? Has anyone else ran into this before?

Thanks!

[LindseyStone]

Yes, enterprise going from 10.8.1 to 10.9.1 and v4 to v5.  I have branched versioning and I have 2,858 records in my Electric Assembly.

[MikeMillerGIS]

ok, my guess was wrong then.  Let us know what support says and I will keep digging too.

[RobertKrisher · Accepted solution]

The SUPPORTINGSUBNETWORKNAME field applied to all applicable domain classes has properties that do not match those expected by the system (on creating a Utility Network or upgrading a dataset). When the SUPPORTINGSUBNETWORKNAME field is created, isRequired must be -1 which means True, and isEditable must be 0, which means False. In this data, isRequired is 0 and isEditable is -1, which caused the failure. The SUPPORTINGSUBNETWORKNAME field is not created until Utility Network Version 5. Removing these fields from the various classes allows the upgrade to be run successfully from Utility Network Version 4 to Version 5, or 6 (which then re-adds the fields in a supported manner).

You should check the SupportingSubnetworkName field for the following classes for each Domain Network in your Utility Network (except the structure domain):

• Device
• EdgeObject
• Junction
• Junction Object
• Line