Issue w/ Calculations

[ISP_graynic]

Since the 2/26 Survey123 update, has anyone had issues with calculations not working? Specifically, we have a Survey123 form embedded in a dashboard in order to edit features which has always worked, but most recently even though the form shows the calculation correctly before submitting, after submitting it doesn't actually change anything. If we manually delete the value from the calculation and type it back in and submit, it works, but the value shown automatically from the calculation doesn't actually change the feature. 

[Stephanie_F]

Hi @ISP_graynic does this happen if you use the form outside of the Dashboard as well? If you are able to, I suggest a Support case to investigate this deeper https://support.esri.com/en-us/contact

[ISP_graynic]

I am unable to try it outside of a dashboard because the issue is when trying to edit an existing record using the List widget and an embedded Survey123 form. When submitting a new record, it does the correct calculation. It's when editing an existing record through a dashboard. This process has worked for two years up until last week when all of sudden it stopped. 

I have also opened a ticket with Support to see if they can help. 

[ZhifangWang]

@ISP_graynic ,

In addition to contacting the Esri Support team, if you can reproduce the issue with a minimal XLSForm file, please share it with us for a quick investigation.

[ISP_graynic]

Attached is an example of a minimal version of the xls. The field with the issue is "hasbeenprocessed". You can see the calculation and default is set to 0. This works on the initial submission, however through another process this value is often changed to 1. After it is changed to 1, when the form is resubmitted with the calculation of "0", the field stays at 1 and does not change to 0. 

[ISP_graynic]

It looks like it isn't related to the specific form and feature class because I just created a whole new form and layer and have the same issue. When changing "hasbeenprocessed" to 1 and then resubmitting the form it should change "hasbeenprocessed" back to 0 but it stays at 1 (even though the form shows 0 automatically). I also tried it and was able to replicate the issue in both ArcGIS Portal and ArcGIS online.