Select to view content in your preferred language

Excluding Features from Field Calculation in Batch Trace?

311
3
Jump to solution
03-25-2026 04:35 AM
JohnGoat
Regular Contributor

Hi,

I am trying to perform a field calculation using the Batch Trace tool, specifically with the Fields to Update option. However, I want to exclude certain features from the calculation based on an attribute condition.
For example, I do not want the field calculation to be applied to records where ASSETGROUP = 12.

How can I do this?

Additionally, what is the logic behind the Code Block section at the bottom?
Is it possible to implement this kind of conditional logic using the Code Block?

 
 

Calculate.jpg

Thanks,

0 Kudos
1 Solution

Accepted Solutions
MikeMillerGIS
Esri Frequent Contributor

Can you use an output filter to limit the trace results to remove AssetGroup = 12?  The code block is designed to allow a user function for the calculated value.  It will not let you limit what features get calculated.

View solution in original post

3 Replies
MikeMillerGIS
Esri Frequent Contributor

Can you use an output filter to limit the trace results to remove AssetGroup = 12?  The code block is designed to allow a user function for the calculated value.  It will not let you limit what features get calculated.

RobertKrisher
Esri Regular Contributor

Also, instead of using Asset Group codes or Asset Type codes for your filters, consider using a network category. Asset groups/type codes are not guaranteed to be unique, and using a network category allows you to exclude/include multiple asset groups/types with a single category.

It also makes the filter easier to understand. Saying you're excluding asset group 12 doesn't mean much, but saying you're excluding something like "cathodic equipment" or "high voltage" does.

JohnGoat
Regular Contributor

We are using a custom data model and not the Electric Network Foundation provided by Esri. In our schema, the ASSETGROUP code values are designed to be unique, so using an output filter seems sufficient for our needs.

Thank you, @MikeMillerGIS 

0 Kudos