52

you can just use

all options > filtered to > option param = get data from url : first item

when using the param in an option instead of the display in the url

this lookup works will for other places in the app also - I use it for tabs, dropdowns and filters a lot.

for instance - user wants an “all” option for an option set.

you could add “all” as an option but then it becomes a filterable value and the searches will fail since data will not have all but instead have “todo” or “complete” (example)

you could add conditionals to do a search without using the option filter when the value is “all” but that becomes messy with several options used in a search…

you could save the option to a state and add conditions to save empty if it is “all” - therefore the search filters correctly still since all will be empty

or you could change the dropdown to text “all > converted to list > plus list > list of options display”

then in the search you just use constraint option = all option > filtered to > this option display = dropdown value > first item" - I usually prefer this option since it is the simplest

I’m sure there are also other ways to do it. but this just shows how flexible bubble is and that there are many ways to achieve the same outcome and it largely comes down to experience and preference.

what also is a great solution for a small app is often a terrible solution for a large app. And as your app scales you will often need to rebuild parts of it to handle the greater scale.

ie an option set for file type
works well when there’s 10 or so types in a small app
works less well when there’s 50
works horribly when there’s 100 (better as data than an option)

I recently had to change an option set for file type to data in an app because it had outgrown the option - but it was the right use of the option initially (only had 3 types), it’s just that the use scaled beyond it little by little and it eventually had 60 types.

could I have foreseen it getting to 60 types? maybe. should I have used a data instead of option initially - maybe. But I made the choices at the time given my best guess of it’s use in the future - which served it well for about 4 years… but now 4 years later it needed a new solution.

The same applies to reuseables - you may not need them yet. But one day you might. You don’t need to create hundreds of reuseables for everything on the page - but if you end up rebuilding the same things over and over… well maybe think about reuseables.