This is a known issue that comes about when using the duplicate checker.
When importing data through the regular RE import and using the duplicate checker, even though a record is found to be a duplicate and an exception is created, the record is imported anyway.
We believe that this is down to the fact that the duplicate checking code within Raiser's Edge is a separate component to the main Raiser's edge application so in-effect a 3rd party component like Audit Trail Classic.
The components, we believe, are run in the order that they were installed meaning that if you recently upgraded then the audit trail component is now older than the RE duplicate checking component, by re-installing Audit Trail Classic this should reverse the order.
It is also possible that if you reinstall the same version of Audit Trail Classic based on how the information is stored in the registry this could still be seen as the older component therefore would it be possible to uninstall and then reinstall the same version of Audit Trail classic and if this does not resolve the issue to install the latest version of Audit Trail Classic.
There are two other workarounds:
- Uncheck the import option from the Audit Trail settings in Audit Trail Viewer. This will prevent Audit Trail Classic from interacting with the importing and therefore any exceptions will be flagged as such.
- Use Importacular to import data as this integrates with Audit Trail Classic and Validatrix and has its own more sophisticated duplicate checking.