DateTime field conversion error when using API to Add a record

AppSheet AppSheet Q&A
1

Hi everyone

I have a automation running using make.com (the new name for integromat), which creates a new record to in an appsheet app from a customer order in a woocommerce/wordpress site.

It was working fine, but is now giving a REST API error from Appsheet:

[400] REST API invoke request failed - Error: Row having key ‘45266’ in table ‘DTC_Customer_Details’ containing value ‘6/15/2023 4:49:03 PM’ in field ‘order_date’ cannot be converted to type ‘DateTime’ using locale ‘English (United Kingdom)’.

The appsheet table settings locale and locale of the table data source have not changed and are both set to ‘English (United Kingdom)’.

The order_date input data in the rest api call generated by make.com is in ISO 8601 date format.

I’ve done the same rest API call with curl, setting the locale explicitly to en-GB in the JSON properties the JSON below, in case the problem was some behind the scenes change in how make.com handles date fields. I get the same error when calling the REST API directly. order_id is the key field for this table.

{
“Action”: “Add”,
“Properties”: {
“Locale”: “en-GB”,
“Timezone”: “GMT Standard Time”
},
“Rows”: [
{

“order_id”: “42323”,

… other fields omitted for space …
“order_date”: “2023-06-11T23:23:23.000Z”
}
]
}

The strange thing as mentioned is the integration was working fine up until yesterday, and I haven’t (as far a I know) made any changes to the DTC_Customer_Details table in Appsheet, or to the make integration - which is a very simple mapping of fields from a woocommerce order to the DTC_Customer_Details fields.

Any thoughts on how to troubleshoot this?

Thanks
Joe

2

Apologies - I have worked out the problem which was staring me in the face. The input for DateTime was using MM-DD-YYYY while it needs to be DD-MM-YYYY for the en-GB locale.
the reason why I thought it was working previously was the earlier orders were before the 13th day of the month, so it was adding the datetime field without an error but the date was wrong, e.g. 12 June was being recorded as 6 of December :grimacing:

Have now fixed to format the date into UK/GB format, and fortunately there weren’t many records affected by the incorrect order_date which were easy to fix as well.

Sorry for not spotting this before posting!

1 Like