Matching Fields Error

[esowers]

We are using FaaS to submit payments into Salesforce. In that setup process we found that our submissions were not being matched correctly. Therefore we added two custom fields to the matching criteria on C&P Settings > Contacts/Accounts.

1. First Name - added Nickname__c
2. Email - added npe01__HomeEmail__c

As soon as we added those two criteria we received this message for any new transaction.

Non-selective query against large object type (more than 100000 rows). Consider an indexed filter or contact salesforce.com about custom indexing.
Even if a field is indexed a filter might still not be selective when:
1. The filter value includes null (for instance binding with a list that contains null)
2. Data skew exists whereby the number of matching rows is very large (for instance, filtering for a particular foreign key value that occurs many times)

When we remove the matching fields the error goes away. It appears that we need to set those custom fields as external IDs in order for this to work?

Is there any other solution for adding these matching fields (adding them in addition to the default matching fields)?

Thanks,

[CnP.Support]

Good day!

Please grant us login access and let us know the Salesforce Organization ID so we review your instance.

[esowers]

Login access granted. 00DU0000000IrhT

Also, I did have a ticket with Premier support, however we found a solution before they could jump into our org.

Thanks,

[CnP.Support]

Good day!

This error occurs only when there are too many matching rules. When there are a lot of matching rules with large number of contacts Salesforce chokes. We have not seen this error with the fields you have selected.

Have you always had the name, last name, and email?

[esowers]

The matching seems to work fine with the defaults values

1. First Name - CnP Alias: First Name, First Name
2. Last Name - CnP Alias: Last Name, Last Name
3. Email - CnP Alias: Email, Email

However, the issue is when we add the two extra fields on to First Name and Email. We decided just to remove the additional matching fields for now because we were rolling it out.

Also, I haven't been able to find it in your documentation, but does it require a match on all three fields in order to be considered a match, or will it be considered a match if just First Name/Email are matched (even though last name is selected)?

I have submitted a transaction where all three fields match a contact record, yet it still dumped it into the temporary contact area.