PRO TIP: by default bubble passes list of text delimited by a comma then a space , . They don’t do it by default on a list of uniqueIDs (things). To keep things standard it’s best to set your own rules of a comma followed by a space to delimit uniqueID
I’ve seen post about getting a list of options from URL, and an array of things from URL. Thought this would help. Option sets work the same as text described above.
@brad.h I think “Unique ID is in” is new functionality. In the past it was only = or <>. Now that we can use “contains” logic, this becomes a lot more straightforward! Thanks for sharing.
Bubble doesn’t officially support a list of Things in the URL parameter . I’m wondering if I should revert back to custom states before going too far down this path.
I asked bubble support “why”. I’ll update this thread when I know more.
Yes you probably should not use URL parameters for a List UNLESS the max count of the list is ~3ish AND the filters for the list have a high WU consumption.
It’s hard to say without understanding what the most pressing of the reasons are but unless you’re are sadomasochist (not that there’s anything wrong with it!) you most likely don’t want to use URL parameters.
Custom states are not the only option, but it all depends on the use case and your motivations: point_up:
I suppose the benefit of search filters that pulls from the url (which incidentally what amazon, airbnb do etc) is that if you forward a url address it will pass on the saved searched filters - something that you could not achieve with custom states.
This airbnb url represents a filtered search with a list of property types included in the search
Exactly. My use case is an email with a link to the filtered results. I ended up not going this route since bubble does not support list of things in the URL.
That doesn’t mean you can not set up your URL parameters to be a list of things and work with it properly. All it means is Bubble doesn’t have a feature to make it easy ‘out of the box’, which is why I had to post the tip linked above in 2020. It works just fine with no issues.
Once it is setup properly there are no more aches or pains if you set 3 or 20 items in the list.
This is partly why I set out in 2020 to get this functionality to work. I also used it for saved searches and to make the UX awesome, so when a user clicks onto a search result and then navigates to the ‘product’ page, afterwards, if they use their browser back button, they are back on the search page with all their filters still selected (something most every single user of an app would expect)
Another reason for this is because custom states are temporary, so once your user refreshes the page they are all lost, whereas the URL parameters are still there.
It is not. It is just a solution to a problem that Bubble doesn’t provide an easy to use native solution. It uses all Bubble native features and is in no way (as far as I know at the moment) of being deprecated because of some change Bubble makes, as it doesn’t do anything to ‘trick’ the system.
I got it working, this post is a “TIPS” category. I was sharing with everyone how I did it.
Shared the editor and demo link too.
I’m trying to optimize for reliability and minimal maintenance. I’m probably too conservative…but when I saw bubble does “not officially support” I ended up abandoning. But still wanted to share the tip with everyone.
. I’m wondering if I should revert back to custom states before going too far down this path.
! What’s the reason for 3 max?
