[Resolved] Bug with ':plus item' function?

[romanmg]

@josh

Another thing to keep in mind is that when you use dynamic data such as the result of a search as one of the constraints in a search, we can’t start the second search until we finish the first search, because we don’t know what the correct constraint should be. If the first search only returns a small amount of data, that’s not a big deal, but if it returns a lot of data, and you chain multiple searches together like that, you can create extremely slow pages, because we have to evaluate it all one-at-a-time, instead of in parallel (which is what we normally try to do).

@emmanuel

Workflows don’t have a sequence, they get run at the same time. So if you have 4 workflows that are triggered by a click on a button, all of them will run at the same time when the user clicks on the button.

So, there are a few discussions about this around the forum regarding sequencing, when Bubble waits to run an action, when it doesn’t, etc. Apparently there are a few factors. @mishav studied the sequence closer than I did, so there might be something more going on than my theory, but I think this is something you’ll need to test more, especially when these lists start to grow on you and other stuff is happening on the page.

Other than that, I read your use case, and I feel like you can restructure a bit. Instead of a list of yes/no’s, why not 1 yes/no for if the User can host 1 type of dog, and another yes/no for hosting 2nd type of dog? If they can host both, both will be yes. If only one, then only one will be yes. The default search would not include a constraint on either yes/no fields to include everyone. If the user’s profile says that his dog is not fixed, then the search would include a constraint to those whose “will host not fixed” yes/no field = yes.