Donors and Donations are not posting to Salesforce

[jadekeena]

OK looks like we're all set! Your note on notifications makes sense for sure! my only concern is that we didn't get any notifications at all when this lost connection happened, nor did we get them when the connection got "kicked" as a result of the error. I've got my email address saved in the notify box so I'm not sure why that happened.

[CnP.Support]

@JadeKeena,

Please keep us posted on what you find out.

As for notification- we already send notification as it has always been the case. The notification area allows you to enter as many emails as you want in the box separated by semi-colon. if we lose connection we will notify you but only notify you once. To repeatedly notifying you is asking for trouble. Back in the days we had notification for every transaction, if it could not connect. A client was doing a great fundraising and they received 50K donations over the weekend. The connection was lost on Friday because their token had expired in Salesforce. With that many donations they ran out of Salesforce API and as a result they were getting an email with each donation from Salesforce and Click and Pledge. By the time it was done they had 250K emails in their mail server queue which crashed their email server.

Hope you appreciate the extent of the issue.

Since then we simply send one email when connection fails and will no longer notify with subsequent failures.

Please let us know how it works.

[jadekeena]

Sorry for the delay, I was out of the office. This solution looks great so far - I logged in and reconnected all the accounts with this method and they seem to all be connected. I'll test each one with donations today and will circle back as well. My only other feature request would be a notification mechanism when connections fail, especially the one direct connection. We went several months with this issue without realizing it because we just assumed everything was connected.

Thanks for your help and work on this!!

[CnP.Support]

Good day!

We just went live with the feature that can solve this problem. We have added connection sharing so you can set up one account and then have all the other accounts use the connection for the selected account.

Please see:




In the SF Connection you will see an option under Connect Type called: Shared with another C&P Account.

Once that option is active a secondary pull down menu will appear showing all accounts that YOU have access to and have direct connection to Salesforce. All your accounts can now use the connection used by that account.

We have not yet announced this but our internal tests show that it works. We love to see your experience and once we are sure it works with your configuration we will announce it to others.

Looking forward to hearing back from you and thank you for working with us to resolve this Salesforce peculiarity & limitation.

[CnP.Support]

Good day!

It is currently under testing. Our ETA is next week.

We will keep you updated.

[jadekeena]

Are you able to give me an ETA on an updated date, if not 4/18? I need to keep our chapters informed and will be out of the office following the 21st so I'd like to communicate the ETA as soon as possible,

[CnP.Support]

Good day!

This is still under test and development. We will update this when we ready to release.

This is a major change in how we do the connection and the change has the potential to impact all clients. We will update this post when we are closer to release.

[jadekeena]

Hi, just wanted to check in and make sure everything's on track to deploy a fix by April 18?

[CnP.Support]

Good day!

We are working on this now and will have a release next week. We have thought of a work around dealing with the Salesforce limitation. It requires major update to our system but our team is working on it. We are planning for a release by April 18.

hope that answers the question.

[jadekeena]

Hello! Just wanted to check in here to see if any progress has been made towards a solution. Please keep me updated asap today. Thank you!

[jadekeena]

Fantastic thank you!

[CnP.Support]

Good day!

Here is another article: https://help.salesforce.com/apex/HTV...est_manage.htm

see:



We are submitting a support ticket to Salesforce asking if the "default" can be changed.

In the meantime we are working on the shared connection idea to bypass this limitation.

I am adding these notes to make sure this thread is up-to-date.

[jadekeena]

Great thank you so much!

[CnP.Support]

Good day @JadeKeena,

Our update to OAuth2 appears to have caused this issue. Please see: https://success.salesforce.com/answe...a=BESTANSWERS&

We used to work with UserID, Password, Token combination. The method was problematic with expiring passwords every x number of days, typically 45 days. Clients were losing connection when their passwords were expiring. Switching to OAuth2 made it independent of passwords and as such removed the uncertainty around passwords. Given the old method is active in the background for backward compatibility those clients that are not using the new method are still active. This is why we have not heard back from the clients with large number of connected applications.

Strange limitation indeed.

We are working on a solution with potentially connection sharing among accounts.

Sorry for the inconvenience -- Salesforce limitations and hidden undocumented features makes us a bit uneasy at times..

I will keep you posted.

[jadekeena]

Glad you were able to replicate! I will update all accounts with our info now. Thank you for keeping me updated!