Validation Errors in Webview Batch

Keith Wilson · April 25

We had an issue that started yesterday and filed a case with Support. Not sure how soon we will get an answer, but I want to know if anyone else is seeing this bug? @Anthony Gallo
When a recurring gift transaction fails it creates a $0.00 gift in the batch. Now those gifts are showing validation errors and won't let me approve the batch. Since the batch cannot be viewed in database view until it is approved, we have no way to fix the validation error in database view.

47e6570484a8eb2b7b599f1569943415-huge-va

64c1af15f1e5e5be6386474b623c0de0-huge-pa

Keith Wilson · April 25

In addition, we are getting errors for “Gift Constituency Code” which is not an available field in web view gift records. Somehow it is defaulting to one of our Constituency Codes but not honoring the constituency of the donor record. Again, no way to correct this error: field doesn't exist in web view, batch doesn't exist in database view.

53c0b4895cbdb5673dd30ccbea07b02f-huge-gi

Xep Campbell · April 28

@Keith Wilson
I am having a vaguely related issue where a gift was imported into a webview batch from Almabase with the incorrect Campaign, Appeal, and Package. When I changed to the correct campaign and appeal and removed the package then saved, it did not save the removal of the package, which is not a valid package for the correct appeal. Since it is not a valid package, I am getting a validation error that I cannot fix. I have a ticket open about it.

I also saw the error with the $0 payment. I moved the gift to a different batch for now so I could approve the remaining gifts.

Keith Wilson · April 29

@Xep Campbell:
I also saw the error with the $0 payment. I moved the gift to a different batch for now so I could approve the remaining gifts.

Yes, I am doing the same for now. I don't want to delete the $0.00 gifts because we can retry the gift once the donor provides updated information. But the gifts have to be approved before you can retry them. ?

Angela Pizzolato · May 5

@Keith Wilson Yes, we are having the same issue with some failed recurring gifts from last week.

Juliana Sheffield · May 6

@Keith Wilson I'm having the same issue. BB says they are working on the issue.

Keith Wilson · May 6

Update: This issue appears to be resolved for new failed recurring gifts in a batch, however, we are still unable to validate/approve any failed transactions between April 23-29. Being able to approve the $0.00 gift enables us to retry the failed transaction when the donor updates the card info.

Kelly CampionSocol · May 7

@Keith Wilson We have had validation issues with our recurring gifts due to the Campaign being made inactive. Our FY runs from April to March and our Campaigns match the fiscal year. I simply edit the gifts showing the error to the new Campaign code in order to correct the error message and commit the batch.

I did go back to our online giving page and update the default campaign to the new year so we only have the validation issue for gifts created in a previous year using the giving page in question.

Kelly CampionSocol · May 7

@Keith Wilson
Could it be possible that somehow the code mapping was switched in tools to the incorrect code? I know this would only apply to new records being created with the incorrect constituency code.

My other thought was that perhaps an inactive constituency code exists on previous gifts and somehow Batch is pulling from previous gift constituency codes instead of the constituent record.

Not that this helps correct the batch issues but it may help figure out where the problem is originating.

Keith Wilson · May 7

@Kelly CampionSocol
Interesting thought. Our org receives check donations via a lockbox and uses a Power Automate flow to import the transaction file from the lockbox to a NXT batch. We aren't sure if the issue is somehow related to the PA Flow and how those gift records in the batch are created.

Validation Errors in Webview Batch

Comments

Categories