I’m using merged with to get a limited list of items and append another list of items. The way I structured it, the result is only the result of the second list. My situation may be the same as this one, but it was closed before being resolved: [image] "merged with" function not wo…

Your lists are the same. Bubble dedupes non-unique items. It’s easy to forget that at times. (I made the same mistake recently and posted about it here — was totally stumped until Support reminded me about it.) [image] A Very Odd Bug in :merged with Operator Bugs Just fo…

Another way of saying this: Remember that Bubble lists ARE NOT JavaScript arrays, they are array-like iterable entities with their own rules and methods.

Yes. I believe I encountered the same problem here: [image] Possible Bug for Sort of Merged Search? Bugs Thanks for the recommendation! By messing around some more with this, I realized that it’s not a sort problem. It’s more of a merge with unexpected functionality. Al…

You’re asking about: search (1) for Thing:merged with search (2) for Thing:sorted by Created Date ? Yeah, the way this works is: Searches 1 and 2 are performed. These two lists become the operands to :merged with. The merge returns the merged list. Regardless of the source of the 2 operand l…

Thanks for jumping in, Keith. Perhaps I’m misunderstanding your answer. The filters on each side of the merge are actually different. That’s not obvious in the image I provided. Here’s the first filter: [image] Here’s the second filter: [image] What I’m going for is two items with a due date…

Laurence, read my reply to @dserber and see how the order of operations works here. He was doing: search (1) for Thing:merged with search (2) for Thing:sorted by Created Date You are doing: Some_list_1:filtered(1):items until #2:merged with Some_list_1:filtered(2):items until #2 Here’s how that…

Thanks, @keith . Based on your recommendation, where I’m stuck now is that I don’t know in what event to trigger the actions to set the two custom states. The whole realm of “non-standard” events is a new one for me. This is what I’m looking at and I don’t see what I can choose to trigger an event …

Thanks! @keith I never understood exactly why the solution of separating the two lists into custom states and then combining them did the trick for me but I suspected it had something to do with the order of the operations. It does seem counter intuitive to me and I think @laurence is in the same…

Yeah, just to be super-clear: You can think of any operator in Bubble… whether it is a mathematical operator (+, -, /, *)… a boolean/comparison operator (“is”, <, >, “contains”, “is emtpy”, “is not empty”, “is not”)… an “arrow” operator (“<-min->”, “<-max->”, “<-range->”)… a “colon” operator (“…

@dserber You are correct we don’t have a combine operator that preserves dupes but doesn’t touch database yet but you can currently merge with no overlap by saving ListA :intersect ListB to a custom state and then :merged with :filtered intersect does not contain this number […

Merged with does not always work

Bugs

dserber June 19, 2019, 10:40pm 4

Yes. I believe I encountered the same problem here:

Any thoughts? @keith

Topic		Replies	Views
:merge with, how could I merge 3 searches? App Organization	16	6187	November 20, 2023
Using ":filter" operator after "merge with" on RG datasource Questions	18	1421	May 9, 2018
A Very Odd Bug in :merged with Operator Bugs	1	1053	May 23, 2019
Merge with and sort Database	10	2797	September 27, 2022
Merge a list with empty list, results empty list Bugs	4	1065	October 18, 2018

Merged with does not always work

Related topics