How are you preparing for batch gift entry in unified view?

Kellie Dentler · January 13

If you are still batching gifts in DBV, what steps are you taking to prepare for the transition? I am at a loss as to where to start, especially since some features we need aren't yet ready in UV (like Batch Control Report).

The only preparation we have made is to start using an NXT form for pledges, and for credit card pledges (we use Luminate for online giving.) It's helpful to get used to navigation but not for much more in the way of prep for grid batch gift entry.

What's your plan? Thanks so much.

Crystal Bruce · January 13

Tagging in a few All-Star experts @Sunshine Reinken Watson and @Carlene Johnson !

Alex Wong · January 14

For us, there isn't any "preparation" as we do not have access to the upcoming upgrade to webview gift batching that was demo-ed previously.

We do not use RE NXT donation form right now, but is using JustGiving Integration and RE NXT Event Registration form, so those get in the RE NXT webview gift batch.

the specific on the processing of these integrated webview gift batch is simple for the finance team, as they just need to approve the gift batch. All editing that is needed is done via SKY API with custom code that will automatically update the gifts created using our org's gift entry policy.

Madeleine Holdsworth · January 14

In yesterday's webinar, "InsideTrack to the Unified View" (the new monthly webinar), the product development team said that Batch Control Report will be in unified view.

Aldera Chisholm · January 14

@Kellie Dentler You don't need to do anything at all, in terms of preparation, other than perhaps watch the demo from the Inside Track and prepare to do any internal training for your team once it goes live.

Keep in mind that web view batch entry going live does not mean database view batch entry is turned off. You will have time to look at both and compare them side by side. Web View batch entry will continue to be updated and developed too, as more features are brought into web view.

For general prep for web view overall, you're doing the right thing by moving forms, I just recommend working in NXT as much as possible to become comfortable, knowing that for now there will be some things you have to do in Database View.

Ange Scott · January 14

nothing at this point - as others have said, we don't have access to the pending changes for testing. Though outside of using Actions & attachments in NXT, I still do everything in DBV. It's easier, clearer and MUCH faster and more efficient for what we need.

I'm really not a fan of NXT and am not looking forward to having to use it for everything, it's just too slow, too many clicks and dropdowns…

Dariel Dixon · January 14

While it's been stated that there's not much that can be done as we don't have access to it yet, there are a couple of things that can be done. Here's a simple list of thoughts in no particular order.

Set expectations. I think that this is the most important thing. Make sure all the decision makers know a change is coming soon, and that we may not be able to create the same level of reporting. This should not be a decision that you have to make by yourself.
Consider an alternate report, or something in the interim to fill in the gap. Find out what the business office and the other stakeholders need to see and try to find another report (or combination of reports) that may suffice.
Be patient. A lot of users have this same concern, and I'm sure one of these brilliant minds will find a solution in time.

I'm not sure how it will work, but we'll see soon enough. Good luck!

Carlene Johnson · January 15

One thing I’d suggest is reviewing any recurring gifts that are still being processed through Database View. If you have any left in DBV, it’s worth converting those to Web View. The WV recurring engine is automatic, reliable, and a great early win for getting teams comfortable with Web View and the online constituent‑matching workflow.

For online recurring giving, it’s also helpful to look at your forms. Any recurring options that aren’t already using Blackbaud Online Giving Optimized or Standard Forms are good candidates for conversion. Since you’re using Luminate, even converting one form as a pilot can give you a clear comparison of donor experience, data flow, and recurring management. And having a form or two in place now also gives your team a chance to get familiar with Online Data Review, which becomes increasingly important as more activity moves into Web View.

If your team relies on the Batch Commit Control Report, you can run the Batch Validation Report in Database View for now. The Control Report is coming to Unified View, but the Validation Report can bridge the gap until it arrives.

Beyond that, there really isn’t much to “prepare.” At this stage it’s mostly about getting more comfortable with the Web View UX—navigation, search, constituent matching, and the general feel of working in NXT. I’d hold off on changing your check‑entry workflow until Grid Batch officially rolls out. Once it’s live, you’ll have time to compare DBV and WV side by side and decide when it makes sense to transition.

Aldera Chisholm · January 15

Great point about the Recurring Gifts! I should have thought of that. :)

How are you preparing for batch gift entry in unified view?

Answers

Categories