GiveBIG transactions not being added to Salesforce

[CnP.Support]

Great.

So the issue is resolved and closed.

Please let us know if we can be of any further assistance.

[[email protected]]

I just found that I didn't have the NPSP Opportunity Rollup Settings correct. I need to have the "Always Rollup to Primary Contact" checked for this to work correctly. Thanks for your help.

Charlie

[CnP.Support]

Good day Charles,

One of our developers is reviewing this and once we have an answer we will post it back. Just keeping you informed.

[[email protected]]

Thanks for your help. I was able to make these changes and confirm that Seattle Foundation GiveBIG transactions are being entered into our Salesforce Instance.

I do see that the Opportunity RollUps are not working for C&P opportunities. When I add a similar Opportunity directly into Salesforce (same Opportunity Record Type = GIFT) it does rollup correctly. So there must be something I am missing in the settings for a C&P created opportunity. Thanks for any tips you have. You still have access to our Org (00DA0000000Ceys) if this is helpful.

My contact (003A000000rmx8d) is the one which shows all the opportunities as well as the C&P Opportunities in the related list. These are the ones that are not being included in the RollUps, even though they are also listed the Opportunities related list all all opportunities.

Thanks

[CnP.Support]

Good day Charlie,

Thank you for granting access - it saves a lot of time. Also please refer to GiveBig as the Seattle Foundation GiveBig since we have a product called GiveBig and it can cause confusion.

We reviewed your instance and found out the issue. Our posts are generating the following error:

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)

Your organization has 114,233 records and in the contact matching you have selected "Legal Name" and "Nickname" as additional fields for contact identification in addition to 5 email fields. While the email fields are not an issue, the Legal Name and Nickname are not indexed fields and majority are blank. The search query is returning a lot of NULL returns and since they are not indexed the error is being generated.

We have removed the Legal Name and Nickname from the list of matched fields and cloned your transaction which had generated the error. The cloned transaction worked and created a temporary contact. We suggest that you do not add those 2 fields to the matched fields. We did not want to post test transactions to your instance without your permission.

To view the status of a transaction in the future please go to C&P Data tab and identify the transaction. Currently you will see 2 posts to the C&P Data. The first one was done yesterday by you on 4/14/2014 which had generated the error and the one we cloned today which is OK and its contact has gone to the Temporary Contact.

Click on Transaction-001 and scroll to the bottom of the page and you will see the error I had posted above.

Let us know if we can post additional tests or if you post tests let us know so we can review the posts making sure all is working.

[[email protected]]

Hi,

I'm setting up our Salesforce Click & Pledge PaaS system for the first time and have been testing with our GiveBIG donation page. My test transactions don't seem to be making it to Salesforce and I don't know how to find them or debug this. As far as I know I have configured the C&P Portal and Salesforce correctly, but I must be missing something.

Here is the information I have on one of these transactions:
Order Number: CNP:1404141805595744492
C&P Account: 19991
SF Org ID: 00DA0000000Ceys
I have granted C&P access to our SF Instance to help.

Thanks,

Charlie