A CSV import skips rows or won't start
Find out why an import from CSV skipped rows, stopped at the row limit, or wouldn't let you continue, and how to fix your file.
- Applies to
- Core 12.7 and later
- Who can do this
- Administrator
On this page
Symptom
One of these happens:
- there's no Import CSV button on the list
- the result shows n skipped, with lines such as Row 12: The name field is required.
- the result says Only the first 5000 rows were read.
- Next shows Could not read the file, or a message about the file's size
- Import stays grayed out
- the column lists offer only one column
Check these, in order
1. There's no Import CSV button
In Core, only Countries, States and Cities offer import. The button appears only if your role has both of the list's permissions:
- the one to create records, for example
feature.core. country. create - the one to import them, for example
feature.(Import Countries (CSV))core. country. bulk_import
Fix: ask an administrator to add whichever is missing, then reload the page. On other lists, add the records one at a time, or ask your Laramin provider.
2. The file is too large, or isn't a file Laramin can read
A file over 10 MB is refused at Next. Fix: split the file into smaller ones and import each.
3. A required field has no column
Import stays grayed out until every field marked * has a column. Fix: choose a column for each one. If your file has no such column, add it to the file and upload it again.
4. The file doesn't use commas
The importer reads values separated by commas. A file saved with semicolons, which some spreadsheet programs use in some regions, arrives as one long column. Check First rows of your file: if each row shows as a single cell, this is why. Fix: save the file again as comma-separated CSV.
5. A state or city didn't find its parent
A skipped row that reads The country id must be an integer. or The state id must be an integer. means the Country or State value matched nothing. Common causes:
- the country or state isn't in Laramin yet. Import or add it first.
- it's spelled differently. A country can be given by its ISO code, its name or its ID number; a state by its name or ID number.
- for cities: two states have that name, for example in different countries. Laramin won't guess which one you mean.
Fix: correct the value in your file, or use the record's ID number. You can see ID numbers by exporting the Countries or States list.
6. Rows broke the list's rules
Each row is checked against the record's rules. A row that fails is skipped and listed with its reasons, for example The name field is required. Every other row is still imported. Fix: correct the listed rows in your file. Then import a file that holds only those rows, so the good rows aren't added twice.
Row numbers count the heading as row 1, so they match your spreadsheet. Empty rows are ignored and aren't reported.
7. The file has more than 5,000 rows
One import reads up to 5,000 data rows. Those are imported, and the rest aren't read. The result says Only the first 5000 rows were read. Split the file and import the rest separately. The unread rows aren't counted as skipped. Fix: put the remaining rows in a new file and import it.
8. You see "Import file not found or expired."
The uploaded file is removed once an import has run, so the same upload can't be run twice. Fix: close the dialog, select Import CSV again and upload the file again.
Still not working?
Raise a ticket from Support Center in your Laramin app. Include this page's link, what you checked, and the messages from the result.
Thanks. That helps us decide what to write next.
Thanks for telling us what was missing.
You already answered for this article today. Thanks.
We got a lot of answers from your network just now. Try again in a few minutes.
We couldn't send that. Check your connection and try again.
Links in this article
Printed from help.bsscn.com. The online article may have changed since.