Latest Contributions by RobertKrisher

@angiexx1 in the screenshot above the symbology is using three fields (Asset group, status, operating status). Can you post a screenshot of the symbology on that layer in the map used to publish the service?

I think putting it in a utility network is a better plan, since this mean you can set up some basic subnetworks for each substation that represent what you need to extract into your OMS/ADMS. If you only care about the distribution side of each substation, set up the power transformer as a subnetwork controller and you're ready to start exporting substations (now all you need to do is transform them).

This is not available in the ArcGIS Pro SDK, but please log an enhancement request for this as its something we have considered implementing at some point in the future. However, you CAN already do this using the ArcGIS Enterprise SDK (IUtilityNetworkQuery2 Interface | ArcGIS Enterprise SDK | Esri Developer), the most common way of exposing this capability is through a SOE or SOI, in your case you would probably want to build an SOE for this.

I suspect there are multiple things happening. Let's start with something simple. Connect the lines on that manhole as shown below, configure an upstream trace with the "use digitized direction" option, and run the trace. Then post a screenshot of the resulting trace (it should look correct).

You need to determine which code you deleted from the domain and re-add the original code and description to the domain before you can reassign it.

What type of dataset is this? If its something with a system tier you could create a network diagram using that subnetwork.

@CristinHolmgren2 are you deploying this to a mobile geodatabase? or a file geodatabase? or enterprise geodatabase? Don't use a file geodatabase when working with associations, they are painfully slow for that. If you are using a mobile geodatabase, make sure it is on an SSD that is local to the machine that is running the tool. You could turn on simple build logging to see timestamps of when the various events are running.

‎06-01-2026

What I'm saying is that you didn't need to extend the domain, you should have use the existing domain and values, just update the descriptions to match the customers data. I have already provided a proposal of how you could have mapped their values to the original values. You should be able to incorporate that into your data migration going forward, and if you need to fix it right now you can adjust the data and schema in the asset package to make the correction. You can see the bitsize in the network properties. Because you are using an asset package to build your utility network, refer to their documentation for hot to control the size of an inline attribute: Utility Network Package_Asset Package Reference.pdf

‎05-29-2026

There is no such thing as creating a new association role. The roles are none, container, and structure. If you are setting the association role of an asset type (e.g. handhole) from None to a Container you will be able to do that as long as the topology is disabled. If the Handhole is already set to be a Structure and you want to make it a Container, then you are altering the association role, which is not allowed once you have enabled the network topology. Based on the error you are receiving, it sounds like this is the case. If you want to alter an association role after enabling the network topology you will need to go back to an asset package, remove any containment/attachment rules associated with it, change the role in the asset package, add new rules, then re-deploy your utility network. You can see what the asset type's current association role is by opening the tool or looking at the network properties (choose the show default values option to make it clearer). The association role of the handhole in the utility network foundation is structure.

‎05-29-2026

The domain you have configured to set the bitsize of your phasesenergized domain (Electric_Phase_Attribution_All) only allows for 3 bits (max value = 7) The domains you have assigned to your features appear to have a maximum value of 14, which requires 4 bits. Furthermore, it looks like you just added RYB values onto the end of the domain instead of using the existing coded values and renaming the descriptions. This is important, because the way you have done this does not allow for the bitwise combination of the different phases, which will result in phase propagation not working correctly. It looks like RYB = ABC, and my guess is if you look at the original coded values in your source data you will see that the integer values from your original domain matched (R=4, Y=2, B=1, and RYB=7). After inspecting your data, it appears that you should have just mapped your phasing values to the existing domain values instead of extending the domain.

‎05-28-2026

You should be able to set an association role after you've enabled your network topology. You just can't change or unassign it, and you will need to remove any existing rules before you can change the role. All the restrictions are listed on the Utility network management tasks topic in the online help.

‎05-28-2026

@AllanBenvin_yyc Because SDE doesn't use a static query for accessing the data like a view does. Take a look at how where clauses are applied to the branch version analytic and it will start to make sense. If you have a limited number of access paths you're supporting with dynamic views, you can recreate optimized queries similar to what ArcGIS Pro is doing. But this is an advanced activity that requires a strong understanding of SQL. Also, it's not doubling the storage requirements of the table. You're duplicating the storage of only the active rows in the table, not the active rows + N years of history.

‎05-28-2026

please open a case with support

‎05-28-2026

Can you show a screenshot of all your network attributes? along with the full attributes of one of the features that has this error?

‎05-27-2026

Lines don't need to be split in order to have connectivity in the utility network, and the Water Utility Network Foundation is configured to allow for connectivity at any vertex along the line. Asset types can be configured with an Edge connectivity policy that controls whether connectivity is allowed at any vertex or only at the endpoints, so if you add any new line asset types you need to remember to set an appropriate edge connectivity policy (the default is end vertex only).

Online Status	Online
Date Last Visited	an hour ago

My Ideas

Latest Contributions by RobertKrisher

Re: Published UN webmap showing coded domain value instead of description

Re: Trace Network in the ArcGIS Pro SDK

Re: Trace Network in the ArcGIS Pro SDK

Re: Valid paths not routing upstream trace correctly through features in multiple subnetworks (Sewer Tee junction)

Re: Utility Network – ERROR 004049 Unable to modify domain, one or more asset types have been deleted

Re: Has anyone created a One Line Diagram or has employed a third party?

Re: 14 Million Associations - Best way to load to Utility Network?

Re: ERROR 003856:* The max value of the domain exceeds the bit size of the network attribute while applying asset package

Re: Association Roles/New Rules

Re: ERROR 003856:* The max value of the domain exceeds the bit size of the network attribute while applying asset package

Re: Association Roles/New Rules

Re: Branch Version Sql Views - Utility Network

Re: Validate Network Topology Fails ArcGIS Pro 3.7 for Water UN, Sewer UN

Re: ERROR 003856:* The max value of the domain exceeds the bit size of the network attribute while applying asset package

Re: Water UN Data Cleanup

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