Lead Import Error Codes
This article goes through the error codes one can receive when importing data into OneLink via a .csv import.
Error: String or binary data would be truncated
This error occurs when a string of text exceeds the character limit for that field. For this example, the address field is limited to only 50 characters.
Error: String or binary data would be truncated
This error occurred due to the Zipcode field expecting numbers for that field. The Zipcode header is intended to expect 5 numbers indicating the intended zip code of that client.
Error: Conversion failed when converting date and/or time from character string
The cause of this error is due to the date not being formatted properly. As we can see from this example '22222' is not formatted as a date, in this instance we would reformat it using Month,Day,Year such as 01/01/01 to resolve this issue.
Error: String or binary data would be truncated
Similarly to the previous “string/binary data would be truncated” error, a field is receiving information that it does not expect. In this case, the Applicant_Gender field is marked with $$$$. This field expects to receive either an M for male or F for female.
Client Import Error Codes
Error: The conversion of the varchar value ‘333444444444’ overflowed an int column
This error happens when a set of characters exceeds the limit for that given field. In this instance, the Lead_Source_ID field has been given "333444444444". The character limit for this field is only designed to take a certain amount of characters, when this is exceeded it gives this error.
Client and Policy Import Error Codes
Error: Conversion failed when converting the varchar value ‘@$$$’ to data type int
This error occurs when providing special characters to header fields that are expecting a number. In this example we have given that field ‘@$$$’ which is considered special characters, which is not expected for this field, thus the error that is received.
Please refer to these articles for further assistance with importing headers in OneLink: