Urgent - Cannot create new Contact in Salesforce from Tempory Contact

[Mark Stark]

When I try to create a new contact from CnP Tempory contacts, I get the following error; it is a normal contact with a first and last name. If the contact already exists in SF, there is no problem.

Insert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, Please enter First Name: []
Error is in expression '{!SaveItem}' in component <apex:commandButton> in page cnp_paas_evt:eventtemporarycontact: (CnP_PaaS_EVT)



An unexpected error has occurred. Your solution provider has been notified. (CnP_PaaS_EVT)

My organization ID is

00Di0000000eL4T, access has been granted

[Mark Stark]

I think the problem is duplicate temporary contacts being created when there isn't an immediate match. If I put in a contact that has a match, I create an single opportunity attached to the contact. But when there is a temporary contact, there are two created for the single entry. If I combine them, I can process them; but I don't understand why two are being created. Thank you

[CnP.Support.AM]

Good day!

It seems that you are referring the temp contacts which has been created through Events. Those are not duplicate temp contacts but Registrant and Attendee.

From the Event version# 4.1x we simply show all temps in one view instead of showing up separately for attendees and registrants / payers. We noticed that most clients do not see the attendee temps and are ignoring them - in the release notes we state that these contacts are now one and the view at the top shows you that they are attendees.

Regarding the error, it seems to be issue with validation rule you have on Contact object. However, could you please let us know the temp contact name which is throwing above error.

Looking forward to hearing back from you.

Thanks,

[Mark Stark]

There are four temp contacts now (that have attendees and payers). They all show the same behavior - you could use TC-015 (Disneyland Resort). We do not have any validation rules on Contacts, but we do have SF duplicate rules enabled. I guess the duplicate rules would fire if C&P is converting both the payer and attendee at the same time even though only one is selected. If I click on the box at the bottom of the form to select "Potential Matches in Temporary Contact List" (see attachment) then it will create a new contact normally. I see now where I can select the view and see payer vs. attendee. Thank you

[CnP.Support]

Good day Mark Stark

In reviewing your instance we noticed that you have NPSP & Person Accounts. As a result of Person Account's presence a few fields are blank in the settings. C&P does not support person account and NPSP also does not support NPSP.

We did a work-around and manually updated those fields in the settings with businessaccount as the account type. Moving forward you should not experience any issues.

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

[Mark Stark]

Please do not do this in the future!!! Please reverse any changes that you have made to my account - where did you make these changes??!!! These donations should not have been processed since they were entered incorrectly!! Did you make that change in the C&P settings or in Salesforce? Please send me the information immediately!!

You have caused auto-send of emails to donor email addresses even though we have separately notified them already. I did not want the Temporary accounts processed since they were entered incorrectly!!! I do not want the blank fields populated, most of our donors are going to be Household Accounts, and I do not want them processed as Business Accounts Thank you,

[Mark Stark]

We are NOT USING THE PERSON ACCOUNT SETTINGS!!! WE HAVE NO PERSON ACCOUNTS AND WE HAVE BEEN USING THE NPSP FOR THE LAST TWO YEARS!!

[CnP.Support]

Good day!

In C&P Settings the field: cnp_paas__Account_Type__c was blank.

If that field is blank the Event Temporary Contact will not be processed. Contacts also will not create since we do not know what account type it is.

In your system Person Account is present and as such there are 2 types of accounts that may be set: Person Account or Business Account. If neither is present our system cannot work - as I stated C&P is not compatible with Person Account and its presence requires certain fields to be set so we know how to move around the objects & their requirements.

Sorry for the inconvenience but we tried to resolve the error you reported and the solution is to have data in the field which is blank. As requested we removed the value in the field, so the Temporary Contacts will not work moving forward.

Please see the Person Account fields in your instance:




Also:




As stated, currently our application does not support Person Account presence since these fields are blank. To give you a bit more insight - our app detects the person account presence and looks for the type of account, namely Person or Business. If the field is blank, given Person Account is present, we do not know how to deal with the account. So we work fine without any issues if Person Account is installed & disabled (not used) but we need to have an account type.

