Hey, everyone.
Not sure if this was reported, but it seems like I'm experiencing a bug. While selecting 2024-12-31 in the date_picker component, the interface shows 2025. I'm seeing this also reflecting in the same field at the table (it's showing 2025, but in the database is 2024).
Thanks!
Hi @Vitor_Dal_Pra,
Very odd 
If you delete the calendar component and recreate it, does the bug persist?
Hi @Jack_T,
I created a new date range component and with the default date format, I got the same results as you.
The issue seems specific for the date format I'm using here: d/M/Y
@Vitor_Dal_Pra Ahhh I see,
Going to guess that the JS library we use for the calendar component needs some additional configurations to work with the that date format
Hopefully this is an easy fix and we can add a toggle to switch the calendar between 'American' date of M/d/Y and the system everyone else uses 
For now the work around would be to use Month, Day, Year as the calendar expects. Apologies for the inconvenience!
They tell us not to give estimates since the engineer teams have a lot on their plate
I would imagine once they got to the ticket it won't take more than a week or few days to add in a way to alternate back and forth between the two formatting options.
Just depends on how many tickets they have to get to before they see this one.
In the short term, you could have a separate component work as the 'input' which takes in the date in the format that you want, and then thread the transformed/formatted data into the calendar 
Hey @Jack_T totally understand that. I wanted to know if we were talking about weeks or days, so you answered that as well, hehe.
Tks!
