Issue with Select One Question Autocomplete in ArcGIS Survey123

[arc_ticodex]

I've been working with ArcGIS Survey123 and encountered a potential bug related to the "select one" question with the autocomplete appearance.

In my survey, I have a lengthy list of domains for the autocomplete appearance. However, when scrolling down through the list, I've noticed that the dropdown unexpectedly closes before reaching the end. This prevents me from selecting options beyond a certain point in the list.

Has anyone else experienced a similar issue, and is there a known solution or workaround? I would appreciate any insights or advice on how to address this problem.

[AFangman]

That looks very frustrating!

I do not think I have an answer for you. Rather, I have a question.
What system are you viewing this survey on?

I do not have this issue using Survey123 on web, mobile app, nor Connect. They all have a different style list than what I see in your video, so my guess is that it is a bug from another version of Survey123?

[arc_ticodex]

Hi @AFangman!

Thank you for your response and for taking the time to consider my issue. I'm currently accessing the survey through an embedded link in an Experience Builder page.

Upon further investigation, I conducted tests on four surveys, each featuring similar questions with a list of species and their corresponding Latin names. Interestingly, the two surveys I embedded in Experience Builder Developer displayed the list correctly. However, the two surveys embedded in Experience Builder Web exhibited the issue I shared in the video. It's worth noting that all four surveys function as intended when accessed through Survey123 on the web.

Considering these findings, my hypothesis is that the discrepancy may be related to the version of Experience Builder within our enterprise environment. 

Thanks again for your help! If I have any news, I'll be sure to share. Thank you!

[AFangman]

That makes sense. I have an issue with a survey that also works fine on the web, but has an issue with a calculated field on the mobile app. Looking for information on this error lead me to your post. Seems like there are some kinks for ESRI to work out between different methods to access a Survey123 survey. We do not have an Enterprise environment yet otherwise I would try this Experience Builder as well as our survey has about 50 common names for trees and I would be curious to see if I would encounter the same issue.

[DustyJordan]

Hi @arc_ticodex ,

Did you ever figure this issue out? I am currently experiencing something very similar. When I open the dropdown menu it immediately closes though, before I get a chance to scroll it or hardly even see it. 

So far it is only occurring on a single select_one field and I cannot figure out why considering there are other select_one fields that are pretty much identical (except for the list) and those are working fine.

[AnthonyJonesRSK]

I've also just run into this issue and it appears to be a problem with with the autocomplete appearance when a survey is embedded in experience builder as arc_ticodex points out. Does anyone know if this has been registered as a bug or if anyone from the Survey123 team has looked into it? It potentially means I will have to completely rework how my survey works and is proving to be fairly frustrating. Thanks

[Ruth_JiatengXu]

Hi @arc_ticodex  @DustyJordan @AnthonyJonesRSK 

Apologies for the late response. Could you please provide more details about your survey or send the XLSForm to me at jxu@esri.com so I can investigate further?

1. Is it a autocomplete question or a dynamic choice list (pull choice from a layer)?

2. How many choices are included ?

3. What version of survey are you using? (Press F12 to open the browser developer tool, you can see the survey version under the console panel)

4. Which browser are you using when you saw this issue? 

Thanks,

Ruth

[AnthonyJonesRSK]

Hi Ruth,

Thank you for your reply on this it's much appreciated.

I've done a bit more testing on this and I think in my case the issue is being caused by the layer refresh settings in Experience Builder. I initially created a test survey in RSK Connect with a select_one_from_file question pulling data with a csv and with the autocomplete appearance applied. I then embedded this in Experience Builder to see if I saw the same issue but my drop down worked fine. I went back and reviewed my original app with the issue and realised that my embedded survey was connected to a dataset, something I hadn't replicated in my test. I made a copy of my old app and began changing some of the settings including the refresh settings which had been configured to honour the layer settings, which I assume are those I'd configured in my web map. After turning auto refresh off my drop down now appears to behave as expected. The only further oddity with my map is that I'm using feature layer views and found that the refresh settings on one layer appeared to affect a separate view layer in my app. I will see if I can create a simpler app of this next week to replicate the issue that I may be able share publicly.

If further testing confirms the refresh rate to be the issue is this something that could be looked into? Unfortunately I need my layers to refresh so users see changes made to the data so turning the refresh settings off isn't really an option. My autocomplete drop down has over 300 records in it so I also can't turn the autocomplete option off either as it then becomes very difficult for our users to navigate through the options.

And just to answer your last two questions my surveys have been published using Connect version 3.20.63 and I'm using Chrome.

Thanks

Anthony

[Ruth_JiatengXu]

Hi @AnthonyJonesRSK ,

Thank you for the investigation. I was able to reproduce the issue and have reviewed it with our developer. When the other experience widget refreshes, the survey question input box loses focus, causing the dropdown list to disappear.

We will collaborate with the experience team to find a solution to this issue, and I will post the update to here.

Thanks,

Ruth

[AnthonyJonesRSK]

That's great, thank you so much for looking into this Ruth, it's very much appreciated.