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”
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.
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 ?
I also solved the problem by filtering the column data with “not empty”. After that WeWeb detects the correct data type.
But on my case I needed this at two columns at the same time, and it seems to not be possible, as WeWeb interchangeably detects one in detriment of the other. Considering that each row will have one of these column as Null.
)
