Howdy,
I'm brand new to Survey123. I'm testing my first survey on my windows computer.
I published my feature service and secured it using this article How To: Create Survey123 for ArcGIS surveys that connect to non-federated ArcGIS Server services. I do not have Portal, we use ArcGIS Online. The Feature service was protected, and the password saved in the connection.
The survey was created using Survey123 Connect Vers. 1.10.43. I generated the XLSForm by logging into my Organization and using the Create Survey function. I made certain that the submission URL and form_id were correct ( I followed an example from a previous form).
The Survey was published just fine, stating that the existing survey will be updated to use the custom feature service (and link). The links work, I'm able to log into the correct feature service.
I download the survey into my survey123 app on my android device. downloaded fine, I was able to fill it out.
BUT.
I get a Code 500 (Unable to complete operation)
The submission URL and form_id worked in generating the survey. However I'm now wondering if the permissions are somehow getting lost when the survey attempts to create a new feature?
This is a very unhelpful code as I am unable to pinpoint exactly what's going wrong.
Hi Erick,
In looking at the screenshot, the form_id is "SWM Service Requests Survey123", correct? That is the name of the layer in the service that is the main form? If so, there is a known issue with layers that have spaces in their name.
That's good to know! I'll change the layer name and republish.
I renamed the layer without spaces or special characters in my original mxd, republished, re-secured, and remade the survey. I am still getting the same error code 500.
Can you forward me the XLSForm?
Sure. How?
Either attach it to a post (using the advanced editor) or e-mail me - jtedrick <at> esri.com
thank you sir, email sent
Hi James,
does the known issue also contain points and underlines? For example. The name of the layer in the service is "gis_fach.test".
Regards
Hi Stefan,
I haven't tested points (underlines are fine)- points are indicative of database schema part breaks, so I could see that possibly causing issues.