Wrong field type in Weweb, not in Supabase

[Corner]

Hi, I’m facing a strange problem (surely I’m missing something but I really don’t see) : I’ve created a new column “docRecent” within a supabase table, which is a boolean, but it appears as an object in Weweb … See the pics below :

In my Supabase table :

Data collection binding (“docRecent” doesn’t even appear in the fields of an object in my collection) :

And when I try to set up “docRecent” as a filter, I get “docRecent” as an object :

And this is how I’m sending the false or true boolean info to Supabase :

Would love to hear from you

[Broberto]

It’s because it’s null. Set your column’s default value to FALSE in Supabase instead. Then it will work.

[Corner]

I thought about this but it’s working with “toutProfiles” which contains NULL values ! So a bit odd, but indeed it must be this

[Broberto]

It usually happens when WeWeb can’t infer the data type from the first row that is returned. So my best guess is that toutProfiles has the first value that is non null (e.g TRUE) if you set the docRecent to TRUE/FALSE it will work.

[Corner]

Very clear, thanks for your time