E-checks not making into the Bridge

[Carl Paulsen]

We have built an integration that handles C&P transactions to match our customized salesforce database. We use the "bridge" data and turn off the normal C&P Opportunity creation and linking to Contacts and Accounts in Salesforce. Everything works fine for most transactions. But e-checks don't make it into Salesforce, and in fact, when I look at the bridge data in Salesforce, these e-check transactions aren't there. C&P support has said the issue is in our programming but I can't understand how our programming could prevent the data from making it into the bridge in the first place.

Interestingly, the data DOES make it into the PaaS table in Salesforce, and the person who made the transaction gets put into Temporary Contacts (I think b/c we've turned off the matching and Account and Contact creation settings in Salesforce). The person making the transaction is in the Salesforce database and shows up in the Temporary Contacts record as a possible match. If we try to manually merge the temporary contact with the match, nothing appears to happen and the e-check transaction still doesn't move into this Salesforce record.

We noticed that there is an apostrophe in the xml <windowname> field and have suspected there may be problems related to that.

Thanks for any help.

I should note that Support suggested I post here.

[CnP.Support]

Good day!

This case was reported in a previous discussion. In reviewing the instance we determined that there are triggers written off of the Bridge that is blocking it and generating error.

Anyway you can disable triggers on the Bridge & test? We have tested this a great deal and it works.

I believe this was originally posted by Baird. Is this related to that case?

[Carl Paulsen]

Hi, thanks for the reply, and yes, it's the same case. I work with Baird and had posted that case. I had a question about how our programming could block data going into the bridge because to me it seemed the data would go into the bridge in C&P BEFORE our programming got involved. When I asked about that, the person who was responding to my questions directed me to post here. So you are saying that our programming CAN block data going into the bridge? How? That might help us track down where the problem is.

I'll check to see if we can disable the triggers, but if we do that, we won't be testing our system. I know the data makes it into the data object in SF, and the temporary contact is being created as I'd expect (since we turn off the C&P system for matching to Contacts). It's just that the data never makes it into the bridge where we grab it and process it.

[CnP.Support]

Good day @[Carl Paulsen]

Here are the error messages we see in our log files:

ManageCnPDataTrigger: execution of BeforeInsert
caused by: System.NullPointerException: Attempt to de-reference a null object
Class.ManageCnPDataController.beforeInsert: line 30, column 1
Trigger.ManageCnPDataTrigger: line 5, column 1
//
ManageCnPDataTrigger
Class.ManageCnPDataController
//

These triggers are not ours and are custom made.

Are these yours?

[Carl Paulsen]

Yes, these are ours for dealing with our customizations of SF and how we want to handle incoming data from C&P. We'll take a look and get back to you if we need anything more. Thank you for this.