What are the capabilities of duplicate rules when lookups/MasterDetail fields are involved in the matching rules. We can certainly detect duplicates using combination of other primary data type fields.
Can I make use of duplicate rules to maintain a one to one relationship between two objects(when I create another child with the same parent -> recognise it as a duplicate)?
Is it possible to use it, to detect a combination of a lookup field and some other field as a duplicate - ex- I want to prevent two contacts under an account with the same first name.
How about preventing duplicates when more than one lookup fields are involved in the criteria i.e. Prevent opportunities with the same name being created under the same parent Account and Contract?
Thanks in advance.