Latest Contributions by RobertKrisher

‎05-16-2026

@MarianoDiNapoli btw, if all you need to do is update some asset type/asset group descriptions, you can do that on your utility network using ArcGIS Pro 3.7. You don't even need to disable the network topology. You can do this using the Design Views or the new Alter Subtype and Alter Coded Value Description tools

‎05-16-2026

It sounds like you are staging and deploying your utility network in the same geodatabase as your asset package. this is not supported.

‎05-16-2026

The warning you're getting about duplicated rows is caused because the asset package tools are detecting duplicate rows in the asset package. Because you are deploying the asset package to a new geodatabse, you cannot have conflicts between what is in the asset package and the target UN (because the target UN is empty). When you run export to asset package the resulting asset package will not contain any UN_* tables, so we populate C_* tables so they can be used to recreate the data in the system tables when the asset package is deployed.

‎05-16-2026

The UN_* tables are the system tables of the utility network, the C_* tables are the corresponding tables in the asset package. You shouldn't be redeploying the asset package to the same geodatabase to make configuration changes, you have to deploy it to a new geodatabase. There asset package is designed to append new data and new configuration into a utility network. If you make changes to an asset package you must deploy it to a new geodatabase, otherwise you will end up with duplicated data and it's likely that most of the configuration changes will not be applied.

‎05-16-2026

@GISP00 glad to hear that worked. that's something I was going to suggest, when you're relying on a foreign key that isn't always populated on a table to migrate a relationship, its a good idea to put a filter to only try and create associations when the field is populated so you don't get any unnecessary warnings. This is especially important when a class can have multiple relationships (transformer > pole, transformer > vault, transformer > pad).

‎05-15-2026

@GISP00 the tutorial was last tested on 3.6, but it is works for 3.5 as well.

‎05-15-2026

I'll let @MikeMillerGIS handle questions about create migration workspace, but you should also look at a newer way to migrate relationships described in this tutorial: Migrate relationship classes to a utility network | Documentation This new approach allows you to map the relationship directly to the associations table, which means that you'll get the latest relationships every time you run the data loading tools. The older approach creates a static CSV file when you create your migration workspace, which leads to relationships and features getting out of sync over time.

‎05-14-2026

That is just one way of modeling a transformer. since you have chosen to model them using containment/associations you will use the modify associations tool to create those associations. When creating features by hand you should be using an editing template that includes all these features, along with their associations, so users don't need to perform these manual steps every time a feature is created. You can learn more about that tool in the ArcGIS Online Help; Associations | ArcGIS Pro documentation You can also find a tutorial with examples of how to populate associations here: Get started with ArcGIS Utility Network for electric | Documentation

‎05-14-2026

Correct, a terminal configuration cannot be modified once created. You can set a terminal configuration of an asset type, but it cannot be modified. While these restrictions might be loosened in the future (with additional checks, safeguards, and specific restrictions) this currently requires going back to an asset package.

‎05-13-2026

Glad you got it working! The trace should always have been working, but if you were relying on update subnetwork then my guess is you were working in a version and not on default.

‎05-13-2026

Once you've created the network attribute you must assign it to each field/class you want to associate with that network attribute then you must ensure that the field on each class is populated with the desired values.

‎05-13-2026

When you run the trace, where does it stop? What is the phasing of the transformer? Can you post a screenshot of the subnetwork definition for this tier from the network properties dialog? You have a non-standard model, so I want to see how your propagators are configured? You'll need to scroll all the way to the right to see these properties:

‎05-12-2026

Not currently. If there isn't already an idea for this, please create one.

‎05-12-2026

Without any special configuration a 3-phase service connected to a 2-phase transformer will still be energized, but only the two phases from the transformer will be energized. Most models are configured to only include medium voltage lines in the subnetwork line (for performance reasons), but just because the line isn't included in the subnetwork line doesn't mean it doesn't belong to the subnetwork or that its not included in calculations for the subnetwork. If the trace is stopping at the transformer and not continuing to the secondary, its because something else is wrong. There is a new network category being added with UN v8 called propagator resetter that allows you to handle scenarios like this. When this network category is assigned to an asset type, like an open delta or step transformer, the trace will reset the propagated values (phasing) when passing through one of these devices. This should allow all three phases of the service to be energized. You can learn more about propagator resetters here: https://doc.esri.com/en/arcgis-pro/latest/help/data/utility-network/attribute-propagation.html#JDZ

‎05-12-2026

A condition barrier will prevent the trace from identifying sources, while filter barriers are used to identify candidate features to act as isolation equipment. For what you are trying to do, you want to configure a filter barrier. I'm just restating what @gis_KIWI4 said in a way that makes sense to me. To be clear, there is no 'internal logic' or behavior of the UN with regards to condition barriers/filter barriers. We will only evaluate the attributes that are configured in the form. There are default condition barriers that are included in subnetwork definitions that are populated when you configure an isolation trace, but these are configurable and can be modified at will so therefore are not 'internal'.

Online Status	Online
Date Last Visited	yesterday

My Ideas

Latest Contributions by RobertKrisher

Re: ERROR 160874: The utility network association already exists

Re: ERROR 160874: The utility network association already exists

Re: ERROR 160874: The utility network association already exists

Re: ERROR 160874: The utility network association already exists

Re: No association records found Streetlight key SupportStructureStreetlights

Re: No association records found Streetlight key SupportStructureStreetlights

Re: No association records found Streetlight key SupportStructureStreetlights

Re: Electric Utility Network - Device Bank associated to Device

Re: Downstream Trace - Sewer Utility Network

Re: How Do You Model A 2ph Transformer Bank That Produces 3ph Secondary Service?

Re: Isolation Trace - Skip Certain Control Valves Based on Attribute / Ground Condition

Re: How Do You Model A 2ph Transformer Bank That Produces 3ph Secondary Service?

Re: Solutions for Creating Schema Diagrams

Re: How Do You Model A 2ph Transformer Bank That Produces 3ph Secondary Service?

Re: Isolation Trace - Skip Certain Control Valves Based on Attribute / Ground Condition

Re: Utility Network Sewer Main Lines: Labeling Iss...

Re: Change Asset Package Spatial Reference Deletes...

Re: Supported workflow to add new fields to existi...

Re: Change Asset Package Spatial Reference Deletes...

Re: Utility and Pipeline Data Model 2023 with "Sub...

European Utility Network Community (UNC)

APAC Utilities Community of Practice