Were the date time columns overlooked for ISO standards? As currently the API’s return yyyy-mm-dd ##:## and get presented back without any context as to ISO. Additionally they are interfered with by the system according to the user profile settings which are automatically updated according to your physical location?
It’s hard for me to fathom how an application so young was not rolled out initially with ISO8601 as the standards have been around for so long.
Since I can now see this first pass of corrections has happened, is there a timeline for correcting the rest of the application (as this is causing us financial hits when time zone changes unintentionally influence things like our payroll which is being done out of monday.com)?
You are looking at the date “changed at” details of the date, not the actual date itself.
You will need to put a date into the field that is not the same as today to make it clearer as to what you are looking at. So chuck say 2010-01-01 into a date field. Then activate the time on the date field and put 10:00, relook at you api and you will see it is in the indeterminate date format of yyyy-mm-dd ##:##, which is not ISO standard. And yes, it’s annoying the “changed_at” field returns the standard and not the important part of the actual data.