Latest Contributions by RobertKrisher

‎03-19-2026

Can you find an area you can confirm is isolatable (visually) and post a screenshot? The easiest way to do this would be in the large pressure zone in something like a cul de sac. Use condition barrier: Closed OR Lifecycle Status Not in Service or Pending Removal And the filter barrier should be: Category Isolation AND Closable I want to see an area of your network that you are sure you should be able to isolate but the software isn't properly identifying those features. I have seen customer datasets where portions of the network are not isolatable because valves are either missing or not properly connected to the system (GIS Data Problem) or even situations in which the network wasn't designed to be isolatable (Engineering problem). Edit: For testing purposes just rely on the network category, this rules out any issues with the Closeable field being populated.

‎03-19-2026

What filter barrier are you using? Is it possible that the area you are isolating doesn't have enough equipment that meets the criteria of your filter barrier to isolate it from all your sources?

‎03-19-2026

Can you show a screenshot of the pipes connected to the treatment plant, intake, and the pressure controller? Please include labels for the terminal connections. If you set the outlet port of the treatment plant as the controller to the system tier, and the subnetwork controller for the pressure tier is downstream of that (and on the downstream terminal of that device) then this shouldn't happen.

‎03-18-2026

You should be able to define the intake from the lake or the water treatment plan as subnetwork controllers for the Water System tier. This is the highest-level tier in the water network.

‎03-18-2026

A shared vertex between two lines at the location where the cross does not cause the two lines to become connected in a utility network. They will only become connected if the endpoint of one line terminates on another line, or if there is a device/junction at the location where the two lines intersect. The Migration Toolset does have the ability to identify and remove these junctions the mid-mid intersections, but we do not recommend you do this because a) it can alter the appearance of lines and b) there is not a strong technical benefit to making this change.

‎03-13-2026

The origin feature's association role determines the type of association that should be. So if you have two associations between features A and B, with one saying that A contains B and the other saying that B is attached to A, then it's a duplicate.

‎03-13-2026

@JohnGoat If the device you put the barrier is an enabled subnetwork controller, then this is the expected behavior and you will need to open a case with support and create an enhancement request. Working through detailed requests like this on the community site is difficult, particularly when you are skipping over some of my steps and instructions. Because I don't have access to your data I may ask you to do strange things (like run a shortest path between the two controller) so I can better understand the topology we are dealing with. At this point I feel this is not an issue we can resolve through discussions like this. Please log a case with support and have them work through the issue with you.

‎03-13-2026

ArcGIS Server and ArcGIS Pro will cache a copy of the rule when it first executes it. So if you aren't restarting Pro or the SOC's for the service after making the change then you run the risk of running the old version. If you kept schema locking enabled on the service this would have prevented the system from getting into this state, but this is the tradeoff you pay when you disable schema locking (you then take ownership of needing to manually restart services after making schema changes).

‎03-13-2026

There are typically three approaches to this problem, and each approach has different benefits, depending on what you're trying to achieve. I would only choose one of the other two options (below) if you were looking for a way to ONLY copy the utility network data and wanted to leave the rest of the objects in the database behind. If you're looking to create a complete copy of your entire database, including your utility network, then restoring a database backup to a create a new database is usually the fastest option. Unfortunately you can't just backup one schema and restore it, you must backup and restore the entire geodatabase because you need the schemas that contain SDE and the utility network, along with any other schemas referenced by SDE. Export/Import asset package, highlighted by @PierreloupDucroix, gives you the most control, and themost information if something goes wrong. The downside to this approach is that you must enable your network topology and update your subnetworks afterwards, which can be time consuming. Copy/Paste or Export/Import XML Workspace document are another way of doing this without needing to download any tools from solutions. This approach has the benefit of preserving the state of your utility network (topology, subnetworks, etc). This is discussed on the utility network dataset administration page of the online help.

‎03-11-2026

This subnetwork category condition barrier should be in addition to any other condition barriers you have for the normal or operational state. Otherwise, the system will not treat the other switches as open. IF you want to see the path between the two controllers, switch the trace to be a shortest path trace and put starting locations at each controller.

‎03-11-2026

Open a case with support please.

‎03-09-2026

Based on my experience and testing, I have seen there to be less consequences associated with using network categories for this kind of workflow, but you're constrained to identifying features at an asset type level. This works well when you're trying to identify types of equipment, but I wouldn't recommend that you try and replace all your network attributes with asset types, just so you can avoid network attributes. I have seen customers use this approach for representing open/closed equipment as different asset types, and any potential flexibility/performance gain you would have gotten is eclipsed by the overhead of maintaining the extra asset types and the exponential increase in rules you have to maintain. This is both the administrative and performance overhead.

‎03-09-2026

@Jens_Dalsgaard you'll still have the problem with inconsistent subnetwork names.

‎03-09-2026

This is already possible via match tables and global lookups in the Data Loading toolset.

‎03-09-2026

If the device that is acting as a barrier is a subnetwork controller (is subnetwork controller = true), then the trace has gone too far, and you will get an inconsistent subnetwork name error. If you want the trace to stop at features that can be subnetwork controllers, but aren't enabled as subnetwork controllers you would set the condition barrier to be on the Subnetwork Controller category.

Online Status	Online
Date Last Visited	yesterday

My Ideas

Latest Contributions by RobertKrisher

Re: Isolation Trace completed with warnings in large subnetworks

Re: Isolation Trace completed with warnings in large subnetworks

Re: How to generate a subnetwork for water system intake

Re: How to generate a subnetwork for water system intake

Re: Automating the removal of redundant vertices on Arcs (Utility Network errors)

Re: Apply Asset Package - Duplicate association found

Re: Downstream Trace Crossing into Another Subnetwork and Failing with ERROR 001890

Re: Can't get rid of attribute rule

Re: Python script to copy UN data from one SDE to another SDE

Re: Downstream Trace Crossing into Another Subnetwork and Failing with ERROR 001890

Re: Unable to add junction object as controller when using a subtype group table

Re: Issue attempting to use Asset types with a Count summary attribute in Set Subnetwork Definition

Re: Isolation trace - Simulate whatifs scenarios

Re: Create Migration Workspace global mappings

Re: Downstream Trace Crossing into Another Subnetwork and Failing with ERROR 001890

Re: Valid paths not routing upstream trace correct...

Re: Feedback on the Prune Branch History Tool

Re: Edit Widget: Create Feature function not displ...

Re: Asset Package - Change Asset Type Domain for a...

Re: Feedback on the Prune Branch History Tool

European Utility Network Community (UNC)

APAC Utilities Community of Practice