Fix CSV Import Validation Errors
The corrected CSV maps each intended value to the right asset field and contains valid rows.
On this page
Correct common file, mapping, required-name, category, location, status, and duplicate-barcode problems.
Before you start
Role needed: Owner or Admin. Ask an Owner if an action is unavailable.
Check the file structure
Use a readable .csv file with a header row and comma-separated columns. If OrbitEquip cannot parse it, export a fresh CSV from your spreadsheet application.
Check required and mapped fields
Make sure every row to import has a Name value. In the mapping step, confirm each source header maps to the intended field and set unrelated columns to Do not import.
Resolve conflicting values and limits
Review category and location names, valid status values, and duplicate Existing Barcode values. Keep the file within the 5,000-row processing boundary and the current plan's live-asset limit.
Retry with the corrected file
Save a corrected copy, reopen Import, review the column mapping, and read the result summary after import.
Tips
Keep in mind
Troubleshooting
Import remains disabled after selecting a file.
Check: Confirm a file is selected, the Name mapping is correct, and required row values are present.
Fix: Correct the source file or mapping and choose the file again.
Open related guideStill stuck? Contact OrbitEquip support.