nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

DBV to NXT Recurring Gift Conversion

Shelley Bell

Hi all - Just completed the conversion to NXT with the majority of the gifts set to automatically run on July 1. I ended up with 36 exceptions after the batches were created and I have no idea what the problem is. I moved all of the exceptions into 1 batch so that I could process the remaining gifts. For the exceptions, the credit cards were charged however there is a problem with the gift info needed to post to RE. I did find that if I change the appeal, the gift validates. However, this will probably not correct the underlying issue as I do not want to have to do this every month. Has anyone experienced this and have a possible solution?

Find more posts tagged with

RaisersEdge7 Databaseview

Comments

Shelley Bell

I have since found a solution, so I am adding to my post in case others have the same issue.
First, if you have an NXT batch with exceptions, select Edit Gifts and the gift list will appear to the right. Hover over the red exception triangle, you will be able to see the error which caused the exception. In my case the majority of the errors were “Gift date is invalid for appeal with ID”. The problem appeals dated back to 2017, 2019, 2020 or 2021. When I investigated further, the appeal on the gift record had an end date. After I removed the end date and then validated the batch, the gifts were “freed”. Strange that the RGs were able to run in DBV for 5,6,7 years, but not valid in NXT. Hope this helps someone else. ?

Jillian Kramer

Hi Shelley and all, Thank you for your post.

We now have run into the exact same issue. That said, I do want to flag that removing the end date feels like a messy workaround rather than a real solution, and the logic still doesn't sit right with me.

The whole point of setting an end date on an appeal is so that new pledges, recurring gifts, or one-time gifts don't get coded to an appeal that has already ended. But for existing recurring gifts and installment payments, the payment should always carry the same appeal as the original commitment gift — that's just how it works.

So the appeal needs to remain usable for those payments even after it has ended. Removing the end date entirely defeats the purpose of having one. The end date and the Active flag should be doing two different jobs, but right now they seem to be treated as the same thing. Has anyone found a better way to handle this?

This also raises another question for me around reporting. When doing year-over-year analysis, the appeal end date is a logical and clean way to identify when a campaign concluded. If we can't use the end date field for its intended purpose without breaking batch processing, how are others tracking when an appeal has ended for reporting purposes? Is there another field or method you're using to differentiate active campaigns from concluded ones in your YOY analysis? Would love to hear how others are handling this!

JoAnn Strommen

That's interesting to me that you didn't have to keep appeal active in db view. I have had to keep several appeals active for recurring gifts begun 5+ years ago. When appeal was inadvertently marked as inactive, got errors in db view. Had to put note on appeal record to keep active for Smith and Johnson recurring gifts.

Alexis Cruz

We had the same problem recently. And as you did ended up removing the appeal end date. I hope a better solution comes soon.