nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

LJackson29

Does anyone know if BUG-000176644 (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) is also occurring in Pro 3.3.5? I have a model builder that has a select by attribute step where it selects features where field = Yes, and then on the selected features, there are 4 field calculate steps, changing the values to Null for all 4 fields. This model builder has been working fine with no issues for the past 2 years. Today, when I ran it, it ran the first field calculate correctly, but the the subsequent 3 field calculates changed all records in the layer to Null! Luckily, I had a backup of the data and can restore it, but I am very concerned it could happen with other model builders (I have about 20 I use to maintain this layer, with many select by attribute and field calculate steps. This is very concerning. Does any one have any insight?

Best,

Leila

Finde mehr Beiträge mit dem Tag

Desktop

Feature Services

Accepted answers

All comments

DanPatterson

It was only reported in 3.5 and is fixed in the first update (3.5.1 and in the upcoming 3.6)

BUG-000176644 for ArcGIS Pro

If no one noticed in previous versions, or reported it, then it could have existed.

There won't be any backporting of the fix, so the update path would be your only recourse.

LJackson29

Thanks, it seems somewhat sporadic. Unfortunately, we are stuck at 3.3.5 until we update our enterprise next year.

RhettZufelt

Not an answer to your question, but in Model Builder, I have had better luck with MakeFeatureLayer with SQL expression on it, then perform the calculations on the feature layer. Otherwise, it seems I have to re-select before each operation.

Robert_LeClair

Within the internals, BUG-000176644, is fixed at ArcGIS Pro 3.6, 3.5.1 and the ArcGIS Server 11.5 Calculate Field path is available here - ArcGIS Server 11.5 Calculate Field Patch

Ron_S1

Has this been fixed for everyone? we have experiencing this but very sporadic, I've caught in recording a couple times. But when I try to create a project that I could send to Esri, it all goes smoothly. I'm if this has been fixed for everyone and maybe this is more of a local issue for us now.

Robert_LeClair

@Ron_S1 - what release of ArcGIS Pro are you using? As mentioned in my above post, BUG-000176644 was fixed at 3.5.1 and 3.6 of ArcGIS Pro.

DanPatterson

also mentioned in my post as being fixed

Nimm an der Diskussion teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.