Latest Contributions by RobertKrisher

‎12-09-2025

Please log an issue with support, this sounds like it could be BUG-000173229.

‎12-06-2025

To be specific about your example, you would run an upstream trace and set a filter barrier on stop logs or on vaults that contain stop logs. This would then let you see all the upstream paths to stop logs, and if you see a path that goes all the way upstream (because there isn't a stop log) you would want to come up with a plan for how to tackle that path.

‎12-06-2025

@Joshua_Moreno There are three fields that are configured when using propagation, and the phases energized field store the results of the phasing that was calculated by the system. Phases energized is a symptom of the problem; the cause is that the field used for E:Phases Propagated (phasechange) is not populated. Here's a screenshot of the standard subnetwork definition for propagation: Here's a screenshot of the network attribute assignment for E:Phases Propagated. If you populate the phasechange field of all your features with the phasing value, instead of the phases energized field, then your subnetworks should start tracing. If you aren't 100% confident in your phasing, you may want to remove the propagators from your subnetwork so you can work through some of the simpler data issues first before you worry about having your phasing 100% accurate.

‎12-05-2025

@Joshua_Moreno if the subnetwork name isn't getting past the controller, then the phasing of your controller or lines are likely not populated or they don't match (i.e. your controller is C phase but the line is B phase). I agree with @MikeMillerGIS that without seeing your configuration with a small bit of data we can only guess about what is happening.

‎12-05-2025

@yockee 1. Create and manage attribute rules—ArcGIS Pro | Documentation 2. Before worrying too much about the backend (REST), I recommend you read more about the capability: Validation attribute rules—ArcGIS Pro | Documentation

‎12-04-2025

The attribute rule is stored in the geodatabase and is exposed through a validation service to clients. There is also the ability to choose between enforcing rules client-side, or server-side only. I recommend you do some research on attribute rules and the validation service.

‎12-04-2025

@TóthRóbert you can use the un properties extractor to extract all your field properties to a file, update them, then re-import them over a map. You can also copy/paste field properties between layers and different maps using the "Paste Properties" context menu option..

‎12-04-2025

@NathanHeickLACSD You will find these discussions in the intro and advanced sessions for the UN that we have at conferences, and you can find an article explicitly about the usage of filters here: Isolating failures using ArcGIS Utility Network

‎12-04-2025

Also, the connectivity trace ignores terminal directions and subnetwork controllers.

‎12-03-2025

1 - No 2 - You won't be able to run subnetwork, subnetwork controller, and isolation tracing. You will only be able to run upstream/downstream tracing with digitized direction. If you want to have attribution about tributaries, lift zones, etc you'll need to manage these using other means, since you won't have subnetworks to update. You also won't be able to use the IsConnected trace to identify disconnected elements, since it relies on traversabilty to subnetwork controllers. If you set up your treatment plant as a controller you'd be able to get most of this, you just wouldn't have the granularity to trace all of your sub-basins or any of the discharges downstream of your treatment plant (with subnetworks). 2a - Can you explain your use case around an isolation trace in a sewer system? Are you looking to isolate a pipe from its sink (i.e. simulating a blockage) or are you trying to determine how to place upstream barriers to isolate the area from upstream flow?

‎12-03-2025

The attribute rule is going to be more reliable and have a better user experience, especially if you're working with data that is versioned or coming in through mobile workflows. You can even make some attribute rules available to mobile users when they are offline, so even when they're editing a local copy of the data integrity is still enforced.

‎12-02-2025

When you do an upstream or downstream trace, you must either choose to use a domain/tier or you must choose digitized direction. You can run a digitized direction trace in an area of the network that has subnetwork controllers, but the trace will ignore the controllers to determine flow. A section of your network can belong to multiple subnetworks (within the same tier), as long as the controllers themselves can't connect to each other. In your example, if that manhole normally bifurcates flows, even when it is not under significant flow, then the area upstream of a manhole that bifurcates flow would belong to multiple tributaries and therefore multiple subnetworks. If the bifurcation only occurs when there is enough flow in the system, then the area upstream would only belong to a single subnetwork since under normal conditions water cannot flow to the second tributary.

‎12-02-2025

@dcoll86 the add-in was compiled and is provided as is with ArcGIS Pro 3.5. If you want to use it in a different version or have any issues with the tool, you will need to download and compile the calculate flow arrows community sample to meet your requirements. Having said that, the add-in does work on my ArcGIS Pro 3.6 install.

‎12-02-2025

@crogis I'm not 100% sure exactly what's going on without seeing exactly what you're doing in your map. I recommend you read these two sources to understand the limitations around the different types of layers and the Add Join tool: Work with subtype group layers and tables—ArcGIS Pro | Documentation Add Join (Data Management)—ArcGIS Pro | Documentation If you think you're within the parameters of what we say we support, please log a case with support so they can step through your workflow with you and see exactly what you're donig.

‎12-01-2025

The field is updated when you run update subnetwork, but if you're using the standard ArcFM model you will only see that field updated when you run the tool in default. If you are not seeing this, please open a case with support.

Online Status	Online
Date Last Visited	48m ago

My Ideas

Latest Contributions by RobertKrisher

Re: Issues Reconciling and Posting Versions When Multiple Utility Networks Exist in the Same Enterprise Geodatabase (Insufficient Permissions Error)

Re: Subnetworks vs. Digitized Direction

Re: How to manage connectivity - Circuits

Re: How to manage connectivity - Circuits

Re: Attribute Validation / Calculation using Arcade or Database Trigger

Re: Attribute Validation / Calculation using Arcade or Database Trigger

Re: WebGIS Best Practices? - All fields MUST be visible when publishing ArcGIS Utility Network with Branch Versioning

Re: Subnetworks vs. Digitized Direction

Re: How to manage connectivity - Circuits

Re: Subnetworks vs. Digitized Direction

Re: Attribute Validation / Calculation using Arcade or Database Trigger

Re: Subnetworks vs. Digitized Direction

Re: Calculate Flow Arrows add-in

Re: Join Table to ArcGIS Utility Network Feature Service

Re: When I change the status of switch from close to open no changes have been observed in the feeder ID.

Re: Add Network Attribute (Trace Network) Issues

Re: How Does deploying UN in a Cloud PostgresQL Db...

Re: Subnetwork problem after upgrade UN v5 to UN v...

Re: Tracing Result by Flow Direction

Re: Validate Network Topology Fails ArcGIS Pro 3.7...

European Utility Network Community (UNC)

APAC Utilities Community of Practice