Product: ImportOmatic
Description: Occurs when there is a discrepancy between the constituent id listed in the file and the id existing on the constituent record
Occurs when importing organization relationships and including virtual fields for the relationship, but not every row has a relationship
Version: All
Environment: All

Answer:

If the constituent is existing in the database and these are not new records, this error is occurring because there is a possibility of a discrepancy between what is in the file as the constituent id and what is in the database as the constituent id. Use the following steps to resolve:
  1. Open the profile you are working with and select "Constituents" from the profile navigation pane
  2. Place a check mark in the check box in front of "Do Not Add New Constituents If they Do Not Match An Existing Record".
  3. Highlight "ID Matching" in the profile navigation pane as well and select to "Treat the data row as an exception".These few changes will allow you to prevent adding new records to the system during import and place any record that is not matched via Constituent ID into the exceptions file as well.

If adding relationships
  1. Open the profile you are working with and select "Virtual Fields" from the profile navigation pane
  2. See if there are any virtual fields for Organization Relationship
  3. Open the data file and find the columns for the Organization name
  4. If there are any rows that don't contain a relationship, this error will occur because virtual fields are a blanket application. IOM is trying to add the value in the virtual field to a relationship and is trying to add a record for the relationship
  5. Move the virtual field to the data file and populate the value for those rows that have a relationship. Alternately, split the file and import the rows with a relationship first and then import the rows without a relationship after setting the virtual field to Ignore

Please refer to the ImportOmatic User Guide for additional information.