# WeWeb Unify: Table View filters of Supabase Tables are off

**URL:** <https://community.weweb.io/t/weweb-unify-table-view-filters-of-supabase-tables-are-off/21490>\
**Category:** Ask us anything\
**Created:** [August 1, 2026, 12:45pm UTC](https://community.weweb.io/t/weweb-unify-table-view-filters-of-supabase-tables-are-off/21490 "2026-08-01T12:45:11Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Janus](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/janus/32/16552_2.png) [@Janus](https://community.weweb.io/u/Janus)\
**Post date:** [August 1, 2026, 12:45pm UTC](https://community.weweb.io/t/weweb-unify-table-view-filters-of-supabase-tables-are-off/21490/1 "2026-08-01T12:45:11Z")

</div>

Has anyone noticed that when you use Supabase in WeWeb Unify, and create table views of your data, the filtering logic is off. I am consistently getting all rows or no rows and I specifically have the “Ignore if empty” toggle off.

I have two parameters (scope and scopeID) and I am creating conditional groups around them. The scope can be rep/nurse/all/none, whereas the scopeID is the ID of the specific rep/nurse.

The filter is simple:

- If scope is all, show all rows,
- If scope is none, show nothing.
- If scope is rep, show only the rows where rep\_id = scopeID
- If scope is nurse, show only the rows where pnp\_id = scopeID

I have it set up in groups to achieve this:

 ![image](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/3X/5/6/56af1a7c3d2fb703971b436e5394a1c58bafd24d.png)

But it seems that irrespective of the conditions of the groups, they tend to allow the filters to still return all rows. This is also true for very simple filters:

If you have an ID and want to show only the record with that ID, You must define the filter for that ID, but you MUST also define the condition explicitly that if that ID is empty, the view must return an ID that you know is not in the db (I use “aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa”), otherwise the filter will always return all values. This work-around is however not working for the case I explained above.

I’d appreciate some help/tips if anyone has experienced this and has found a way around it. Thanks!

---

<div class="post-metadata">

**Author:** ![Msanders4](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/msanders4/32/13284_2.png) [@Msanders4](https://community.weweb.io/u/Msanders4)\
**Post date:** [August 3, 2026, 12:49pm UTC](https://community.weweb.io/t/weweb-unify-table-view-filters-of-supabase-tables-are-off/21490/2 "2026-08-03T12:49:53Z")

</div>

It might be doing this because you’re using “or” between each conditional group instead of “and”

---

<div class="post-metadata">

**Author:** ![TracyY](https://avatars.discourse-cdn.com/v4/letter/t/96bed5/32.png) [@TracyY](https://community.weweb.io/u/TracyY)\
**Post date:** [August 3, 2026, 4:20pm UTC](https://community.weweb.io/t/weweb-unify-table-view-filters-of-supabase-tables-are-off/21490/3 "2026-08-03T16:20:48Z")

</div>

@Janus I also have this problem, specially when I need “is empty” or “is not empty” and I already tried changing AND/OR and nothing.

This is my filter:

If `alcance` is empty (no filter selected) → don’t apply any scope filtering (show everything)

- If `alcance = "centro"` → only show banners where `centro_id` is **not empty** (banners assigned to a specific center)
- If `alcance = "corporativo"` → only show banners where `centro_id` **is empty** (corporate/fallback banners with no specific center)

 ![Captura de pantalla 2026-08-03 a las 17.03.34](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/3X/2/f/2f7a46fda676052d87349444ea4f8600287b9145.png)

- If I change it to AND → it shows nothing, doesn’t matter the value of “alcance”, even if “alcance” is empty (which means it should not apply the filter…)
- If I leave it to OR → it shows everything, doesn’t matter the value of “alcance”

---

<div class="post-metadata">

**Author:** ![Msanders4](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/msanders4/32/13284_2.png) [@Msanders4](https://community.weweb.io/u/Msanders4)\
**Post date:** [August 4, 2026, 10:32pm UTC](https://community.weweb.io/t/weweb-unify-table-view-filters-of-supabase-tables-are-off/21490/4 "2026-08-04T22:32:09Z")

</div>

@Tracy what would happen if you removed that outer conditional group and then simply changed it to “and”?

---

<div class="post-metadata">

**Author:** ![TracyY](https://avatars.discourse-cdn.com/v4/letter/t/96bed5/32.png) [@TracyY](https://community.weweb.io/u/TracyY)\
**Post date:** [August 5, 2026, 8:33am UTC](https://community.weweb.io/t/weweb-unify-table-view-filters-of-supabase-tables-are-off/21490/5 "2026-08-05T08:33:51Z")

</div>

No results, doesn’t matter the value of “alcance”

---

<div class="post-metadata">

**Author:** ![DanielL](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/daniell/32/13398_2.png) [@DanielL](https://community.weweb.io/u/DanielL)\
**Post date:** [August 10, 2026, 4:05pm UTC](https://community.weweb.io/t/weweb-unify-table-view-filters-of-supabase-tables-are-off/21490/6 "2026-08-10T16:05:01Z")

</div>

Hey @Janus @TracyY @Msanders4  
Just a quick note to let you know we are looking into it. We’ll share an update asap, most likely later this week or next.

---

<div class="post-metadata">

**Author:** ![DanielL](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/daniell/32/13398_2.png) [@DanielL](https://community.weweb.io/u/DanielL)\
**Post date:** [August 20, 2026, 11:22am UTC](https://community.weweb.io/t/weweb-unify-table-view-filters-of-supabase-tables-are-off/21490/7 "2026-08-20T11:22:12Z")

</div>

Hello everybody! Should be fixed now.
