When publishing my existing surveys from Survey123 Connect v2.3 I am now getting this error (see below). Is anyone else getting this error and know what to do about it?
Hi Joe, the problem is the pulldata('@geopoint') function, as you can read here: https://community.esri.com/thread/198665-publishing-error-xform2webform#comment-702632
Does your survey contain external selects? We are currently investigating some issues with publishing surveys containing external selects with 2.3 which appear to be reporting the same error you have identified above.
Hi Philips, my survey doesn't contain any external select.
You can find my survey XLS in this post:Survey123 (v. 2.3.24) - Issue publishing code 401
My survey is quite simple and does not contain “external selects” – see attached.
The original survey was not publishing with v2.3, so I backed up and deleted the survey form folder from “My Survey Designs” and created a new blank “Public Affairs” survey using Connect 2.3 thinking that changes were made to the default XLSForm and associated files. The new blank PA survey did successfully publish to my ArcGIS Online. I then renamed the new blank “Public Affairs.xls” survey file to dismiss it and added my original v2.2 “Public Affairs.xls” file to the folder. I deleted the successfully published blank PA survey and associated *.iteminfo file. I opened Survey123 Connect, opened my Public Affairs survey, then I clicked on the “Update survey from SLSForm Spreadsheet” button to get the current XLSForm. Publishing failed with the 401 error.
Thank you for your time,
I removed the pulldata('@geopoint') function from my form and that fixed my problem!!
Thank you for your input.
Yes, as Stefano points out, there is currently an issue with pulldata('@geopoint') and external selects in the updated Survey123 API. This will hopefully be resolved shortly, once complete we will update you so you can add this question type back into your survey.
This issue appears to be fixed. Can anyone confirm resolution?
This issue should now be fixed:
Yes, it's ok now
Retrieving data ...