I found this idea after searching for something similar - the ability to delete or edit an entire committed batch. The RE NXT features grid shows Delete batches as already existing in NXT, and yet buried within the Help info (see attachment) it says:

Delete batches: To the left of the batch's name, select the ellipsis, then Delete.

Only batches that contain no gifts can be deleted. You can move all the gifts from the batch you want to delete to another batch to make it eligible to be deleted.

The ellipsis does not show the delete option otherwise.

What does this even mean and what does it entail? There is no explanation of how to move gifts to another batch - does this mean admins will need to create a query, group load all to a new batch and then fill in everything else manually? What is the use of only being able to delete empty batches? An Administrator should absolutely have the ability to delete batches, and if the only current way to do so is in database view, what does that mean for database view going away, that we can't delete batches at all unless we "move all the gifts"? If I'm creating test gifts in a test batch I want to be able to delete the entire batch after I see how fields move over. I don't want to have to zero out all the gifts or go one by one into records to delete. Let alone if a batch is created erroneously or some other issue when committing.

It is also far too easy to commit a batch in web view; there is no pop-up like in database view regarding applying gifts to recurring gifts and pledges or not; we have multiple donors with an active recurring gifts that also give additional types per year and we need the options at minimum to have:

• the data to be validated for error checking

• To have gifts apply to pledges and recurring setups only when prompted

• the option to have the commit batch reports are finally added - when! - unless commit reports will be automated for every single batch. I as many others need this to reconcile.

• delete batch after committing - I would love to this not be an option in WebView or one admins could toggle off as I never want a batch automatically deleted after it is committed

Another instance where I should be able to delete is running a test registration in RE NXT events using our test BBMS account and a fake credit card. It creates a batch for this test registration and I cannot delete the gift within and as a result the batch itself. Yes I can move the gift to a different batch but it still doesn't help with deleting the fake test 'gift' (i.e. registration) using a test credit card via our test merchant account.

This also leads me to the idea that we should be able to do a test registration on an RE NXT Event we are setting up to see what the thank you page looks like and confirmation email without having to deal with all this nonsense. Yes we could set the fee to $0 but that voids the ability to be able to truly test the form using our test merchant account with a test credit card. Very frustrating.

A gift was erroneously marked posted to the GL (to a date in the future!) as part of testing a new feature, and it is now locked for deletion and we are additionally unable to adjust necessary fields. Database admins must be trusted to make fiscally-responsible decisions as to when it's appropriate to delete a gift. We sometimes use $0 gifts, so adjusting to zero does not actually solve our problem.

Please trust your users. We have a lot of systems in place to prevent fraud already. We know when it is prudent to delete.

Agree with all the comments below. This is a must-have feature for any system - we need to be able to delete records entered in error. It should be up to the database administrators, not Blackbaud, to determine when it is appropriate to delete a gift. We need the ability to delete a gift no matter how it was entered.

I agree! We had a recurring gift where the card information expired. After catching on and notifying the constituent, they decided not to continue. Now I have a bunch of individual unapproved batches with a $0.00 amount, from the expired card, that are taking up space in the NXT Gift Batch area.

As we are cleaning up data, we need to be able to delete gifts that are entered in error.

Anthony,

We understand the importance of preserving gift history where relational data exists. However, us users should have the ability to decide what to keep and what to remove in cases where deletion is appropriate (e.g., test transactions, incorrect entries, or gifts without associated data).

Since BBMS already tracks the transaction history, these records don’t necessarily need to remain in RE, where they can clutter the database and impact usability. We need the flexibility to delete such gifts ensures cleaner data.

Want to be able to delete. Gifts from our online platform are rarely processed for just one date. It's easy to pull gift made today in batch and then accidentally pull it with gifts made later today in tomorrow's batch. Do not want adjusted gift of $0 on record when it was due to error.

This Idea HAS NOT SHIPPED. A gift entered in web view cannot be deleted in either web view or database view.

We need to be able to delete incorrect entries entered in either mode- the web view is just an 'overlay', so there is no reason why gifts entered there are special. We who have the rights to delete gifts are WELL AWARE when the 'trail for gifts' should be preserved through an adjustment, and when the mistaken gift entry should be deleted.

The ability to delete a gift in web view was released earlier this year. That capability allows for gifts with no transactions associated with them to be deleted. As we move forward with our reconciliation unified view, we need to ensure that the trail for gifts is preserved. There are instances where deletion can occur (non transaction ID, transaction occurred but in test mode, etc) but for those gifts where we have relational data, we want to preserve that history and refunds/adjustments are the advised method. We are evaluating feedback for instances where gifts should be able to be deleted as we move forward.

I thought this ability has already shipped? If it hasn't, it's a no-brainer.

this is causing me A LOT of extra work (and aggravation). Plus it is going to be more work come year end and giving summary time. URGH!!! Why mess with something that was working just fine in database view

When I brought this up with Blackbaud, I was told: "On the whole, Blackbaud suggests that gifts are never deleted in either DB or Webview. Adjusting a gift to $0 allows for better tracking and a reason for why the gift was deleted."

However, we use $0 gifts to mean something else (something that should actually be tracked on a constituent's record). I don't see any reason to track a gift in RE that was entered erroneously and shouldn't exist in the first place. That should be handled outside of the database.

A better solution would be a history of actions performed by users in the system - that way, the incorrect gift wouldn't be attributed to a constituent, but it could be seen that a particular user deleted a gift.