The Calculate Field tool does not honor active selections and layer filters when using a SQL expression on file geodatabase data, resulting in calculations on all rows.

Description

The ability to set the expression type to SQL in the Calculate Field geoprocessing tool when working with file geodatabase (.gdb) data was introduced in ArcGIS Pro 3.5. A potential data corruption bug has been discovered wherein Calculate Field does not honor the active selection or layer filters (for example, definition query, time filter, range filter, or spatial filter) when using a SQL expression on file geodatabase data, resulting in all rows being calculated.

Cause

BUG-000176644: Calculate Field does not honor active selection or layer filters when using a SQL expression on file geodatabase data, resulting in all rows being calculated.

Workaround

When using Calculate Field, to preserve the original values of your data, make a copy of the input table as a backup, or use the Enable Undo option in the Geoprocessing pane.

Do not use SQL as the expression type until this bug is addressed with a patch. Use Python, Arcade or VBScript as the expression type. 

This issue will be addressed in 3.5 Patch 1 (3.5.1), planned to be available the first week of June 2025. Until a patch is available, the software update service will be disabled in ArcGIS Pro. Customers who understand this issue and the workaround can download ArcGIS Pro 3.5 from My Esri.

Steps to Reproduce