Last year, we added a feature to ImportOmatic that allows users to intentionally skip rows based on the values contained within a column. This means less work removing declined credit card transactions, organization rows, and other types of data that we often isolate prior to importing. Since then, we’ve also added an additional option for you to isolate the intentionally skipped rows from unexpected exceptions. This is an optional function. By default, when you upgrade to the latest version, ImportOmatic will keep the same functionality you have already been using – it will export all exceptions, intentional and unintentional, within the same file. If you want to turn on the separate files, just head to the Output Files section of your profile, and mark this checkbox:
When you enable a separate file for skipped rows, it will only include those rows that were skipped by a dictionary. Any rows you manually skipped during the import itself will still live in the standard exceptions file. Profiles with a skipped rows file enabled will output the following files:
Error.txt – Contains the messages explaining what unintentional exceptions occurred, including manually skipped rows
Exceptions.csv – Contains the data rows of the records listed above, so that you can make necessary corrections and re-import:
SkipRowError.txt – Contains only those rows that were skipped intentionally by one or more Skip Row dictionaries:
SkipRowExceptions.csv – Contains the data rows of the intentionally skipped rows, so that you may correct, discard, or import them through a separate profile you’ve configured:
Hopefully this small checkbox will have a big impact on your import processes!