topic Re: Make user only select the select one/multiple button labels in ArcGIS Survey123 Questions

Make user only select the select one/multiple button labels

Vincentvd — Wed, 04 Jan 2023 12:55:36 GMT

We have made a large survey for the survey123 app that contains select one/multiple questions. The problem is that while scrolling on the right of the screen, the user sometimes accidentally changes the selection of the select_one/ select_multiple questions because the trigger area is extended all the way to the right. Is there a way to only limit this to only clicking on the checkboxes or labels?

The problem is that depending on the answer, other questions appear. The entered values of a question are deleted when questions are hidden again when people accidentally click an option during scrolling.

Re: Make user only select the select one/multiple button labels

DougBrowning — Wed, 04 Jan 2023 15:02:18 GMT

I posted this a few years ago but never got anywhere on it. https://community.esri.com/t5/arcgis-survey123-questions/tap-area-for-radio-buttons-is-now-too-large/td-p/1008062

and here https://community.esri.com/t5/arcgis-survey123-questions/can-i-limit-the-area-of-selection-for-select-one/td-p/878025

I had the same problem where users filled out a ton of data then when scrolling to review it, then they hit the Not Collected button on the section by accident and then all their data was gone.

This was all using relevant since that was all there was at the time. Then body::esri:visible came out and I changed to that. Then all it does is hide the questions but retains the values vs changing all to blank. It was also a bit more stable. Of course it does work a bit different and it does mean they could add data then say Not Collected but we felt it was worth it.

You can also flip the choices around so the Yes or something is on the right vs the left.

Hope that helps

Re: Make user only select the select one/multiple button labels

Vincentvd — Thu, 05 Jan 2023 08:18:08 GMT

Thanks for the tip. I wasn't aware body::esri:visible could be used for that. This seems indeed like the best solution for now.