nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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-errors-and-warnings-02126-02150-002136.htm) 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!

Encontre mais publicações marcadas com

Accepted answers

RobertKrisher

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

All comments

MikeMillerGIS

Please log an incident with Tech Support. I have not seen this issue before.

KyleGallagher16

Mike,

Looking at all of the existing UN v4 feature classes that have the subnetworkname field present, they all appear to have the same field properties:

Name: subnetworkname

Alias: Subnetwork name

Data Type: Text

Allow NULL: True

Domain: None

Default: Unknown

Length: 2000

The only exception is with the Structure Boundary feature class where the subnetworkname field alias is "Supporting subnetwork name". Not sure if this is what's causing the error but wanted to throw it out there.

MikeMillerGIS

If a subnetwork name field is added without data, it is added with Allow Null = False. It appears a tier was added after data, which means the subnetwork field has to be added with Allow Null = True. So Update is expecting this field to Allow Null = False is my guess.

KyleGallagher16

Sorry, Allow NULL is False for all of the existing subnetworkname fields present.

No tiers were added as I'm only using the out of the box Electric Distribution Substation tier.

MikeMillerGIS

My only guess is it is trying to add the SupportedSubnetwork field to assembly as allow null equal false with data.

Assembly:

KyleGallagher16

The SupportedSubnetworkName field already exists in ElectricAssembly with the properties you showed. No data is present in the feature class.

We've submitted an incident with Tech Support.

MikeMillerGIS

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

LindseyStone

What was your solution on this with Tech Support

MikeMillerGIS

Are you attempting this on an Enterprise GDB? If so, is it versioned and does it have data in it(assembly class)?

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.

KyleGallagher16

We looked at the SDE intercept files and they pointed to the ElectricAssembly feature class, which had zero features in it and the schema was unchanged from when the UN was built. I went with the following workaround to get to UN v5:

Export Asset Package using SDE UN as input
Created DB backup
Truncated all SDE content
Stage Utility Network in the SDE
Apply Asset Package using the exported AP from first step

Kyle

RobertKrisher

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

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.