06-06-2012 05:20 AM
Check for Duplicates is a hard-coded function that, according to Sage support, does not raise any events to capture which records were deleted and which records survived.
Given this limitation, I'm looking for a Check for Duplicates rewrite. Has anyone tackled this?
Here's why ...
If you had a Library client, think of the case where the custom entity is a book. If you keep a field on the book entity called “CHECKOUTCONTACTID” so that you know which contact has the book checked out, this field will become orphaned if the contact is the subject of a Check for Duplicates delete.
As far as I can tell, there are no tools available to the developer to prevent an orphaned relationship other than to disable Check for Duplicates and replace it with a rewrite.