View State Limit Exceeded when processing Some Temporary Contacts

[Simon]

I’m working with A client to track down a glitch with the temporary contacts.

Have you ever run across the Visualforce “View state Limit exceeded” when trying to view a temporary contact.
However it seems to only happen when there's a lot of matches to the last name? that’s the only commonality that we’ve been able to find.

Is that something you’ve run across before?

It only seems to be happening on common names like Williams, Smith etc.. ie things that have LOTs of matches.

On a possibly related note, the temporary contact also has a section called “Attach to Existing Leads”? I’ve not seen that section on temp contacts before.. but they have a Lot of leads (they just launched their marketo integration)

The installed packages are couple versions behind and are in the process to get production upgraded, but its a large complex instance so everything has to be vetted & tested in sandbox before production is updated, so that process takes a bit of time.

Org id: 00D5000000071yL
You’ve been granted access.

Here’s a link to a Temp contact that doesn’t render: https://yearup--cnp-paas.na32.visual...8000003CJQHEA4

[CnP.Support]

Good day Simon

The instance is using an extremely old version.

May we upgrade them and then you test?

see:

[Simon]

Do NOT upgrade!

We're in the process of updating, but with all the automation they have in their instance and the number of users that could potentially be affected, everything gets tested out in sandboxes before being allowed to deploy to production. We're in the process of doing all that but it's not ready for production yet.

[CnP.Support]

Good day!

We will not upgrade.. I think that is what you meant

Version 9.3 had an issue with large number of Contacts. Upgrade may solve this.

[Simon]

Great we'll try and accelerate our testing then.

One last thing, What does the 'Attach to Leads' section under the temporary contacts do?

[CnP.Support]

Simon

Please include a screen shot. I am not sure I follow.

[Simon]

Sure thing, here's the url for the Temp Contact in the screenshot.: https://yearup--cnp-paas.na32.visual...8000003CjXyEAK

hm your photo uploader shrank it to itty bitty size. here's the image url: http://kellpartners.com/temp/yearupTempContactLead.png

[CnP.Support.AM]

Good day @Simon

Please refer to the following link: https://help.salesforce.com/apex/HTV...tm&language=en

In C&P Temporary contacts we shows the existing leads which match's the information with the temp contact and allows them to convert into Contact.

Hope that answers your question.

[Simon]

Hey again,

We've got things tested and are in the process of updating the packages.
Class and PAAS packages updated but events repeatedly fails with the following error:

1. Unexpected Error
The package installation failed. Please provide the following information to the publisher:

Organization Name: Year Up, Inc.
Organization ID: 00D5000000071yL
Package: Click & Pledge Events
Version: 4.4007
Error Message: The post install script failed.

I've refreshed the your Access period.

Please go ahead and try and update it and hopefully it will be successful for you.

[CnP.Support]

Good day Simon

We updated your instance as requested. Please check it and let us know if we can be of more assistance.

[CnP.Support]

Good day Simon

Sorry but the previous post is not quite accurate. We upgraded your instance to release 4.4005 which is the prior version but were unable to upgrade to 4.4007.

Please grant Salesforce Support access so we can work with the support team at Salesforce and figure out what is going on.

Thank you.

[Simon]

Thanks for the update.
I've granted SF Support access you should be fine to proceed.

Thanks
Simon

[CnP.Support]

Good day @Simon,

With the help of Salesforce Support we have identified the following 3 triggers that are failing the post-installation script:

1. CP_CreateCampaignMember
2. CP_UpdateOppWithRegistrantEventSiteInformation
3. CP_UpdateRegistrantAndAttendeePaymentOptions

Please disable these 3 triggers and try the upgrade again. We can also do this for you but we need direct login access through an admin user since this cannot be done through the support access we currently have.

Please let us know if we can be of more assistance.

[Simon]

Thanks for the deep dive. I'll confer with the client on what the best approach is as there's some pretty critical business logic tied to at least one of those, but they're also slated to be removed with their next major internal update (which is why it worked in the prelaunch sandbox).

-Simon