Good afternoon @derekwu - I've been using the Sync API with CSV files in production lately, it's great!
I have some feedback - during today's testing, I created a CSV with pricing data, and I went to use the new Sync API to bring that CSV back into a new sync'd table - however I noticed that for any currency field within the input CSV file, the sync tool was unable to convert this to either an Airtable numeric or currency field.
I feel that a lot of CSV data would be output from systems, containing units, be it either units of currency or measurement - and it would be greatly beneficial if this could be configured somehow when configuring the CSV Sync.
Considering this limitation for the first time now, I think the only two workarounds available are to either manually strip out the units from the original CSV data, or, continue with the sync, then create a formula field that parses the CSV string data into the desired numeric value with post-Airtable Field formatting applied.
Good morning @derekwu - just some further feedback on the Sync API for CSV_DATA - in that when taking CSV from one source.
I've found that the incoming CSV data may contain duplicate fields and I'd like the ability to resolve this problem within Airtable, and not have to deal with it prior to my data uploading to Airtable using another app.
For example, I can't control the fields that output from this running data source - meaning that before I get this data sync'd in Airtable, I have to parse it through another app, be it Google Sheets, Excel... Really I'd just like to have it upload to Airtable and then review/resolve the duplicate field issues from within Airtable.
Also, I've another question on if the "Duration" conversion process could be improved. Here we have running data, but none of it can be converted to leverage the Duration column - at least not easily.
Some similar data - "Best Lap Time" that could be displayed via a Duration field;
But upon converting within the Sync CSV Data setup, there's no way to correct the duration format.
EDIT: Thankfully those duration field configs aren't stuck - and can be updated to reflect the true data after the initial sync process. 🥳