Bug: Formula columns in inptuFields

Interestingly, theres no way to edit and fix typos in post titles on this platform.

isn’t the bigger issue that a developer platform is sending us dates in anything other than ISO8601 format?

Also, if I do the following to build the date in YYYY-MM-DD format:

CONCATENATE(
  YEAR({Date}),
  '-',
  IF(MONTH({Date}) < 10, 
    CONCATENATE("0", MONTH({Date})), 
    TEXT(MONTH({Date}), "0")
  ),
  '-',
  IF(DAY({Date}) < 10, 
    CONCATENATE("0", DAY({Date})), 
    TEXT(DAY({Date}), "0")
  )
)

it will still produce something like "11 March 2026" as the input field value, so this really is not behaving correctly.

So it really looks like whenever the date is presented in YYYY-MM-DD format, it then additionally gets converted into the local date from the original column.

This is quite a large bug that does need looking at.

OK, I’ve found the workaround. You need 3 separate formula columns.

“YYYY” with the formula `YEAR({Date})`

“MM” with the formula:

IF(MONTH({Date}) < 10, 
    CONCATENATE("0", MONTH({Date})), 
    TEXT(MONTH({Date}), "0")
  )

“DD” with the formula:

  IF(DAY({Date}) < 10, 
    CONCATENATE("0", DAY({Date})), 
    TEXT(DAY({Date}), "0")
  )

You can then concatenate them together in an automation block like so:
 

They will be passed in to the inputField in the automation block without being converted back to the local date for the automation user.

Is this crazy? Yes. Does it work? Yes.

Even using this:

CONCATENATE("2026-",FORMAT_DATE({Date}, "MM-DD"))

Ends up with the date in 11 March 2026 format. Overall, not good.

​@noa.rapoport  One more thing. If you want to fix this, I can recommend a similar approach to that taken in our Microsoft 365 integration for monday.com when we do export to Word documents.

Documented here - https://monday-help.dsapps.dev/microsoft-365-office-embedded/preparing-your-word-templates - but for clarify, added below:

--- 

For a column of type Date, named Date, the following tags are available:

• {Date} – the date as displayed in the column

• {Date.UTC} the date/time at Coordinated Universal Time (UTC)

• {Date.language} the language of the automation user

• {Date.time_zone_identifier} the time zone of the automation user

• {Date.local} – the date/time of the column in the local timezone for the automation user

• {Date.local_format} – the date/time of the column in the local timezone and format for the current user e.g. 11 September 2024 or September 9, 2024 at 08:00 or similar dependent on the automation user’s language & timezone settings

• {Date.ISO} e.g. 2024-09-11 or ISO 8601 date format

• {Date.DMY} e.g. 11/09/2024 or international format

• {Date.MDY} e.g. 09/11/2024 or American format

This could be added into automation blocks in a similar way that the People/Person column works, where you can choose emails, phones or names:

Here’s my workaround for the date column bug: