Find the reason for a failed import row, so you can fix it and re-import.
An import row usually fails because Name or Asset Type is missing, or because a field like Cost Frequency doesn’t match an accepted value.
At a glance
| For | Company administrators |
| Platform | Web Portal |
| Applies to | All regions |
| Time to Read | About 2 minutes |
| Checks in this article | • Name or Asset Type is missing. • Cost Frequency doesn’t match an accepted value. • A date couldn’t be read. • You’re missing the results email. |
5 Checks to complete
1. Name or Asset Type is missing
These are the only two required columns — every row needs both Name and Asset Type.
2. Status, Condition Rating or Owner Type doesn’t match an accepted value
The Status, Condition Rating and Owner Type fields use predefined values. When these fields are included in the CSV file, enter the wording exactly as shown below.
| Field | Accepted Values |
| Status | Active/Operational Standby Under Repair Out of Service In Storage/Stock Decommissioned Sold Scrapped/Disposed |
| Condition Rating | Excellent Good Fair Poor Unsafe |
| Owner Type | Owned Leased Hired Contractor Owned |
3. Cost Frequency doesn’t match an accepted value
Cost Frequency must be exactly Daily, Weekly, Fortnightly, Monthly, or Yearly when provided.
4. A date couldn’t be read
Unreadable dates are left blank rather than failing the row, but check the format if a date hasn’t imported as expected — day-first formats such as DD/MM/YYYY are preferred.
5. You’re missing the results email
Check your inbox and spam folder for the import results email — it lists the total, imported and failed counts, with a reason next to each failed row.
Result
You’ll know it’s fixed when the results email shows all rows imported, or you understand the reason next to each failed row.