One org still having issue w/ verify error

[Perc-BRC]

Hi! I helped earlier last week to troubleshoot an issue where on the C&P Settings page it lists the user as Inactive, and on the portal 3rd party verify page it says "Warning: We have established connection with your Salesforce instance but your application is NOT up-to-date. Please upgrade to the latest release at your earliest convenience." It looks like it was fixed for another user, but it's still broken here.

I just upgraded this org to the latest (9.5) and reverified, but I'm still seeing the error and and users not listed as active in Settings. Can someone hop in and look, please?
Org ID 00D80000000LajA
C&P Account is 35679 (a second account connects through this one as well-- 35634)

Thanks!
Barbara

[CnP.Support.AM]

Good day @Perc-BRC,

After upgrading to latest version, have you tried to re-establish the connection in the https://portal.clickandpledge.com? I see there is NO information in the portal under 3rd Party > Sf Connection for Account#35634.

Would you please try to re-establish the connection now and let us know what you see.

How to Connect Click & Pledge and Salesforce: http://help.clickandpledge.com/custo...rticles/803669

Looking forward to hearing back from you.

Thanks,

[Perc-BRC]

That 3564 account is connected through the other account, via the picklist on the Portal to use another C&P account. Apparently every time I re-verify the main account and it gives the error, it's disconnecting 35634. That's not good! I reset each to its own direct to salesforce link and I still see the error.

[CnP.Support]

Good day Perc-BRC

How many accounts are connected to this one Salesforce Instance? There is a limit of 4 direct connections to a Salesforce instance and once that limits has reached Salesforce disconnects the other connections.

The above is why we have introduced Shared connections where one account is set up as a direct connection and the others use the shared connection.

I am not saying this is the issue but what you are describing is similar to how Salesforce behaves when more than 4 accounts are connected. See: https://help.salesforce.com/apex/HTV...est_manage.htm

So may I ask how many accounts are connected to this single Salesforce instance?

[CnP.Support]

Good day Perc-BRC

I reviewed the account and see that none are showing as connected. Please see:



May I suggest the following actions:

1. Login to Portal and connect account 35634 as DIRECT connection
2. Login to Portal and connect account 35679 as SHARED connection
3. Login to Portal and connect account 29208 as SHARED connection

Currently it seems like none of these accounts are connected.

Please let us know when you have done this so we can review the settings again.

[Perc-BRC]

Hi-

This is done, except #3. That's our Partner test account, not related. I've disconnected and removed it to get it out of the mix. We still don't see anything on the app side, and I got the error when connecting 35634 that my app wasn't up to date.

Thanks

[Perc-BRC]

I think I solved it. This upgrade was installed for only sysadmins, and our API account is not a full sysadmin, but almost (sysadmin minus things like user edits, security edits, etc). It couldn't fully write to the new API Settings fields (didn't have FLS access). I'll have to go through and add them by hand maybe? Any way to upgrade again w/o overwriting the app and losing data?

[CnP.Support]

Good day!

We are working on an update to be released on August 15. Perhaps we can install the PaaS version in your instance by tomorrow and install as full admin to help.

You cannot install the same app again in Salesforce.

[Perc-BRC]

Hi- We can wait for August, thanks. I found all the fields that were new in the objects and gave the profile access. I'll add to documentation that upgrades should always go to all users! Thanks.