If that is not how your flow works, then our system will not work. Please note that this is also stated in our application on AppExchange, that we do not support Person Account.

Sorry again for the inconvenience. If you decide to uninstall the event please let us know.

[Mark Stark]

URGENT - TEMPORARY C&P CONTACT PROCESSING NOW DISABLED!!! Whatever change you made now makes it impossible to process temporary contacts. Previously, I could select the duplicate temporary contact, and then the new contact would be created. Now, this no longer works, I am getting the error whether I run it with the duplicate selected or not.

[Mark Stark]

Thank you! I can now select duplicate contacts and the transaction will process. It would not process after you made the change. I was also upset that several temporary contacts were processed overnight. I have workflows that automatically send acknowledgment emails to the donors - they will be confused because our admin had entered the donation incorrectly (should not have entered a company as an individual), but had real email addresses. So, now individuals at the company will get thank-you emails with names like "Dear Disneyland". Thank you.

I have not had any trouble processing unduplicated Temporary Accounts through C&P with the old settings. My problem was with the duplicates created when both the registrant and the Attendee are created by a specific Event type I have set up for donating items.

[CnP.Support]

Good day!

The only change in your instance was manual addition of "Business Account" to the C&P field: cnp_paas__Account_Type__c

No other changes were made to your account and that has since been reverted back.

& we read all posts the same way with all caps or all lower case. We are also trying to help you resolve your issues and have no intention to misguide or cause havoc with your instance. We have had clients that have had Person Accounts with the same issue and once they choose what type of accounts they want to use moving forward we have resolved their issue so they use the app. Prior to a few changes which were made a long time ago, we did not support Person Account - if it was installed our app would not work- period. Given Salesforce's inability to revert a Person Account to a regular account, once it has been enabled, we tried to come up with work around.

The work around that was in place is not being followed through in the new releases as we no longer carry all the code for this exception. Our goal is to rid our code of all the signatures of Person Account in the future as it is limiting addition of new features. Every feature has to account for all the variations caused by the Person Account.

We know why this error is happening and one of our developers has informed us that we can add a line for the exception to account for the NULL condition. We will add that to the next release update and if you wish to be on the interim release we can update your instance next week.

We apologize again for the inconvenience but please note that in release 10 we will be removing all provisions for Person Account presence.

[Mark Stark]

OK, is there a way to stop two Temporary Contacts being created, or is that going to happen every time there is an unrecognized donor? Thank you

[Mark Stark]

I am sorry for my strong reaction. I first realized it happened after being contacted by a confused donor. I would like to evaluate changing settings on the system to better process temporary contacts. Is there a way I can make the change you made so I can test it's effects in a controlled manner? Or can we schedule a time to do it when I can turn off the auto-responder and emails to donors for testing? Thank you

[Mark Stark]

I would like to be on the interim release of the software. However, from your comment, I understand I should never upgrade to release 10 since it won't work with person accounts, is this correct? And it is the same for anyone like me who chose person accounts a long time ago and cannot change it, correct?

Thank you,

[CnP.Support]

Good day!

Please see this link: https://na25.salesforce.com/a2O31000000QKqE




We made a change in your instance so the Standard view of the object does not redirect to our VF page. Our developer updated your instance using the developer console and manual query, but you could do it this way also and it is easier for you to interact with a tab.

Simply go to that tab and EDIT it - Account Type should say: businessaccount

Once you are all set and want us to revert you back to the old way just let us know. We will go and add the redirect to the VF page.

Please (Please please please) do not make any changes to the other fields. The reason we have a redirect on this tab is to make sure clients do not update this manually. A lot of validation takes takes place in our VF pages and if you update any other field without our validation you could break the app.

Hope this helps.

If you want we can also install the app in a Sandbox so you could test your flows. Just let us know if we can be of more help.