Experience Builder Filter dropdown truncates species list

[GeoffreyMason]

Hello,

I using Experience Builder with a filter to chose what value (fish species) I would like to display.  Only the first half of the species appear in the dropdown.  If I type in a species I can get to the ones that are not visible.  However, I would like the whole species list to show.  

Does anyone have a work around to get the whole list of species on the dropdown?

See images below.

Thanks!

[Laura]

Mine continues the list once you keep scrolling down. 

[GeoffreyMason]

Interesting.  Mine displays 34 values but won't scroll any farther down the list.

[Laura]

What does your whole exp builder look like?

[GeoffreyMason]

[Laura]

What version of enterprise or are you using agol?

[GeoffreyMason]

AGOL

[Laura]

I checked the rest of my layers. Looks like the majority keep going as I scroll down but I did come across one that didn't. Same field 'type'. Not really sure of the difference for why it wouldn't. I could see the full list in live view and under the view published app.

[BenGan22]

Hi @GeoffreyMason  and @Laura,

What I discovered regarding this topic today is interacting with the filter widget via the dropdown list in "Live view" results in a truncated list that doesn't show the full list of options. A workaround is to use the "Pill selector" if the list is not overly long. For me, the "Pill selector" input style displayed the full list of options.

The other thing to check is to check whether the full list of options appear in the "Preview" app or the published app. For me, the full list of options appear in the "Preview" app or the published app, just not in the "Live view" when editing the app.

Hope this helps!

[AustinAverill]

I run into this once or twice a month, in my case it appears to be a bug. For me specifically, I have encountered this issue where once a filter has been applied, the list is then truncated when attempting to access it again. This persists until browser cache is cleared and a new session is started in the application. However, the issue occurs immediately when a filter is applied again - 

My current work around is to use the "Pre-Defined" option for my drop down choices and then manually enter in each value to select. This is clearly not a great option in the event you have data changing or what have you. But if your species values are pretty consistent or not subject to change, this is a 100% work around.