survey123 issues post November update

[AmeWunderle]

Hi all,

After the November update, a number of our surveys had issues with submission from the field app. My coworkers would simply get an error message that showed "Send error" with the dreaded red exclamation point on top. 

After testing this myself, using the logging option in the field app, I noticed that it didn't seem to like any of the fields where I used the concat() calculation. Once I removed these (thus making my surveys a little less useful), the survey submitted in the field app after publishing the changes (In the error details for the fields was the text: "Unable to apply edits"). 

Was this calculation option deprecated? The place I use it most often is to link my surveys together, calling one survey from the current & auto filling the fields in the second survey like creating a workforce assignment from a current inspection.

Has anyone else experienced this?

Thanks,

Ame

[ChristopherCounsell]

Unable to apply edits is a generic error. It could be a result of feature service issues from earlier in the week as part of the ArcGIS Online update:

https://status.arcgis.com/

Or it could be tied to the concat expressions themselves (e.g. string is too long for the field, but I'd expect a different error).

They did make some changes to the calculation behaviour but I can't see anything to suggest they removed concat(). Sometimes the fixes they make cause errors when things start behaving 'correctly'.

Can you share your XLSForm and confirm the versions of Survey123 Connect and the field app?

[A_MN]

@ChristopherCounsell 

We are experiencing the same issue after November update.

[ChristopherCounsell]

Can you share the xlsform or the calculations you are using?

I understand the issue may be tied to the update but it's difficult to help without more information.

There have been fixes in the past that caused users surveys to break, but it was because of the survey design. E.g. hidden required questions.

We used concat() and do not have reports of this issue. I'm curious if it's specific to your surveys or if this is something that could impact us as well.

[A_MN]

Below is my calculation. After the November update, the error occurred. I changed the bind::esri:fieldType column from connect to null, which resolved the issue temporarily. However, the same error still occurs in some surveys. I’m not sure what is wrong.

concat('<a href="arcgis-survey123://?itemID=929482f61093494aaeb8b6fa34da4952', '&field:BEN_site_visit_code=', ${site_visit_code}, '&field:BEN_location_province=', ${location_province}, '&field:BEN_location_district=', ${location_district}, '&field:BEN_mon_date=', ${monitoring_date},'">Interview #1 / 1 مصاحبه 1 / مرکه </a>' )

[AmeWunderle]

Hi A_MN and Christopher,

After tinkering with my surveys, I realized it wasn't necessarily the concat issue, but the use of it to create an <a href> link to another survey exactly as A_MN is doing above. The error message I saw indicated that there may be issues with a html link.

To fix this, I changed the question to a text field, not a calculate field, then updated the alias directly using the data entered without the extra apostrophes and commas needed when making the concat field. 

<a href="arcgis-survey123://?itemID=929482f61093494aaeb8b6fa34da4952&field:BEN_site_visit_code={site_visit_code}&field:BEN_location_province=${location_province}&field:BEN_location_district=${location_district}&field:BEN_mon_date= ${monitoring_date}>Interview #1 / 1 مصاحبه 1 / مرکه </a>