I don’t have a video, not much video to do, but here is example, I was importing a CSV, which I always do import, the CSV format changes slightly in the way that there is one less column in the updated version of the CSV.
The CSV import didn’t work as expected using the Airtable CSV import because the auto-mapping mixed up 2 key columns, one of them is the primary column for me.
The new CSV changed, however, not these columns. Some other previously mapped column (Expenses column) was removed from the new version of the CSV I am importing.
That seems confuses the CSV import and now some mapping broke.
Previously I was importing mapped:
Order Number → Order Number
Sales Record Number → Sales Record Number
Importing the new CSV now and it mixed up these two.
The rest of the columns seems imported correctly.
Unfortunate thing with the CSV import extension in Airtable is it doesn’t warn you if things are not normal:
a) the CSV template has changed
b) mapping is broken in some way
Both things could be accomplished easily.
So I am adding this here because you asked me for an example.
Maybe a good soul can wring a GUI for the Airlift.
Or maybe ChatGPT will get so good one way I can ask it to create a GUI
The issue with Airtable doesn’t happen very often, but when it does it happens in the most inconvenient of moments. Maybe I need to look at the online CSV import tools for Airtable although some of them do charge by line, regardless whether the CSV contains line of data or line of comments which I am not importing.
I am using application called Easy Data Transform and that using the transformation Stack and then Transpose and Compare Cols etc I compare 2 CSVs , the original template and the imported CSV to see if they match. It tells me if they are not matching. It’s a workaround as Easy Data Transform doesn’t have native CSV comparison, but it works via the Stack function.
However, I didn’t use the Easy Data Transform today, Forgot to use it. So went ahead and imported it to Airtable via Extension and it mixed up the columns because there was a small unrelated change in the CSV:
Here is the mix-up: