Exceptions 101: Decoding the Error Notepad Text

When importing data into the Raiser’s Edge™, exceptions can be a common nuisance to some users. Exception are helpful notifications that protect your database from improper data, but since they represent rows of data that need to still be processed, they can be time-consuming to interpret and handle. So, let’s delve deep into exceptions and learn how to read and handle them properly.

When exceptions are created, there will be two documents produced by ImportOmatic® – an Error.txt file and an Exceptions.csv file. These will always land in the folder designated in ‘General Settings’ or in profile settings under ‘Output Files’. The exceptions data file represents the “WHAT” and will contain the failed rows while the error notepad represents the “WHY” and will contain the reasons why the exception rows failed during the import. Use the error notepad to know what corrections need to be made before reprocessing the leftover rows in the exception data file.

When attempting to handle exceptions, understanding the error notepad is an important part of your troubleshooting. Here is a breakdown of what you may encounter in the error text. At the top of the notepad, you will find information regarding the ImportOmatic (IOM) import profile and the data file location:

Next, you will see the actual reasons for the exceptions created during the import. Don’t let back-end table text data overwhelm you, the notable parts of the error are highlighted and simplified below:

This exception was caused by an invalid incoming data value in the ‘Country’ column and is easily resolved with a dictionary that translates ‘U S A’ into the existing RE table value of ‘United States’. Once the country dictionary is applied to the appropriate column (row) in the profile, this exception can be reprocessed.

When reading an error notepad, remember that the reason for the exception is stated immediately after the line number is listed. The additional back-end table text data that is shown can be ignored. If you’re interested, you may note the specific value causing trouble after the term ‘Value:’ within the hard brackets of the back-end table text data. As an additional note, the ‘line number’ does not account for the header row in the file, so “line 1” is technically row 2 in the file. In the screen shot above, for example, ‘Line 5’ is referring to row 6 in the original data file.

You may review the following Omatic Knowledgebase solution on specific error messages.
The most common can be found here. After you master decoding the exceptions, it really isn’t that daunting after all. In fact, you can be thankful for them!

The Raiser’s Edge™ is a trademark of Blackbaud, Inc.


Share this post