The searchbox has two modes for search options: static and dynamic. Static works fine, but dynamic is not truly dynamic. You have to use the “Do a Search for” action, and can’t do anything else to it afterwards. It would be really nice if we could specify a list of options in a truly dynamic way, similar to everywhere else in the app.
Example for usage:
I want to allow the user to choose a “type” from a list of predetermined types (stored in an option set, for example). However, the user can also specify their own “type” if the predetermined types are not satisfactory. They can do this by not selecting one of the types on the list and just typing their own. If they do this, however, we want that type to be stored somewhere so that the next time they choose a type, it appears alongside the predetermined types. Thus the searchbox would needed a truly dynamic option: “Get an option set -> Type Options -> All options :appended to Current User’s Types”
A user can create “tools”, which have a name and a link. They can also categorize those tools. Those categories can either be one of our predefined tool categories or one of the custom categories they specified.
Of course, there are a very large number of potential use cases. Basically any time you want to search on a subset of data, but can’t easily store the information that you use to determine the subset as a searchable field. Or any time you want to search for an item from two data sources.
I also have this need very often of having a searchbox work on option set.
The “dropdown” works on option sets, but it doesn’t support “auto suggest”, which is critical, as otherwise user has to scroll down through full dropdown to locate what they want.
My best workaround Ive found for this issue is to use the multiselect dropdown component with a limit of 1 possible selection. That solves most cases you need the searchbox for.