Good day Simon
This issue has been addressed via support earlier today.
The problem was fixed by reducing the number of matching fields for unique contact. The instance has over 200K contacts and as such Salesforce is not able to match against the many selected fields. We always recommend first name, last name, and email as well as their associated alias'. Matching against street may result in such errors given those fields are not indexed by Salesforce.
Please let us know if we can be of more assistance.
-
Data Skew error
I could really use some help tracking down what's giving me the data issue, I'm getting dozens of thse emails, it appears that something is causing the the processing on the C&P Data entries to fail, but debug logs aren't of much help. The org ID is below and you've been whitelisted. I've updated to the latest (as of this morning) packages and am still getting the error.
Here's a copy of the error emails.:
Sorry, but we have encountered an error while posting the data to your Salesforce account.
Additional information:- Order number: 1610051216396313553
- Contact name:
- Transaction Result:
- C&P Data ID: 550
- Organization ID: 00D36000000v7m7
- Organization Name: [redacted]
- Applications : Application Name: Salesforce:CnP_PaaS_Evt:BoxOffice- Version Number4.2015
Installed Packages: 4.3000-4.2015-9.7010
"Non-selective query against large object type (more than 200000 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)"
Please check the following link for details:
https://na30.salesforce.com/a1A36000001Uq7A
Leave a comment: