Why does my CSV import fail, abort, reject values, or show no rows?

Short answer: Most failures come from a file that isn't UTF-8, headers with special characters, a non-comma separator, or values that don't match the target field. Fix the file, check the failed rows, and retry.

Why it happens

• A file that isn't UTF-8 can report success yet load nothing.
• Headers must be English alphanumeric. Special characters or non-Latin scripts fail.
• Only the comma (,) works as a delimiter.
• Dropdown values must match the list exactly, punctuation included.
• Dates fail when their format doesn't match the format chosen in the mapping.

How to fix it

1. If the import was aborted or some rows failed, download the failed rows or open the error log to see why.
2. Re-save the file as UTF-8 CSV. One reliable way: open it in Google Sheets and download it again as CSV.
3. Keep one header row with plain alphanumeric names, and make sure every value sits under the right column.
4. Map each column to a field of the same data type.
5. For "values are not present in the selected list", make the list value and the CSV value identical.
6. For dates, select the matching format in the mapping, for example DD/MM/YY HH:mm for 17/05/19 12:57. See the supported date and time formats.
7. For User fields, such as a board's assignee, put the user's email address in the column.

Row limits per import:

• Datasets: 50,000 rows and 100 columns. See importing data into a dataset.
• Dataforms: 5,000 rows, or 500 if the form has dropdown, aggregation or lookup fields. See importing data from a CSV file.
• Child tables: 1,000 rows per import. The Import CSV option appears only when Enable table import is on in the table's settings.
• Boards: 500 rows. Split bigger files. See importing items from a CSV file.

If the import says it completed but no rows appear, or progress sits at 0%:

1. Try a hard refresh, a private window, or a cleared cache with browser extensions off.
2. If the "import successful" email arrives but the progress bar never moves, a firewall may be blocking the page's live connection. Ask IT to check, or test from another network.