Import Errors do not Transfer to Constituent Update Batch Template Exception Batches

When running an import process and import errors such as "Import for simple data list 'ON' for batch instance field 'State' was not found. You may wish to review your settings for 'Simple data list fields' on the Options tab of your import process." may occur.

Upon committing the batch containing these types of import errors and an exception batch is created these import errors are no longer present in the exception batch and do not re-appear upon validation.

Regardless of the import error, it is expected that these errors would transfer to the exception batch created.

The expectation that all import errors would exist/persist as batch committal exceptions does not apply to the scenario described in this Knowledgebase article.  

This series of events occur when you have mapped an import field to a simple data list with a collection of possible values and your source file contains invalid entries for that collection.  (e.g, a State field is mapped and the import file is populated with value, such as "ON", which does not exist in the CRM States code table collection).  

The import process reads in the string value of the content in the import file (e.g., state = "ON") and compares it to what exists in CRM (states code table).  When this occurs for an invalid value such as a state = "ON," an import error will occur because the value supplied did not exist in the States code table collection in CRM.  The resulting batch is created with no value entered into the state field.  (Since the value didn't exist in CRM, it was discarded when the row was added to an exception batch.)  The exception batch does not have a batch row error matching the import can be committed because there is no logic in the committal process to prevent a commit for a blank state field, only to prevent invalid data.  

Thus, the best way to prevent this scenario is to create import files that do not have invalid data, such as a value for state that doesn't actually exist in CRM.   

Steps to Duplicate

1. Go to Administration\Import and create an import process using the Constituent Update batch template

2. Go to the batch that was created and note import errors which typically are in this format, ""Import for simple data list '' for batch instance field '' was not found. You may wish to review your settings for 'Simple data list fields' on the Options tab of your import process.

3. Now commit the batch and note that an exception batch is created.

4. Open the exception batch and see that the import errors are not there and if Validate is clicked they do not re-appear.

Environment

 Blackbaud CRM
 4.0
 4.0.168.0

Was this article helpful?