Does anyone know the reason why I see different options for operator for the same field when setting the filters on the collection itself vs. in an element that is bound to that collection?
vs.
What kind of collection are you using? Sometimes the Filter option is actually a back-end filter, meaning it’s following the principles of the provider it uses
This is a dynamic collection from Supabase. In this case, the ‘person’ object is the result of a join using the Advanced field selection.
Yes, when using filters in Supabase collection settings, you are actually filtering on the back-end, hence why the different options
1 Like
Got it. Thank you for shedding light on this.