Do you know why filters can be disabled on their own ? I thought about the condition element that is not loaded, but it is not the case.
I can’t even try to set up a new filter … It’s completely disabled
I can’t even try to set up a new filter … It’s completely disabled
You need to fetch the data, if there is no data, by default it will be empty. Filters are taken from the data.
That’s what I did, like when I got this error (the one on the pic), I tried manually start over the fetch of the collection (with “Select the source”, “Configuration” etc) but once arrived to the “Query configuration” step, I get again this error (hope that’s clear enough)
In that case I think you’ll need to remove the filters, re-fetch data and redo the filters. I highly suggest using the workflow actions when you have many filters like these. I wrote about them in my blog about Advanced Usage of Supabase in WeWeb.
Alright that’s what I’m gonna do, thanks