Hi Airtable Community,
I’m trying to confirm whether the CSV Import Extension supports updating an Airtable Checkbox field from TRUE → FALSE when using “Update existing records / Merge”—or if there’s a known limitation/workaround.
What I’m trying to do
We run a recurring sync where we:
-
Export a CSV from Google Sheets that contains:
-
a unique ID (used for matching)
-
several columns of values
-
one column that represents a boolean (e.g.,
TRUE/FALSE)
-
-
Import that CSV into Airtable using CSV Import Extension → “Merge with existing records”
-
Map:
-
CSV ID → Airtable ID field (for matching)
-
CSV boolean column → Airtable Checkbox field
-
What works
-
If the Airtable checkbox is currently unchecked (FALSE) and the CSV value is TRUE, the checkbox updates to checked (TRUE) correctly.
The issue
-
If the Airtable checkbox is currently checked (TRUE) and the CSV value is FALSE, the checkbox does not get unset—it stays TRUE after the merge/update.
I’ve tested multiple “false” representations in the CSV, including:
-
FALSE -
Off -
unchecked -
no
In all cases, FALSE → TRUE works, but TRUE → FALSE does not.
Steps to reproduce (minimal example)
-
Create a table with:
-
a unique ID field
-
a Checkbox field
-
-
Create a record where the checkbox is TRUE
-
Create a CSV with the same ID and the checkbox column set to FALSE
-
Use CSV Import Extension → Merge with existing records
-
Map ID + checkbox field
-
Run import
-
Result: checkbox remains TRUE instead of changing to FALSE
Questions
-
Is this expected behavior / a limitation of the CSV Import Extension?
-
If yes: is there any recommended workaround to force TRUE → FALSE updates via import/merge?
-
e.g., using a different field type, a formula + automation, a scripting workaround, or a specific accepted CSV value format?
-
