We have activated the standard duplicate rules and matching rules for Account. Generally, they seem to work and the duplicate records get written into the tables DuplicateRecordSet and DuplicateRecordItem. There are a few exceptions though that do not get written into the databases. When the duplicate Accounts are inserted manually, they are detected as duplicates, and the duplicate Account message appears on the top of the user interface. But this query does not give me any results for the specific duplicates, matching by name:

SELECT DuplicateRecordSetId, Id, IsDeleted, Name, RecordId, Record.Name, DuplicateRecordSet.Name, DuplicateRecordSet.RecordCount FROM DuplicateRecordItem WHERE IsDeleted = false AND DuplicateRecordSet.RecordCount > 1 AND Record.Name = 'Test Account'

For an example, the duplicate matches via First Name and Last Name and Billing Address so that the Account Matching Rules should get triggered. When I try to reproduce the error, the records get inserted into the duplicate tables just fine.

  • When are you calling this query? The duplicate record entries are not committed to the database until after the duplicate record itself is, so it may well be a timing issue. – sfdcfox Aug 29 '19 at 13:53
  • The records are already inserted into the database. That has been done manually, and they have been detected as duplicates. Only the duplicate information cannot be found in the database. – user40501 Aug 29 '19 at 14:01

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.