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; } } }

Modelbuilder: Calculate fields (multiple) issue post 3.1update

Andy_CS

Hi,

I use the Calculate Fields (multiple) geoprocessing tool in multiple model builder models. After updating to 3.1 each instance of the tool has had its 'Fields' parameters removed and the 'Expression Type' parameter reset to 'SQL' from 'Python 3'.

I can't be certain that the update has caused the issue, but they were all working fine pre-update. I've tried restoring my toolboxes to earlier versions but this has not resolved the issue.

Could be something to do with the enhancement to the fields settings in the tool?

Has anyone else experienced this?

Find more posts tagged with

Desktop

Accepted answers

Chris Underwood

Fixes to these problems, logged as BUG-000156873 & BUG-000156874, will be included in ArcGIS Pro 3.2

@Andy_CS @Mondi_GIS @KateBray @CMorneau

Chris Underwood

These problems are logged in defects BUG-000156873 & BUG-000156874

All comments

Chris Underwood

Fixes to these problems, logged as BUG-000156873 & BUG-000156874, will be included in ArcGIS Pro 3.2

@Andy_CS @Mondi_GIS @KateBray @CMorneau

Mondi_GIS

Having the same problem after the upgrade - I have hoped an obvious bug like this would have been fixed in the new patch.. but nope! A nasty surprise for me post-upgrade!

CMorneau

Add me to the growing list of users having the same problem with this tool in 3.1.0. Most of our team upgraded to 3.1.0 last week, including me. In every model & model tool I've viewed so far that uses Calculate Fields (multiple), my parameters have been gutted. And if I view my processing history from pre-upgrade, there are no details listed. None. This is very frustrating. In some instances, I used Python for my expressions. In others, Arcade. Regardless of expression language, everything was gutted from my instances of this tool.

KateBray

@ChrisUnderwood thank you

Chris Underwood

These problems are logged in defects BUG-000156873 & BUG-000156874

Andy_CS

I have a support case open and will update if anything is resolved.

In the meantime I've reconfigured the tool in all of my active models to work in 3.1.

If you are able to reopen your projects and models in 3.0 then the tools should open with their original, working, configuration. I've made a note of them in 3.0 then set them up again in 3.1. Not the best solution and certainly time consuming but its the best I could come up with to get them working ASAP

KateBray

Im experiencing the exact same. After upgrading to 3.1.0. ALL my fields have been removed from the calculate multiple tool which is a significant problem for me. I cant remember the all the fields that were passed to the python code, nor can I remember the unique expression that was used to pass fields to the python code block and it has broken models that are currently deployed to support day to day business.

Ive gone back and checked backup versions of my toolbox that were saved last year, to see if I can extract the code from there but alas the fields and expressions have also been removed.

It seems this section of the software upgrade was not sufficiently tested. This is a HUGE problem for my active models!

danretired

So it reset modelbuilder tools. Not sure if that is expected, you might want to reach out to Tech Support on this issue

Andy_CS

'reset' was a poor choice of word on my part...

I've opened the models up in 3.0.2 and they are configured as expected, it's only in 3.1.0 that the parameters have been removed and the expression type changed. Looks like some sort of compatability issue to me?

There is a new section in the 3.1 help page regarding an optional sql expression in the fields parameter explanation.

Tool in 3.0.2:

Tool in 3.1.0

danretired

The only thing that appears to have changed in the help topic between 3.1 and 3.0 is the caution at the top.

The default is still python for the expression type

Calculate Fields (multiple) (Data Management)—ArcGIS Pro | Documentation

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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