Advanced Donation Form - createDonation endpoint issue

Nick McGinnis

I opened a support case for this as well, but I cannot find a solution and was hoping someone on here has seen this issue before.

We have an issue with the Advanced Donation Form in BBIS and how the transactions pull into the CRM.

If a user is logged into BBIS with their BBIS account and use the ADF to process a transaction for someone else using the createDonation endpoint to create a pledge, when the pledge is downloaded in the web transactions it pulls the up user that was logged in as the constituent and updates their record with the donor information they filled out on the ADF form.

I have samples attached of the object sent to the createDonation endpoint, the response from the endpoint, the record in the transaction table and then lastly the issue in the enhanced revenue batch. The issue does not happen when someone is logged in and they process someone who is making a payment and goes through the BB Checkout process, it only happens with the pledges that are not processing payments that use the createDonation end point. You can see in the transaction sent to the endpoint and the return that no information is sent for the backofficeid, but in the transaction table there is and I assume this is where it is pulling the constituent to update, rather than using the donor information.

The image is hard to see, but it shows the row is going to update Nicholas McGinnis, but if you click edit constituent it has the donor information it is going to overwrite my record with.

Sent to createDonation.json

returned from createDonation.json

What is downloaded from transaction.xml

Issue in pledge.png

Nick McGinnis

@Nick McGinnis

I know this is a very niche and specific issue to our organization, but if someone ever stumbles across this issue we ended up created a BBIS part that forces any non-admin to be logged out of BBIS circumventing the issue.