There are several data conditions that could cause a data row not to be imported. If an error occurs on any row, it will skip that row and process whatever rows it can. The import screen will display any errors that occur and will provide record counts. The error row number is the data row number. For example, if the third row fails, the error log will stay “Error Processing Row #2” because it is the second data row. The header row is excluded from the count.
Below is a list of some typical error messages for invalid data conditions:
BAD DATA CONDITION
|
EXAMPLE
|
ERROR MESSAGE
|
Invalid Group Plan
|
Insurance Company = One
Insurance Type = Two
Group Plan = Three
Insurance Provider does not match entered data
|
Could not perform lookup for field 'ASSIGNMENT_INSURANCE_PLAN_ENROLLMENT!PREMIUMS_PAID_TO' on value: 'One Two Three'. Got error:No key found for value: One Two Three
|
Invalid Classification Display Value
|
ASSIGNMENT_INSURANCE_PLAN_ENROLLMENT!PREMIUMS_PAID_TO equals a value that is not in the drop-down list options displayed on the screen
|
Could not perform lookup for field ‘TABLE_NAME!FIELD_NAME' on value: ‘XXXXXXX'. Got error: No key found for value: XXXXXXX
|
Date is not valid
|
ASSIGNMENT_INSURANCE_PLAN_ENROLLMENT! ENROLLMENT_DATE equals = “January”. (The date format should be XX/XX/XXXX.)
|
Unexpected Error during SQL execution for table ‘TABLE_NAME’ with message: Syntax error converting datetime from character string.
|