topic Re: Setting IncludeBarriersWithResults to FALSE does not seem to work in ArcGIS Pro SDK Questions

Setting IncludeBarriersWithResults to FALSE does not seem to work

EdwardBlair — Tue, 05 May 2026 23:35:44 GMT

Hello -

I'm probably missing something stupid, but I can't get a Utility Network downstream trace to exclude barriers from the result set. I'm setting the TraceConfiguration IncludeBarriersWithResults to FALSE -- see below. But the results returned always include the barrier features (which happen to be fuses my my use case.) Note that the equipment *below* the barrier *is* excluded, but not the barrier feature(s) themselves.

Any pointers on what I am missing would be much appreciated.

Thx,

----------------------------------------------------------------------------------------

using (un)
using (UtilityNetworkDefinition utilityNetworkDefinition = un.GetDefinition())
{
using (NetworkSource networkSource = utilityNetworkDefinition.GetNetworkSource("ElectricDevice"))
using (AssetGroup assetGroup = networkSource.GetAssetGroup(agName))
using (AssetType assetType = assetGroup.GetAssetType(atName))
{
DomainNetwork domainNetwork = utilityNetworkDefinition.GetDomainNetwork("Electric");
Tier sourceTier = domainNetwork.GetTier("Electric Distribution");
TraceConfiguration traceConfiguration = sourceTier.GetTraceConfiguration();
traceConfiguration.IncludeStructures = false;
traceConfiguration.IncludeBarriersWithResults = false;

// proceed to get a tracer from the trace manager and execute a downstream trace with the

// above trace configuration

Re: Setting IncludeBarriersWithResults to FALSE does not seem to work

RobertKrisher — Thu, 07 May 2026 17:02:34 GMT

Can you replicate this behavior by running the same trace inside ArcGIS Pro? Does this only happen when the fuse has terminals?

Re: Setting IncludeBarriersWithResults to FALSE does not seem to work

EdwardBlair — Thu, 21 May 2026 12:53:10 GMT

Here goes...

Devices in in the category "E:Switch -Fuse" are defined as barriers for this trace.

Option to include barrier features is un-checked.

Trace is executed stopping at fuses, but fuses are included in the result.

Re: Setting IncludeBarriersWithResults to FALSE does not seem to work

RobertKrisher — Thu, 21 May 2026 13:38:22 GMT

Does the fuse have terminals/does this only happen when the fuse has terminals?

Re: Setting IncludeBarriersWithResults to FALSE does not seem to work

RobertKrisher — Thu, 21 May 2026 13:47:58 GMT

I ask about the terminal thing because that is a designed behavior of trace, where we include the device as a barrier if it has terminals, even when the include barrier features option is not selected.

Re: Setting IncludeBarriersWithResults to FALSE does not seem to work

EdwardBlair — Thu, 21 May 2026 13:51:29 GMT

Yes. The fuse has terminals. Kind of confusing. But if that's the way it works its good to know. Thanks for the info.

Re: Setting IncludeBarriersWithResults to FALSE does not seem to work

RobertKrisher — Thu, 21 May 2026 14:18:03 GMT

@EdwardBlair if you really need to hide that feature you can add an output condition to the trace that will explicitly hide it. In this case, adding an output condition where the category is not equal to E:Fuse.

I apologize for using screenshots of water data for this issue, I was having issues finding a spot in the electric project I was using where the fuses had terminals.

Re: Setting IncludeBarriersWithResults to FALSE does not seem to work

EdwardBlair — Thu, 21 May 2026 15:03:08 GMT

There you go! That did it. Thanks Robert!