
Comment Post Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Jan 23, 2023 12:01 PM
Hi,
I am working on a project requiring syncing complex data to Airtable. After having errors due to some columns containing json data (working on a Python script), I switched my API queries to typecast=true which solved my issue (json data is converter to text).
https://airtable.com/developers/web/api/create-records#request-typecast
However, I was surprised that using this parameter gives me some errors on dates formatted as "2023/01/19 10:12:18" while same data was working correctly with typecast=false :
requests.exceptions.HTTPError: ('422 Client Error: Unprocessable Entity for url: https://api.airtable.com/v0/*********/*********', '422 Client Error: Unprocessable Entity for url: https://api.airtable.com/v0/*********/********* [Error: {\'type\': \'INVALID_VALUE_FOR_COLUMN\', \'message\': \'Cannot parse date value "2023/01/19 10:12:18" for field date_intervention\'}]')
Isn't typecast=true supposed to be more permissive ? If so, why such errors on dates while they are accepted on typecast=false?
0 Replies 0
