unusual behavior - temp contacts not creating opportunities

[[email protected]]

Hi! I was so relieved that this got fixed, and then I forgot to post and let you know that all is well. I appreciate it very much. Thank you.

[CnP.Support.AM]

Good day @[email protected]

We have fixed the issue in your instance and processed the errored order numbers.

The issue was, in the presence of NPSP we are having the Async process from Temp which is due to a number of factors to avoid CPU Time and Execution Time exceptions. For example, custom fields in Contact/Account/Opportunity are more than 100 fields in each object, the number of custom mapping and workflow rules, and the number of Opportunity triggers...etc.

Flow rule has a number of parameters to pass the information, in your case, one of the values of the parameter is missing for the required field when it is trying to create one of the records in the object. We tried to debug it but were unable to find the object in the logs.

However, we have disabled the process in Async mode in your instance to avoid the above issue.

Please check and let us know if we can be of any further assistance.

[[email protected]]

I've created a View for C&P Data with errors, so you can also check this for more:

https://npsafoundation.lightning.force.com/lightning/o/CnP_PaaS__CnPData__c/list?filterName=00B5c000007nRBMEA2

[[email protected]]

Thanks - you could look at these order numbers:

28969-2210101646562778586

28969-2209161713273617788

I'm sure there will be more by the end of the day today, if you need more to look at. Much appreciated!

[CnP.Support.AM]

Good day @[email protected]

I see that the two order numbers you shared have been processed successfully. Would you please share the new temp contact order numbers which have the error so that we can review it further?

[[email protected]]

Just adding info in case this is helpful - this mainly seems to be happening when the name and email in the C&P data are not an exact match to an existing contact, but it also happens with some temp contacts for which there is no existing contact. In the case of the existing contacts, is it possible that my duplicate rules are part of the issue? If so, if you could check whether I have those set correctly, that would be amazing.

I'm pasting below a new errors that I've received, as well, in case this is informative:

Visualforce Page: /apex/cnp_paas_evt__EventTemporaryContact

caused by: System.DmlException: Update failed. First exception on row 0 with id a1G5c00000CtX3tEAF; first error: INVALID_ID_FIELD, invalid record id: []

Class.CnP_PaaS_EVT.EventTemparyContact.SaveItem: line 304, column 1

[[email protected]]

Hi there. Salesforce Support investigated this issue, and escalated it to a Tier 3 engineer. According to them, this is being caused by a Click & Pledge issue:

"I heard back from our tier 3 engineer this morning, who found that this issue is being caused by the Click & Pledge package.

The error's last line is:
Class.npsp.TDTM_Config_API.run: line 92, column 1
Trigger.npsp.TDTM_Opportunity: line 33, column 1: []--null--427--(CnP_PaaS)--System.DmlException

This indicates that the error is from "(CnP_PaaS)--System.DmlException". CnP_PaaS is Click & Pledge Payment-as-a-Service. Also, in the debug logs, we see "|ENTERING_MANAGED_PKG|CnP_PaaS".

Though the error mentions "npsp.TDTM", our TDTM framework is called every time our objects are updated, so that does not indicate that NPSP is involved in the error.

Other testing we did confirmed that Opportunities can be created directly in the object without any problems. We also were not able to find any flow/process/automation that is involved in the Click & Pledge temporary contact processing, likely because it is part of that managed package and is not accessible.

Unfortunately, all of that means that this issue is out of scope for Salesforce support. I would recommend following up with Click & Pledge support and sharing the above information with them."

I would appreciate if you guys can look into this further. Thank you!

[CnP.Support.AM]

As stated, the first two order numbers you are referring to i.e. 28969-2209191146508712010 and 28969-2209191058163007256 have been processed automatically since the contact exists in the instance and the other two order numbers i.e 28969-2209192236282680898 and 28969-2209192338160983002 processed from Temp and throwing an error due to the missing parameter in the flow by NPSP.

Regarding creating opportunities before processing attendees, it is expected behavior. Opportunity will be created when the Registrant is processed from temp.

Please contact NPSP to get resolve the issue.

[[email protected]]

Hi - hoping someone can check back on this tomorrow, thank you!

[[email protected]]

Another thing I just discovered - in the instance of Order No. 28969-2209201653563311530, for an event attendee, the opportunity had already been created before the temp contact was processed.

[[email protected]]

Oops - granted! Thanks.

[CnP.Support.AM]

Good day @[email protected]

The access to your instance is expired. Would you please grant us login access so that we can check the above order numbers?

[[email protected]]

Hi - I have an active ticket with Salesforce support about this problem, and the technician I worked with has escalated the issue to a Level 3 engineer team.

I now have an active event, and I've discovered that some temp contacts associated with the event are generating an opportunity, whereas others are not. And temp contacts with any other process are still generating the errors and being blocked from creating opportunities.

Would you be able to let me know what the difference is between the data underlying the orders 28969-2209191146508712010 and 28969-2209191058163007256, which did generate opportunities when the temp contact was processed, and orders 28969-2209192236282680898 and 28969-2209192338160983002, which did not?

Thanks very much!

[CnP.Support.AM]

Good day @[email protected]

We tried to debug the issue and found that one of the flow is missing the parameters which is causing an issue but we unable to find which flow is causing an issue.

Please note that the difference between automatic contact creation and temporary contact process is: in Automatic contact creation, when data arrives, we process the data in QueueableHandler from Contact to Opportunity and in case of Manual i.e. temp process, we split the process into two request, one is Contact and the other is Transaction and when it call the QueueableHandler for opportunity creation it throws an error due to the missing parameter in the flow.

You will need to contact NPSP to get resolve the issue.

[[email protected]]

Yes, thanks! Please do reprocess that. Much appreciated.