topic Re: Circuit Filter in ArcGIS Utility Network Questions

Circuit Filter

Joshua_Moreno — Tue, 27 Jan 2026 23:00:00 GMT

I'd like to create a filter in ExB or similar that would allow me to only see all devices/structures/lines along a single circuit whether when selected or somehow filtered using a filter widget. Is this something anyone has done? Essentially, I'd like to cut out all extra noise from adjacent circuits to give my team a clear picture of a single circuit and it's connected devices.

Re: Circuit Filter

gis_KIWI4 — Wed, 28 Jan 2026 07:25:24 GMT

Hi @Joshua_Moreno - The SUBNETWORKNAME field can be used for this. You can set up the filter widget to filter on this field. This field is present on devices and lines, basically all the domain network elements.
If you want to include structures then use the SUPPORTEDSUBNETWORKNAME for filtering structure junction and structure boundary.
Use "contains" operator rather than "equal to"
The good thing about this approach is that open switches / boundary devices will remain visible as they should have both subnetworks listed in the mentioned fields eg - Subnetwork A :: Subnetwork B

Re: Circuit Filter

RobertKrisher — Wed, 28 Jan 2026 14:32:28 GMT

The only other catch to using the Subnetwork Name field for you is that you must run Update Subnetwork for it to be populated. Customers who have hierarchical models (pipeline, water, sewer) have multiple subnetwork name fields (system, pressure, etc) so they need to pick which field (which corresponds to a tier) they want to use.

Re: Circuit Filter

RichRuh — Wed, 28 Jan 2026 16:20:18 GMT

Another solution that does not rely on the Subnetwork Name field being properly updated is to use the Utility Network Trace Widget in Experience Builder.

To do this, you would define a trace configuration in ArcGIS Pro that does a subnetwork trace- use the setting for include structures, and an output filter to define which asset types you want to include. Once you've gotten the trace working in Pro, add it to your web map and then it would be accessible from inside Experience Builder.

--Rich