Constituent Update Batch does not identify duplicate records in Smart Client

When using Constituent Update batch to update a constituent who is a potential duplicate, an exception should occur to allow the user to either add this as new record or confirm that this is a duplicate.  In both the Web Shell and Smart Client, users receive the exception:

This constituent might be a duplicate. Click here to view.

In Web Shell, users are able to click and view the potential duplicate.  However, in the Smart Client, when users attempt to view the duplicate, they may receive the message:

There were no duplicate records found.
Download and install the latest patch, which contains all fixes from previous patches. If you are running an older version, download and install the latest version and then the patch. 


 3.0.516, SP 2
 3.0.516, Service Pack 3

Was this article helpful?