Allow manual search for records that error or exception out. Especially in the case of those returning with 502 "over 100 records match"
When IOM throws an exception, it is a pain to go back and edit a file then run a re-import process for something small like a mis-typed zip code. More critically, the new error that ignores an import line if there are over 100 matches is particularly frustrating because it forces the user to use less complex matching options (bad when importing/matching lots of records), or have to spend lots of time after the import manually making entries for records that have too many false matches. It would be better to allow the user the option to manually search for a matching record when the error/exception is thrown and edit/enter the correct data on the fly.
Brad C
shared this idea
-
Lucy P
commented
Totally agree Brad on this - we are having real problems since upgrading to the newest IoM and encountering the 5.2 error messages about having over 100 potential dupes to match to. I'm having to go back in to the ones I can't match, add in a fake middle name, change matching criteria to include middle name, and re-import. Then delete the fake middle name from the records and restore matching criteria to original settings. We didn't actually encounter the issue of RE crashing when finding over 100 potential matches previously, so this 'fix' hasn't fixed anything for us, it's created some real problems. We don't always have postcode or other details to match on but do often have email or phone, so perhaps there could be more options added to the dropdown in the matching criteria options, like email address etc (these are pretty limited presently). Or just have the option to switch off this error message completely. For small databases it's not going to be an issue but we have over a million records on ours and there are many common names that occur over 100 times. Please fix this!!