Troubleshooting CSV File Imports
This article provides troubleshooting steps to help resolve any issues you may encounter while importing CSV files into Execution. As a new user, importing CSV files can be challenging, but most issues can be resolved by editing the file itself.
Required Field Mapping is Missing
This error occurs when one or more required fields are missing. If you scroll up to the import file fieldnames, the system will indicate which field is missing.
Could Not Find Value for Required Field
This error message indicates that the field name entered in the import section does not match the column name in your CSV file. Simple typos, such as unintended spaces or mismatched upper and lower cases, can cause this issue.
Value Not in the Right Format
The system will notify you if the value entered is not in the correct format. For example, entering a comma instead of a dot for a decimal value will trigger an error.
Name Not Found in the System
Many names in the system are tied to existing terminologies. If you enter a name that the system doesn't recognize, you will receive an error message. To fix this, ensure that the terminology used in your CSV file matches the terms already in the system.
Terminology Dependencies
Here are some examples of fields where correct terminology alignment is crucial:
Reports:
- Site ID
- Departments filter
- Transports filter
- Teams filter
- Work packages filter
- Asset name
- Affected activity
- Team name
- Transport ID
- Reason for downtime
Work Orders:
- Site ID
- Asset ID
- Subassembly ID (if the 'skip field if missing' box is unchecked)
- Component ID (if the 'skip field if missing' box is unchecked)
- Order type
- Kanban status
- Transport allowed
- Required skills
Assets:
- Site ID
- Asset type
- Work packages
- Milestone
- Milestone status
Subassemblies:
- Site ID
- Asset ID
Components:
- Subassembly ID (if the 'skip field if missing' box is unchecked)
Personnel:
- Role
- Department