Best Of
Re: Is Gift Batch Going Away In Database View after Today 4/1/2026?
I highly doubt that this is the case for the following reasons: I would have expected to receive at least one if not several emails from BB informing of the impending turn off of the feature in dbv as happened when features were turned off in database view of Financial Edge and moved exclusively to web view. Also, not every functionality of gift batch in dbv is already available in wv batch. They are planned, in process of being implemented but not yet operational. I would expect that for something as critical as gift batch, dbv will not be turned off before everything is working in wv.
Re: What's New In Blackbaud Raiser's Edge NXT® — March 31, 2026
I'm very excited about the online constituent forms. However, the documentation does not make it clear as to WHERE one would see these changes come in to be approved, edited, etc…
Will this go through the same Online Data Review process that gifts and event registrations do? Is there a way to test a form and how the data will come in without publishing a live page?
I'm wondering where we can get more information on this as the product documentation is lacking. Thanks!
Editing to add that I've figured out that the data will come in via Online Data Review - so one has to go to GIFT MANAGEMENT in order to process these form submissions.
Re: Constituent Data Collection Solutions - BB Native or Third Party
Based on a post I saw somewhere, Blackbaud is working on developing the ability to have a form that will integrate with RE that is NOT a gift or event form.
I recommend you attend the upcoming Product Update Briefings to get more information!
Does anyone experience challenges reading case central notes on complex cases
Curious if others are running into this as well, when a support case becomes more complex and spans multiple emails back and forth the case notes can get pretty hard to follow.
Each note often includes the entire email thread from prior responses, so you end up scrolling through a lot of repeated content just to find what actually changed or what the latest update was.
It makes reviewing the case history more difficult than it probably needs to be. Are others experiencing this? Any tips or workarounds?
Please vote for these ideas!
If you’ve ever thought, “there has to be a better way to do this in RE NXT/WV,” you’re not alone.
I’ve compiled 20 RE NXT ideas focused on improving database management, reporting, and everyday efficiency. These address common friction points many of us encounter regularly.
The Idea Bank depends on community engagement. Votes and comments directly impact prioritization, and higher engagement increases visibility for the ideas that matter most.
Take a few minutes to go through the list:
✅ Review ideas
💬 Add a comment
🔗 Share with other users
Thank you!
Feel free to add any and all additional ideas in the comments!
Austen Brown
If you could design your prospect pipeline fresh, from the ground up....
what is the one thing you'd change?
I have the rare opportunity to architect the RENXT workflow/coding for prospect id—>qualification—>portfolio assignment. I definitely have my own plan right now, but I wonder what others in this space wish they had implemented earlier.
Thanks!
Re: Query Access of Past Account Holder in WV Remaining?
You’re correct that the queries, lists, and reports will still remain available. The recommended approach is not to delete a user from Security, but to rename the account by adding an “X” or “Z” to the beginning of their username. This makes it immediately clear which queries, workflows, lists, and other assets were originally created by that person. This allows you to sort your list of users alphabetically so that only active users remain towards the top.
This method also makes future cleanup much easier. For example, you can sort by creator and quickly identify everything associated with ZUser_Name, then decide whether any of those queries or assets should be deleted.
Re: Constituent Criteria Options Available in Workflows
@Kathleen Scaglione That is the only option in the “Select criteria” option when setting up a new workflow. What you will likely want to do is use the “Select list” option and have a constituent list that is based on birthdate or some other criteria than making a gift. The caveat I want to make sure people know about these workflows is that once someone goes through the workflow, that workflow will not send to them again. This means that for a birthday process like you alluded too, you would have to create a new one each year or so. Anyway, hope that helps a bit.

Re: Updating Credit Card Information for Automatic Recurring Gifts - CVC now required
Hi All,
I hope to add some clarity on the payments side of this.
When a constituent's existing card token is on file, recurring gifts will continue to process without any changes.
Where the new behavior applies is when a staff member enters a new/updated card for a constituent, whether for a one-time gift or to update a recurring gift's payment method. That flow now runs through Blackbaud's updated checkout experience, which collects the card security code (CSC/CVV) and postal code at the time the card is stored/processed. This is aligned with card network and issuer expectations for new card entry, and collecting CSC & postal code at that point improves authorization outcomes leading to higher approval rates and fewer unnecessary declines.
The CSC requirement for new card entry is not configurable, it's a required part of the new checkout flow. For more detail, see the New Checkout FAQ.
If you run into issues or your experience differs from above, please reach out to Support directly and they can help investigate.
— Jake Gaston, Senior Product Manager, Payments
Re: Tributes as new Constituents...adding deceased people and pets to database
@Amber Mullins This is a tough one, because the tribute module is acting as expected. It wants to attribute a tribute to a constituent, whether deceased or not. I've seen several workarounds for this, but the one I'm most familiar with is using a dummy account like Anonymous and creating the tributes to that record. That way, all of the tributes are on that record.
However, I think it might be better in this case to create the tribute on the record of the pet owner, if known. That would give you better gift tracking for you. You can use the Anonymous record for pets with unknown owners.






