Make Survey123 Connect and the Survey123 Web App Intercompatible

373
0
07-09-2025 07:36 PM
Status: Open
Labels (2)
Sherbert1848
Occasional Contributor

Currently, Survey123 Connect forms are not editable in the Survey123 Web App. When I publish a survey in Survey123 Connect, I get this message when I open it in the Web App:

"This survey was published with Survey123 Connect. Questions cannot be modified in the web designer. The sample below is for illustrative purposes only and does not represent your actual survey."

This is a ridiculous flaw that basically means Survey123 and Survey123 Connect are completely different products; the only thing that makes them similar is that they perform a survey creation function. All I really want is to be able to write my questions and response options in an XLSX, upload it to the Web App, and design the rest of it there. Instead, I have to write out my questions and figure out how to make Survey123 Connect do what I want it to: I want to separate things into different pages, change the themes, add graphics, and add question logic. These are pretty simple functions that would take more time to learn to do in Connect than it would take to complete in the Web App. However, writing the questions in the Web App is a terrible pain. So I have to choose: go through the pain of writing questions in the Web App, or work with a clunky design system in Connect and ONLY Connect...

So, my idea is a simple concept - fix this. I should not have to choose between these two methods of work; Survey123 Web and Connect should complement each other. They don't need to be identical - there are things I can do in ArcGIS Pro that I can't or don't do in ArcGIS Online, but I don't have to choose one without the option of using the other when it's appropriate. If I upload a survey in Connect, I should be able to edit it on the Web App and vise versa. However, if one were to prioritize compatibility aspects, the Web App should absolutely have an XLSX question upload option.

I truly hope that my predicament highlights the absurdity present in this lack of compatibility, and I hope Esri decides to take action to improve their product.