Dedupe Rules based on Custom Fields of Contact Sub-types

[Richard Bramley]

Currently you can create dedupe rules for standard data for the three contact types (households, individuals and organizations) and the custom fields for the three contact types, but you can't use the custom fields of the contact sub-types.

My suggestion is that the custom fields for the sub-types of the relevant contact type be shown as fields that matching can be done against and that these fields be used in the places where deduping is performed.  If the custom field does not apply to one or other of the contacts being matched, it will be treated as a mismatch for that field.

I have made this change to my system and will submit it as a pull request.  Is there any objection to this behaviour?  Are there any pitfalls that anyone can see?

[Erik Hommel]

Sounds like a good suggestion to me. Would it be an idea to stick this in an extension?