Select to view content in your preferred language

New Batch Editor functionality doesn't work for calculated fields

243
5
Friday
StuartMoore
Frequent Contributor

i've just tried the new "Batch Editor" functionality it seems to calculate the values in the form but it doesn't save them against the data and only saves the values you manually update.

the below example the outcome / high level outcome & status fields are all calculated based on the questions above and the comments field is manually entered

StuartMoore_0-1751622722876.png

StuartMoore_1-1751622860215.png

after pressing update and viewing the data in the popup it shows the comments populated but all of the calculated columns are blank

StuartMoore_2-1751622931177.png

 



5 Replies
LindsayRaabe_FPCWA
MVP Regular Contributor

Confirmed - I'm seeing the same behaviour. Very disappointing! Thought I was clear free when I saw that it was honouring the calculated Required and Visibility conditions, but alas, one search to find if there were others finding issues, and here we are.

Also discovered in testing this issue, that if you have features with differing values in a field, it correctly returns the (Different values) statement in that field if it's a normal field, but not for Calculated fields. Something else that should be considered. 

Time to disable again. 

@AlixVezina 

Lindsay Raabe
GIS Officer
Forest Products Commission WA
HeatherGonzago
Esri Contributor

Thanks for the info, we are currently investigating this and will keep you updated on any updates as soon as possible.

- Heather

LindsayRaabe_FPCWA
MVP Regular Contributor

Thanks for the update @HeatherGonzago 

Lindsay Raabe
GIS Officer
Forest Products Commission WA
0 Kudos
HeatherGonzago
Esri Contributor

Hi, in addition to the original question. You mentioned 

Also discovered in testing this issue, that if you have features with differing values in a field, it correctly returns the (Different values) statement in that field if it's a normal field, but not for Calculated fields. Something else that should be considered. 




Could you clarify exactly what you are seeing? This could be something that may potentially need to be addressed. 


0 Kudos
HeatherGonzago
Esri Contributor

Hi everyone, we addressed this issue in a patch. We should have it out later today. You should be able to pick it up and see the changes by tomorrow.

Thank you for letting us know so we could take care of it quickly.