users receiving error when processing temporary contacts

[CnP.Support]

Good day!

Our team has ran the debugging in your instance & has made the following observation.

There is a custom trigger in your instance named: CP_UpdateOppWithRegistrantEventSiteInformation




The Record Type used in this custom trigger is set to "Development Contact" and is seen below, this record type is not active for the set user.




The above trigger crashes our program when trying to create a new contact.

Please review your custom triggers and make sure they are fully functional to ensure all applications work as they should since one issue has cascading effect across the entire platform.

To test the issue we enabled the Record type for 1 transaction and disabled it to avoid any unintended consequences. The following actions were taken:

1: Record type was enabled


2: One of the requested contacts was processed



The Temporary Contact was processed without any issues.

We changed the Record Type back to disabled. Please review your triggers and enable it if you wish to process the Temporary Contacts.

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

[[email protected]]

Yes! Those are fine to create as new contacts.

[CnP.Support]

Good day!

In reviewing the temps you provided it seems like these contacts are new contacts as none of the contacts match the email.

Are we safe to process them as new contacts?

[[email protected]]

26950. We unfortunately cannot disable the multi factor authentication as it is a system-wide security setting put in place by someone higher up than I! It would be great if y'all were able to troubleshoot this without actually needing to log in as the user with their credentials.

[CnP.Support]

Good day!

We are prompted for a code. it is sent to alaq****@yearup.org. Please send it to us.



Is it possible for you to remove the 2 factor authentication for the period of our testing. This is taking way too long and I am sure it is frustrating for you as well and we also like to make sure it works for you.

Unless we can login we cannot test and see your custom permissions and how they are blocking Salesforce from creating contacts. As this is not really a Click & Pledge issue but a Salesforce issue you may want to work with Salesforce if that works easier for you. Unless we can login as the affected user we cannot test this.

[[email protected]]

I seem to not be receiving notifications for this post anymore. Not sure what happened as I did not change any settings. Please try TC-7811 or TC-7664. Thanks.

[CnP.Support]

Good day!

Any update on this? We need to duplicate the issue to determine the objects with the permission issue.

[CnP.Support]

Good day!

Please let us know the first name and last initial of a Temporary Contact so we can test it.

[CnP.Support]

Good day!

Miracles do happen.. they just need patience I guess.

We are in. We will update you once we have one of our developers review this.

[[email protected]]

Code is 30152

[CnP.Support]

Good day!

Please do not hate us for this.. it truly is not our fault.



now we need a verification code.

[[email protected]]

I just reset the password, please let me know if you received the email and are able to log in.

[CnP.Support]

Good day!

We have received the email for changing the email and have verified it. Now we have requested the password but have not received the notice to change the password. We have requested it 3 times and yet no email.

We will update you as soon as we have received the email.

[[email protected]]

This is a screenshot from my setup audit trail. I changed Annie's email as you requested yesterday. I will change it again right now.

[CnP.Support]

Good day!

This is not something we can possibly address over the phone. We need to have access to the account and test it.

Even if you set up an account with our premiere support they have to ask developers to review your custom permissions and our developers do not work directly with clients and support. We have not received any emails to [email protected] regarding this change. Please change it again and we keep an eye on the notice. As of this moment we have no way of checking.