unusual behavior - temp contacts not creating opportunities

[[email protected]]

Hi - I've encountered an issue where the processing of temp contacts does not create the opportunities for the related contact.

For example, today for CnP Data-220901-0056122, the temp contact processed without an error message, but no opportunity was created (and then the related flow triggered by opportunity didn't run). There is this error in the C&P Data record:

Upsert failed. First exception on row 0; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, npsp.TDTM_Opportunity: execution of AfterInsert
caused by: System.DmlException: Insert failed. First exception on row 0; first error: UNKNOWN_EXCEPTION, invalid parameter value: []
(System Code): []--null--427--(CnP_PaaS)--System.DmlException

For another contact, who has chosen an autorenewal, the opportunity got created for the authorization for the future charge (C&P Order No. 28969-220901052655384, opportunity ID 0065c00000pGxCyAAK), but not for the actual charge. See C&P Data Data-220901-0056115. Same error message on the data associated with the charge.

On the same day, transactions which were not associated with temp contacts processed correctly, creating opportunities and triggering the respective flows.

Can you let me know what to look into next? Org ID: 00Do0000000I2hr. Access has been granted for one month.

Thank you!!

[CnP.Support.AM]

Good day @[email protected]

Would you please process the Temporary Contact TC-11263 for the CnP Data-220901-0056122 and let us know if you still see that error?

Regarding the C&P Order No. 28969-220901052655384 we noticed it was processed from PMPro. Please note that PaidMembershipPro allows its users to set a different initial payment, so you can offer a discount on the initial payment. In order to accommodate this, the integration runs two separate transactions - a one-time payment for the initial (possibly smaller) payment, and a pre-authorization for the future, larger payment.

In your case, here is the initial payment order number for $88: 28969-2209010526517590918 and the amount to be billed one cycle after the initial payment with $0 i.e pre-authorization order number is:
28969-220901052655384

The actual installment date is 9/1/2023 on which the amount will be charged and the opportunity will be created with the amount.

[[email protected]]

Thanks. When I processed that temp contact, I got an Apex error message:

Apex script unhandled trigger exception by user/organization: 005o0000000IISS/00Do0000000I2hr

npsp.TDTM_Opportunity: execution of AfterInsert

caused by: System.DmlException: Insert failed. First exception on row 0; first error: UNKNOWN_EXCEPTION, invalid parameter value: []

(System Code)

Does this pertain to any custom automated processes we have in place? Or a C&P process? Thanks!

Arnold Brown FYI

[CnP.Support.AM]

Good day @[email protected]

We just reviewed and found no issues, the temp contact was processed without any error.

C&P Data: https://npsafoundation.my.salesforce...Pos=0&srKp=a0c
C&P Transaction: https://npsafoundation--cnp-paas.vis...c000004vdfDAAQ
Opportunity: https://npsafoundation.my.salesforce...c00000pGxQxAAK

[[email protected]]

Hi - unfortunately, still having the issue where the processing of a temp contact is not creating an opportunity. In contrast, transactions which do *not* need a temp contact successfully create an opportunity.

I just did two successful membership transactions through PaidMembershipsPro to test this, with two different results.

1) I used my name and email address (full matches) so the transaction posted to the existing account/contact record without the creation of a temp contact. Order no 28969-2209051406327373110 was associated with opportunity ID 0065c00000pGxWWAA0.

2) I used my name and a different email address for a new transaction, which then created Temp Contact TC-11269. When I processed the temp contact, the transaction was successful. However, no opportunity was created, and there was the same Apex error message in the transaction details as was shown on previous transactions, on order No. 28969-2209051432296590559.

This seems to have started happening since the last update of our org's C&P apps.

Our architect Arnold Brown says that we don't have access to the related trigger code (npsp.TDTM_Opportunity: execution of AfterInsert) because the NPSP doesn't give us access, so we can't tell what's throwing it.

I hope this gives you more info to look into it. Thanks!

[CnP.Support.AM]

Would you please allow us to reprocess the C&P Data for order number 28969-2209051432296590559 to debug the issue?

Looking forward to hearing back from you.

[[email protected]]

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

[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]]

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]

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]]

Oops - granted! Thanks.

[[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]]

Hi - hoping someone can check back on this tomorrow, 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 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!