Connecting Connect Campaign to Salesforce

[jmueller]

Ok, we are all set. Many many many thanks. Regards, Jan

[CnP.Support]

Please see below:



it is all there and you may set it up accordingly.

[CnP.Support]

Good day!

I just check account # 20904 and no more transactions are remaining.

You are all set.

Let us know if we can be of more help.

[jmueller]

And back to my original question. If we are now updated and connected, what do I need to do to see the Salesforce Campaigns tab in Connect?

[jmueller]

Thank you, I think we're almost there. Using custom report I was able to see transactions a little further back than 90 days, to the end of 2015 when we get a spike in donations. It seems like all the transactions are there but in the downloaded report, there is no "posted" column like there is in the 90 day view. I tested a few and they are all in Salesforce, but I was just curious.

I think it's reasonable to assume that all the transaction have been posted to Salesforce, but if there is no harm, why don't you go ahead and push any past transactions that may have generated an error. I expect there will not be any, but it would be useful to know whether or not there were.

Thank you, Jan

[CnP.Support]

Good day!

As for the OAuth the answer to your question is YES.

We provide a report for 90 days by default. You may create custom report dating back in blocks of 90 days.

I will push all your legacy transactions that are in the system but have generated error. Is it OK to post them?

[jmueller]

Thank you. So what I understand is that the legacy connection may have been working even though in our SF Connection tab in the Portal showed we were not connected (meaning the new OAuth2 connection had not been enabled. Is that correct?

I already updated/enabled the SF connection tab earlier today when you first mentioned it. Would doing that erase any past error log entry? I wasn't quite clear on what you were saying about that, but it sounds more likely that our legacy connection has been working.

In any case, I checked transactions via Connect as you suggest and everything seems to have been posted except for a series of fraud charges that I didnt know about until now. We have not been using Connect so I presume Connect is able to read all C&P charges and see whether they have been posted to Salesforce.

However, the transaction tab in Connect only goes back 90 days, not quite to the time we did the upgrade. How might we look another month or so before that?

Thank you very much, Jan

[CnP.Support]

Good day Jan,

Please note that what you see, behind the scene could be different.

When we changed the Salesforce connection to OAuth2 we maintained the legacy connections. If your account is working now it means the legacy connection is working and that will post. To make sure all clients switch to the new method we show the status of OAuth2 connection in the SFConenction tab.

Currently we do not show errors since once an error occurs we post it once and then disconnect the account. Per your statement your account is posting so it means the old connection is still active.

Please visit the Connect transaction tab and review the Salesforce connection column. If any transaction has not posted you will see the status as NOT POSTED.

I suggest that you first go to the Portal > Account Info > 3rd Party > SF Connection tab and enable the connection. Once connected go to Connect and review the transactions.

As also stated before we can push all the historical failures back to your Salesforce.

Hope that helps.

[jmueller]

I'm sorry. I forgot I was in the Connect section of the forum. The transactions I am referring to were not through Connect but through a C&P checkout page. We have not had any donations via Connect that I am aware of.

[jmueller]

Thank you for checking. I guess we would be interested in data from 2014 and 2013, but it's strange that you don't show a more recent error. Is it possible that our connection has been down that long--that seems unlikely, especially since I can see 2015 transactions in Salesforce. Is there a way to make sure that we catch any missing 2015 and 2016 donations?

[CnP.Support]

Good day Jan,

Please see: http://help.clickandpledge.com/custo...ticles/2084081

The last error we see in the system was from 10/21/2014. If you want we can push it back to your Salesforce. Once we report the connection error the connection will be removed and no longer reported. We report this once to avoid overwhelming your servers. We have had cases where a site under heavy traffic was disabled and our notices literally crashed their mail server with tons of posts about connection failure.

Do you want us to push the data back to Salesforce for the ones we see. WE see 2 in 2014 and 4 in 2013.

[jmueller]

Thank you again. I don't suppose there's a log that shows how long our connection has been down that would be easy to check? We haven't had a lot of donations since the update in January but we've had some. How do we post those transactions to Salesforce?

And we did check and enter emails for error notifcation, thought we did that first time as well.

[CnP.Support]

Good day Jan,

If you add the error notification email we will notify you if there is a connection issue. You may add any number of email addresses for notification in case of error.

Have you added your email to the error list?

[jmueller]

Never mind about the URL, I entered NA14.... and that worked. We are connected, but still wondering what may have happened and whether we need to monitor the status of our connection.

[CnP.Support]

Good day!

With each upgrade of the API Class Library you need to update the connection. If you were using the legacy UserID / Password / Token combination it would have maintained connection for as long as your password or token was valid. Once either of those expires the connection will be disabled.

Please enable it now using the new OAuth2 method as provided in the tab in the portal.

Hope this helps.