Survey123 web app functionality

[JasperRomero]

Hello Community,

I'm hoping someone can help me understand exactly what functionality is available to Survey123 in a web app. I am trying to configure a self-submission form for the general public to add themselves to a Community Yard Sale web map. To do this, we want to use our Locator service to assess whether the address they submit is within City Limits. 

I have the City Limits as a hosted feature layer polygon that is shared publicly. Our Locator is on Portal, but is apparently publicly available through AGOL (not sure exactly how this works, maybe AGOL references the Portal service on our enterprise server? but other folks say it's public). 

I had initially used XLSForms to set it up so that first users drop a pin on a geopoint question, then were prompted to edit a text address field whose default value was the address obtained by reverse-geocoding the point if necessary (i.e. if the reverse geocode gave the wrong street address for their location). This worked great in the Survey123 Connect preview, but broke on the web. I have read that reverse geocoding may not be supported at all on the web version - can anyone confirm or deny?

Additionally, I had been using calculations and constraints to assess whether the pin dropped in the geopoint fell within the city Boundary by querying the public hosted feature layer. I don't think I even had this working correctly in the Connect preview - my goal is to configure the survey so that if the point is outside city limits, the response is not accepted and an error message shows, reminding the user to put the point within the City. Is this possible at all? Can it be configured in such a way that it will still work in the web app of the survey?

Thanks in advance for any suggestions, clarifications, etc.

[StephanieM1]

Hi Jasper,

There is a current enhancement request to "Implement the functionality of Reverse Geocoding in the Survey123 web application." 
This is currently In Review.

This Survey123 documentation states that features using the pulldata("@geopoint") properties are not supported in the web app.

That same link also provides some information on constraints. This Esri Community post also has some good info.

Survey123 Connect seems to have the most options for what you are trying to do.

[JasperRomero]

Hi @StephanieM1,

Thanks for the response - based on that information, it sounds like what I'm hoping to do is not possible if all respondents will be filling out the survey on the web. 

Is pulldata fundamentally impossible for web app survey responses, or just not implemented yet? 

I have been using Survey123 Connect to configure the survey, but if I'm understanding correctly the issue is that features I configure there, which work correctly when previewing responses in Connect, will be broken on the web. This is pretty frustrating - it would be great if Connect would make it a little clearer what will fail under certain conditions, instead of showing things working when they won't necessarily function correctly under all use cases. 

[StephanieM1]

Yes, right now it is a limitation in Survey123 Web.

Not all pulldata functions are impossible for web app survey responses, though. For example, pulldata("@layer") was introduced in Survey123 Connect 3.16, so this one will work in the web app if it is published with 3.16 or later. 

I understand this can be confusing. If you have any questions regarding if something is expected to work in the web app and you are unable to find it in documentation certainly feel free to open a case with technical support and we will be happy to help!