Using Cascading Choice Lists in Survey123 Connect

BrandonCranfield

Hello all!

I am using cascading choice lists in my survey built in Connect (v3.20.63). Noticing some interesting behavior when publishing the survey to portal (v11.3). The feature layer treats the first choice list as a coded value domain, but all related subsequent choice lists are treated as text input fields. We need the subsequent lists to be treated as coded value domains as well in order for the modify/edit capability to present those fields with dropdown choice options. This is in an attempt to remove as much human error from the process as possible.

Any suggestions?

abureaux

• Publish from Connect without the cascade settings so that all select_one and select_multiple are treated the same. Then add it in afterwords.
• Publish from ArcPro with domains and then build the survey in Connect on top of that, adding cascades at that point.
• Don't edit directly in a web map, and instead use an embedded survey or other such process.