# Different filter operator options for the same field

**URL:** <https://community.weweb.io/t/different-filter-operator-options-for-the-same-field/7116>\
**Category:** Ask us anything\
**Tags:** filter, supabase\
**Created:** [February 19, 2024, 3:01pm UTC](https://community.weweb.io/t/different-filter-operator-options-for-the-same-field/7116 "2024-02-19T15:01:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Larry](https://avatars.discourse-cdn.com/v4/letter/l/47e85d/32.png) [@Larry](https://community.weweb.io/u/Larry)\
**Post date:** [February 19, 2024, 3:01pm UTC](https://community.weweb.io/t/different-filter-operator-options-for-the-same-field/7116/1 "2024-02-19T15:01:30Z")

</div>

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?

 ![filteroncollection](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/8/8c4e659b5c1bbfc9fada6ff32770d9747d950fbe.png)

vs.

 ![filteronelement](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/2/271e4a2502e699c76839ca8d2af13d58f9089cb0.png)

---

<div class="post-metadata">

**Author:** ![luka](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/luka/32/1571_2.png) [@luka](https://community.weweb.io/u/luka)\
**Post date:** [February 22, 2024, 9:26am UTC](https://community.weweb.io/t/different-filter-operator-options-for-the-same-field/7116/2 "2024-02-22T09:26:50Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Larry](https://avatars.discourse-cdn.com/v4/letter/l/47e85d/32.png) [@Larry](https://community.weweb.io/u/Larry)\
**Post date:** [February 22, 2024, 1:38pm UTC](https://community.weweb.io/t/different-filter-operator-options-for-the-same-field/7116/3 "2024-02-22T13:38:26Z")

</div>

This is a dynamic collection from Supabase. In this case, the ‘person’ object is the result of a join using the Advanced field selection.

---

<div class="post-metadata">

**Author:** ![luka](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/luka/32/1571_2.png) [@luka](https://community.weweb.io/u/luka)\
**Post date:** [February 22, 2024, 1:39pm UTC](https://community.weweb.io/t/different-filter-operator-options-for-the-same-field/7116/4 "2024-02-22T13:39:23Z")

</div>

Yes, when using filters in Supabase collection settings, you are actually filtering on the back-end, hence why the different options

---

<div class="post-metadata">

**Author:** ![Larry](https://avatars.discourse-cdn.com/v4/letter/l/47e85d/32.png) [@Larry](https://community.weweb.io/u/Larry)\
**Post date:** [February 22, 2024, 1:50pm UTC](https://community.weweb.io/t/different-filter-operator-options-for-the-same-field/7116/5 "2024-02-22T13:50:17Z")

</div>

Got it. Thank you for shedding light on this.
