Select to view content in your preferred language

Modelbuilder: Calculate fields (multiple) issue post 3.1update

2702
11
Jump to solution
02-28-2023 02:24 AM
Labels (1)
Andy_CS
Regular Contributor

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?

 

Tags (1)
0 Kudos
2 Solutions

Accepted Solutions
ChrisUnderwood
Esri Contributor

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

View solution in original post

ChrisUnderwood
Esri Contributor

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

@Andy_CS @Mondi_GIS @KateBray @CMorneau 

View solution in original post

11 Replies
DanPatterson
MVP Esteemed Contributor

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


... sort of retired...
0 Kudos
Andy_CS
Regular Contributor

'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:

calc_multi_3x0x2.PNG

  Tool in 3.1.0

calc_multi_3x1x0.PNG

KateBray
Occasional Contributor

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!

Andy_CS
Regular Contributor

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
Occasional Contributor

Thanks Andy, appreciate it.  Ive contacted Support to request the previous version installation file - I have over 20 instances of this problem in just 1 model alone, each of those with multiple fields and unique expressions that have all now vanished. Hoping to downgrade and wait for the next fix to avoid days of rework.

Thanks for the post.

 

DanPatterson
MVP Esteemed Contributor

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


... sort of retired...
0 Kudos
ChrisUnderwood
Esri Contributor

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

ChrisUnderwood
Esri Contributor

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

@Andy_CS @Mondi_GIS @KateBray @CMorneau 

KateBray
Occasional Contributor

@ChrisUnderwood  thank you

0 Kudos