It looks to me like it’s an issue with time zones - for me in the UK the last DATETIME_FORMAT works correctly for all times of the day - but then I am in the UK on the date line!

There is a support article about this though:

I hope this helps - it looks as though they have thought about it!

Thanks Julian, yes it seems the problem lies in Airtable assuming I’m in London

I wonder how I can tell them where I am so when I enter a date and time it is saved correctly!

Hi James

I’ve had a bit of a play around with this and the Set_Timezone function doesn’t seem to work as expected - I think this is one for Airtable to answer!

Cheers Julian - nice getting to know you - I hope I can return the favour one day

I’m sure you will get the chance!

You may be interested - I have literally just now created a new Linked in Group called Mobile and Web Databases which is intended to be a forum for people using services like Airtable (and others) as well as Zapier etc. I’m hoping that it eventually becomes a great place to share experience across different platforms, find reviews etc.

Your welcome to join (as is anyone else reading this):

https://www.linkedin.com/groups/8572976

Still working this problem through with Victoria at Airtable - when we get a resolution I’ll let you know.

Hey guys! Is this an official bug? It looks like SET_TIMEZONE doesn’t do anything…

Hi Tuur,

Try DATETIME_FORMAT(SET_TIMEZONE({Some Date Field}, ‘YourTimezone’), ‘HH:mm’))

Alex

It’s a bit strange. When I use something like:

DATETIME_DIFF(DATETIME_FORMAT(SET_TIMEZONE({Value}, ‘Europe/Amsterdam’), ‘YYYY-MM-DD HH:mm’), NOW(), ‘minutes’)

I get a 240 minute difference when my own value is now…

DATETIME_FORMAT(SET_TIMEZONE(Value, ‘Europe/Amsterdam’), ‘YYYY-MM-DD HH:mm’)

Gives me a timestamp that’s 2 hours later than my original value.

Airtable takes GMT by default or something?

Yup.

DATETIME_FORMAT(SET_TIMEZONE(NOW(), ‘Europe/Amsterdam’), ‘YYYY-MM-DD HH:mm’)

Works.

Cheers @Alexander_Sorokin