Person Account behaves differently than other objects for Duplicate Rules if the field being checked is not visible to the user
Last updated 2018-05-05 ·Reference W-4673502 ·Reported By 8 users
If a user does not have access to a field, for which a duplicate rule is setup to check duplicates, there is no error thrown for person account. However, if the same is setup for a different object (standard or custom), the error is displayed.
Create a duplicate rule to match a field's value.
Create a trigger to update the field's value to a specific value - to see the effect.
If a new record is created, below would be the behavior:
Generic object: If trigger is active and field is not visible, the duplicate is checked and error is thrown.
Person Account: If trigger is active and field is not visible, the duplicate is checked, however, it results is a no match and error is not throw.
Give the user access to field. In case the field value is not to be displayed, hide it on page layout.
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.