Our support team may enable CSV import locking on your workspace. This mode is designed to ensure that all uploaded CSVs conform to previously uploaded (mapped) ones. This avoids all types of data mistakes and problems described below.
Suppose that you have a CSV file called "example.csv" like this:
On import, you mapped fields, for example like this:
Later, you imported another CSV file called "something else.csv", whose "Total" field has been renamed to "Amount".
When you import, you will get a warning like this:
If a CSV import locking is enabled, we will prevent you from finishing the import because your schema changed. This avoids all types of data mistakes and problems.
For example, formulas may reference fields by name. If your field names change constantly, formulas must be updated constantly as well.
Also, logic may rely on the file name to know which type of data it is. For example, if the file name has "Deals" in its name, then some logic may assume that it contains deals. If the file name has "Invoices" in its name, then some logic may assume that it contains invoices.
The CSV file lock ensures you do not run into those types of issues, and forces you to use consistent CSV names and schemas. As a result, formulas don't need to be updated to account for an ever-changing schema (or ever-changing file naming conventions).
Should you need to add a field or change mappings, please consider contacting support for assistance. We can help you find the best way to update your schema.