Resolve Excel Import Errors
- Situation
- Server side error
- A column not found in file
- A cycle in dependencies is detected on a line
- Invalid key value
- Contact Support
- More Info
Situation
When importing Excel files into Wrike, the import operation may fail for various reasons. Wrike will display an error message explaining the cause of the problem. This article provides additional guidance on resolving specific error messages to help you successfully import data into Wrike.
Server side error
"Server side error" can be caused by incorrect formatting of the file or insufficient user permissions and access restrictions.
Incorrect file formatting
- Start/End Date columns should be set to Date type. By default, dates should be added in mm/dd/yyyy or mm.dd.yyyy format.
- The Depends On column must reference only existing task keys from the Key column and use correct syntax (e.g. 5FS, 12FF, 10SF, 1SS). Values like "nullFS", "nullSS", or links to folders/projects should be removed.
Tip
To ensure smooth data import, please use simple data entry without merged cells or Excel formulas in your spreadsheet.
Permissions and access restrictions
- You must have the permission to create items in the location (folder/project/space) where you are importing the file. Your account admins can help to update your permissions in the location, if needed.
- Only account-level custom fields can be created via Excel import. Users who don't have the rights to create account-wide custom fields will see the error message.
Reach out to your account admins in case you need to create new account-level custom fields before importing data.
Alternatively, the required custom fields can be created at the space level. Make sure the Excel column name exactly matches the corresponding custom field title.
A column is not found in file
The error "Column is not found in file" can be caused by the absence of the required columns – Title, Description – or a mismatch in their formatting (for example, extra letters or numbers added to the headers).
The required column headers are not case-sensitive, but they must have the correct spelling and character count.
A cycle in dependencies is detected on a line
The error is displayed when the file lists the same key for different unrelated items. For example, if the same key is specified for a task and its parent task, folder, or project. If multiple unrelated tasks, projects, or folders contain the same key, all items under the duplicate key will not be created upon the import.
Invalid key value
The error occurs when the value entered in the key column is equal to or greater than 1,000,000. Make sure that all key values do not exceed 999,999.
Contact Support
If the steps described in this article didn't help, contact our Support team assistance. Please include the following information in your request:
- The file you are trying to import into Wrike.
- Permalink of the location where you are trying to import the file.
- Timestamp of the recently failed import attempt.