I have multiple Choice components that have drop down options for things like Event Type, Time Zone, Country, Social Platform.
If I search a Choice Component that has enough options to enable a Search at the top of the list of options (around 16+ options, eg. Country and Time Zone have over 100+ options), when I go to Choice components that have just a few options and no search (eg. Event Type, or Social Platform), the options are pre-filtered by the search entered in the Choice component with search, except you can’t clear the search. You have to go to the original Choice component where you started the search to clear that search and re-enable the options in the other Choice components.
This caused users I tested this with to think this was a bug. They thought the app was broken, and I did too. But after testing I found it’s a flaw of the search not being cleared from the other Choice components.
Note, in the Glide Editor, this is not a problem. The Choice Components work as expected, always showing all options even if you’ve searched one of the Choice Components. The problem only seems to exist outside of the Glide Editor.
Suggested fix: Always clear the search after user exits the Choice component. Or always have the search visible on all Choice components so the user can clear the search if it’s carried over from other Choice components
PLEASE FIX as this is blocking me from releasing this project. It’s critical that users are able to see all options in the Choice menus.
Hi.
I found a similar issue today, I have some tabs setup with the visible data only showing data created by the signed in user only, with tab filters also set to only show signed in user data.
This all works fine however if I add a ‘In-app filter’ and use it, the filter displays all records and not just the ones for the signed-in user.
I have currently turned off all of the ‘in-app filters’ to avoid any issues.
Hi.
I found a similar issue today, I have some tabs setup with the visible data only showing data created by the signed in user only, with tab filters also set to only show signed in user data.
This all works fine however if I add a ‘In-app filter’ and use it, the filter displays all records and not just the ones for the signed-in user. I have currently turned off all of the ‘in-app filters’ to avoid any issues.
Thanks for the suggestion, but the problem is not in a List or Inline list view. The problem is within the Choice Component in a form. When you have enough options (about 16+), a search field appears for the end user using the form. When they filter that Choice Component, the search is saved and applied to all other Choice Components in the same Form. And if the other Choice Components have just a few options (around 15 or less) where no search box appears because it’s just a few options that can fit on screen, they are unfortunately filtered by the search you previously entered in the Choice Component with MANY options. To the end user, this hides all options that don’t match the previous search, until you clear the search from the original Choice Component.
I was able to duplicate @ray_d’s same issue in staging (assuming the production version is the same). Doesn’t seem to be a problem in the editor, but is a problem with published app. I only tried this on my desktop chrome browser. Doesn’t seem to matter if you are inside of a form or not, but on the published version, if you have a choice component with the search bar showing and you type in a search, then that search takes affect on all other choice components. Opening another choice component that doesn’t have enough rows to show the search will still have the search applied from the previous choice component. I think the main difference between the glide editor and a published app is that the search bar retains it’s value on a published app. For example, open a choice component that shows the search, type in any value, then close it and reopen it. In the Glide editor, the search box clears itself out. On a published app, that search bar will still be filled from the previous value you typed. @Mark
And yes, what you described is indeed the same problem I was having. If you have a mix of Choice components on the same form, where some have 10+ choices, others less than 10 which means no search box, searching one Choice component will apply the same search to the others, and since some have no search boxes, it’s hiding the options making it seem like it’s broken.
