Hello WeWeb team 
I experiment a rather painful issue with Supabase Data Collections.
My collection has advanced fields, including two dates (date_de_debut / date_de_fin, please don’t judge this awful french naming I claim no responsibility on it 
)
Yet, when I try to filter my collection, those two fields appear as “object”
And because of that I can apply just three kinds of filters on them
although I’d like to have filters like “date greater than”.
The reproducibility of this issue is pretty bad, as on an other collection on the same table dates are listed as text fields 
Any idea about what it is or about what I’m missing there ?
Thanks !
Nicolas
Yeah it’s a WeWeb thing, probably your first record has a null value in the timestamp, so weweb doesnt pick it up. For more flexibility I reccomend using the Workflow Actions to interact with Supabase in WeWeb. I wrote an article on how it works.
That’s a very cool article 
I painfully discovered a fair part of its items while exploring weweb x supabase, but it would have been a great time saver for me !
I’m planning to use Workflow actions for a very specific data collection on an other page, but as far as I know it implies to have custom pagination and miss quite a few native features of Weweb
@ Weweb team : isn’t there a way to gain more resilience there and not stop at the first null value to state the type of a field ? 
Oh and thanks a lot @Broberto for pointing out the root of the problem there !
You can simply fetch data that hasn’t the null in the first row, set it up and then it will work forever like that.
Yeah, I get that very often, as much as I push my content here, it sometimes doesn’t get to you guys 
Yep I did that to overcome the issue … for now.
But I don’t really want to be unable to easily update or even visualize the filters I’ve setup for a data collection ! (that’s what happens right now)
You can create a pretty decent copy of a Collection as a Global workflow btw.
