In last week’s Exceptions 101 blog, we learned how to break down exceptions in order to learn how to read them properly. With time-saving steps on deciphering and handling exceptions, exceptions don’t seem as daunting. In fact, ImportOmatic exceptions are helpful notifications that protect your database from improper data. Since many exceptions are quite common, today we’re providing a guide for working through the top error messages.
- Invalid Code table entry – If you’re receiving this exception, the value imported from the data file does not match an existing Raiser’s Edge (RE) table entry value. However a dictionary can be created to resolve this error! To learn more: http://iom.uservoice.com/knowledgebase/articles/291355-error-invalid-code-table-entry-gl-post-status
- ‘xyz’ is an inactive table entry, you must reactivate it if you wish to select it – If you’re receiving this exception, the value imported from the data file is an inactive table entry value. To resolve, locate the respective RE configuration table and reactivate the value ‘xyz’.
- Required Field Missing – If you’re receiving this exception, a new record is attempting to be created and a field marked as required must be added to process the data row and create the new record. To resolve, add the required field value to the data file, to the virtual fields or with a default set. To learn more: http://iom.uservoice.com/knowledgebase/articles/291295-error-required-field-missing-constituent-code
- Number of fields in this data row (xx) does not match number of fields profile (xx) – If you’re receiving this exception, the number of columns in the incoming data file and the number of columns in the ImportOmatic (IOM) profile must be an exact match. To resolve, adjust either the profile or file to ensure they are identical in layout. To learn more: http://iom.uservoice.com/knowledgebase/articles/291432-error-line-1-number-of-fields-in-this-data-row
- This record was skipped by user – If you’re receiving this exception, this error is created when the IOM user selects the “Skip” button during import processing (this option skips the entire row and records the row as an exception within the exceptions.csv file).
- This row required user interaction and was skipped – If you’re receiving this exception, this error occurs when selecting the check box to “Skip Rows Requiring User Interaction” (*Note* this setting creates exceptions instead of standard processing screen interactions)
- Import canceled by user – If you’re receiving this exception, this error is created when the IOM user selects the “Esc” key during import processing. All rows processed before this process into RE. The row that the cancellation was made on and all rows after will be recorded as exceptions that did not process and can be located within the exceptions.csv file.
For more tips & tricks on working though exceptions, check out ImportOmatic’s User Voice: http://iom.uservoice.com/knowledgebase/topics/46282-importomatic
The Raiser’s Edge™ is a trademark of Blackbaud, Inc.
Allison Bolduc is a Consultant for Omatic Software in the Professional Services department. She currently assists clients in implementing, learning, and maximizing their use of Omatic products. Previous to holding her current position at Omatic Software, Allison worked for seven years in the nonprofit world as an Associate Director of Development at the Charleston Animal Society and as a Membership Coordinator at the Gibbes Museum of Art. In these roles, Allison gained real-life practical experience working with the Raiser’s Edge 7 (both as a non-hosted and hosted client), Blackbaud NetCommunity and Sphere Friends Asking Friends. Allison holds a bachelor’s degree in art history from the College of Charleston and is a member of the Association of Fundraising Professionals.