When importing data, the values in each field must be of the same type as defined on the field. For example, if a field is set to a numeric type and one of the values in this field is ‘I am not a number’, it cannot be imported.
In such situations, you will see the Synchronization Errors window:

This window lists all the values that could not be converted to the type specified by the field. At this point, you have three alternatives:
| Retry | Allows for fixing the problematic values at the source and retrying the import process |
| Skip All | Rows that contain problematic values will not be imported |
| Cancel | Abort the process |
Here are some scenarios where this could happen:
| Problem | A Date/Time field contains a textual or numeric value that cannot be converted to a valid date or time |
| Resolution | Check the source data and make sure the value is indeed a date/time. If the value is textual and appears to be valid, make sure you specified the correct culture in the import configuration window. This culture information is used to parse the values according to the formats commonly used in that corresponding region. |
| Problem | A numeric field contains a textual value that cannot be converted to a real number |
| Resolution | Check the source data and make sure the value is indeed a numeric. If the value is textual and appears to be valid, make sure you specified the correct culture in the import configuration window. This culture information is used to parse the values according the formats commonly used in that corresponding region. |
|
This often occurs when trying to import Excel file, because they are unstructured and allow mixing of values of different types in the same field. Make sure the field types are correct before trying to import.
|