Recurring Donations stuck in Temporary Contact

[franklin]

Client's Recurring Transactions show up in the Temporary Contacts but do not have any actionable matching options. Beneath the Settings Section is blank (where the possible matches and ability to create new contact would normally exist).

They are upgraded to the most current release.

Thanks!!

[CnP.Support]

Franklin,

This is strange since this has never been reported or frankly makes sense within our design. Your page does not look like the following?

[April Harris]

Stuck Temporary Contacts

I also have donations that are stuck with no contact match...
Client is on version 7.3006

[CnP.Support]

April,

May I ask you to upgrade to the latest release (released today) and try it.

There was an issue that was addressed in this release with orphaned recurring transactions. I am not sure if your case is the same but I like to see if the new release fixes it.

Please let me know.

[April Harris]

Upgrading to the most recent package did not fix the issue. Other ideas? Thanks.

[CnP.Support]

April,

Please grant us access to your account so we can review the account.

This condition happens if the master transaction is missing and as a result the conversion returns error. We need to check if the order number associated with the transaction has a master transaction in the system or not.

We will review the information once we have access to the account.

[April Harris]

Access granted.

[CnP.Support]

Thank you April,

We will review and let you once we have know what is going on with these transactions / contacts.

[CnP.Support]

Good day April,

One of our developers reviewed your instance and realized what is going on.

You have a custom Trigger "insertPayment" which is based on Opportunity and is causing this error:

CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, insertPayment: execution of AfterInsert caused by: System.QueryException: List has no rows for assignment to SObject Class.GlobalVariables: line 21, column 1 Trigger.insertPayment: line 13, column

In our application we process in the following order:

1. Account
2. Contact
3. Transaction
4. Custom Question
5. Campaign
6. Campagin Members
7. Recurrings
8. Case creation for decline
9. Opportunities
10. Soft Credits
11. Opportunity Contact Roles

When all are set up we will remove the temporary contact and consider it as processed.

In your case the error is being caused when creating the Opportunity because of your custom trigger.

When you try to process the Temporary Contact the second time you will see the following error:

Before Insert or Upsert list must not have two identically equal elements

which should be expected since the transactions are already in the system and now you are forcing a duplicate.

I hope the above helps with resolving the issue. If you need any further help please let us know.

[April Harris]

The only triggers I see on Opportunity are the NPSP triggers. I thought CnP played nicely with NPSP? Also, this org has had CnP or over a year and has not run into this issue previously, so I'm wondering why now?

The NPSP trigger I believe you say is causing this reads as

"Last Modified By

Contacts & Organizations, 3/29/2013 10:01 AM"

If this is an NPSP CnP compatability issue, then this org shouldn't be the only one affected and I assume it would be something CnP would need to adjust to in order to work with the NPSP?

[CnP.Support]

April,

The trigger is called: insertPayment and it is not an NPSP trigger since it does not have the NPSP namespace prefix.

This trigger is a custom trigger based on our analysis.

Nothing has changed with our system and the error is being caused by this trigger which is a custom trigger by the account.

[April Harris]

I'm sorry, I must be going blind. I do not see that trigger. Below is what I see for Apex Triggers:

[CnP.Support]

April,

Sorry for the confusion-- this is my mistake.

I gave you the answer for another post and as a result now everyone is confused. We are still reviewing your case and we believe we have found an issue. Our developers & testers are testing and we will have a solution by tomorrow.

I will keep you posted and again sorry for my mistake.

[CnP.Support]

Good day April,

We believe we have figured out what the issue is. The problem is with recurring transactions that have started before we had contact matching. It is a combination of many factors coming together that we believe is causing the issue.

We can send you a link to update the instance or if you want we can upgrade it and test it. We don't want to update your instance without your permission.

Let us know how you wish to proceed. If this patch works for your case we will go ahead and release it to the appExchange.

Thank you and sorry for the inconvenience.

[April Harris]

No problem! An update to anyone in this thread - Kami and team created a new release to fix the issue. Thanks to the CnP team for being so responsive and helpful!