I’m trying to use Supabase API to get a filtered view in Supabase. While I’m able to query the Supabase API with filters in other tools just fine, I’m not able to apply the filters in WeWeb. As the Supabase API docs suggest, I add the filters as query parameters (and, as I learnt in another post, wrapped the object in an array). However, as you can see in the screenshot, the API is called without applying any filters (which results in loading the whole view). How can this be solved?
Can you send the payload/the query strings from the tab? It’s most likely wrong formatting imo.
Can you not just use the built in Supabase Select action in the workflow? I’ve found the filters there can achieve everything I need and that’s a fair bit of nested objects with conditional clauses.
Using the filters on data → collections is more limited.
That’s the thing: even though you see the query string that I use in the initial picture, there is no payload (query string) submitted, when the query is executed. There is no payload tab and the preview tab is empty.
I think you have the RLS enabled on the table, it usually returns this kind of empty array.
I’ve set a security invoker on this view - the underlying tables of the view have RLS activated, yes. So there is no way to load the data via API?
Security invoker, means that it gets invoked with the rights of whoever invokes it. Meaning that it respects the RLS. If you want to avoid RLS, you need to set it to be security definer.