I’m having the same issue here, same string DD/MM/YYYY. Result is #ERROR! and it just doesn’t make sense. Did you find any other solution?

If your date string is in any other format besides the U.S. date string format of MM/DD/YYYY, then you need to specifically tell the DATETIME_PARSE function what format you are using.

So, your formula would need to look something like this:

DATETIME_PARSE('31/12/2020','DD/MM/YYYY')

or

DATETIME_PARSE({Date_Field},'DD/MM/YYYY')

Hi Scott!

We tried. It doesn’t work, even specifying the format it returns “error”. Is like the function is ‘broken’ somehow.

I hope someone in the Airtable team can check this out soon. I need to make some calendars!

What is your formula?

Sorry Scott! I think it’s about how I constructed the tables, timezone probably in conflict somehow.


Still, sometimes the datetime parse function won’t “parse” the string as a date.

Since I redo a lot of the tables, I’ll be alert on catching an example for you. Now I don’t have any.


Thanks!!

It is a joke or the problem is always the same after 2 years??? This program would be so great if they care of the customer problem…

No, this is not a problem in Airtable, and has never been a problem in Airtable.

The input needs to be a text string, and the output from DATETIME_PARSE will be a date.

The fact you have to pass systematically by a second column for each date column is a problem.

What specifically are you talking about? What are you trying to do that you can’t do with one column? Try not to be so cryptic so people can actually try to help you.

Same problem.

I'm pulling a date in a lookup field and need it to be recognizable as a date for automation.