Plus, I HATE having to type in the CFAP in web-view gift entry fields. Give me a drop down so I don't have to memorize or look up sponsorship level names (for example)

!

Absolutely! Every time I try to use it because DBV is going away I switch right back because it takes so much longer in WebView!

100% agreed & concur with Erin's comment: This. The amount of time wasted on some of these tasks in webview is astounding.

Effective data entry user interface on the web is essential to productivity in Raiser's Edge NXT and for your customres. Things as simple as not including marital status on the initial record and making us save a record and choose "constituent summary" and "personal info" to enter this information is not good UI. Also, Salutations are difficult to manage in webview and have to similarly be added. It is also very easy to click cancel at the bottom of the screen and delete all the work you've entered when entering constituents online. I am happy to give more feedback on this issue as well. Thanks again for all the consideration and feedback.

This. The amount of time wasted on some of these tasks in webview is astounding.

Agree whole-heartedly with these suggestions. The frustration level has been increasing at a steady rate as we have been trying to transition from database batch entry to webview batch entry. Unfortunately, we have run into major stumbling blocks, particularly, trying to apply payments made by personal checks to recurring gift records so the payments will appear as recurring gift pay-cash; updating that information on each donor's record after a batch is approved is much too time consuming. I don't envy the engineers trying to work out all these issues, but I certainly hope they take note of customer concerns before setting the final timeline for eliminating the use of database.

This will be the reason that you can pry database view from my cold dead hands. I get that there are complications with shortcuts in a web-based application, but those of us who have been using the program for years and years, have keyboard shortcuts down and can navigate almost all of database view without a mouse at all (except for some annoying non-keyboard navigable things like exporting a previewed report). I'm about 500% faster in database view, especially when performing repetitive tasks.

Totally agree that the timing of turning off query in database view needs to be revisited. Blackbaud is putting in a lot of work into NXT and things are on their way, but many essential features and functionality still missing. This item (note the number of votes) is a prime example.

Editing data from a query in webview has too many clicks to get to what one needs to update (true even when just trying to edit something on a record). This is one of those things where I feel like BB isn’t helping to us work smarter. I can use a query in dbview and click on each record and update what I need to sooooo much quicker and easier than I can with using the same query to make same updates in webview.
And not all the fields are in webview. I currently need to update some funds on some fund relationships. Fund relationships are NOT in webview at the moment. If dbview query goes away before they are in webview then I can’t even update what I need to. It’s bad enough that there isn't any way to mass update fund relationships even in dbview…..
Blackbaud, please reconsider the timing of turning off of database view query.

Please also vote for https://renxt.ideas.aha.io/ideas/RENXT-I-8185, which goes into the comment below in more detail.

(Note to Blackbaud - Please do NOT merge these ideas. They touch on similar topics, but they are not the same.)

I’d like to elaborate on the "Timing Note." Users who perform data entry and clean-up typically rely on queries to efficiently work through groups of records, rather than searching for each record individually—a slower approach that also increases the risk of repetitive stress injuries. If queries are disabled in Database View before all necessary fields are editable in web view, it will create workflow challenges and place additional strain on already overextended and under supported staff, such as database managers and data entry specialists.

yes, 100%. I absolutely loathe webview and avoid it for the majority of my work. I generally only use it to add Actions and attachments. Everything else is done in DB view - Batching in DB takes 1/4 of the time it does in NXT!

Could not agree more. The lack of navigation other than tab and shift + tab in journal entry view is one of the worst UI decisions I think I've ever dealt with in a software.

working in the database all day, I depend on keyboard navigation and shortcuts. Exclusive mouse work is inefficient and leads to RSI, carpal tunnel etc., as well as significantly slowing down the work. This UI has not been created with 50% of the users in mind. Please reconsider who your audience is

Thank you, Sunshine! This is well-stated.

Also vote for this idea in a similar vein: https://renxt.ideas.aha.io/ideas/RENXT-I-7942

Agree. Using webview will totally crush my input time. Way too much scrolling and clicking.

The tiles-based UI ends up being very cumbersome for the tasks described in the idea. Even after rearranging the tiles, viewing a piece of information like a gift on a record or a relationship takes many clicks and a lot of scrolling where in database view it would take 2-3 clicks.

This is a GREAT idea. It takes so long to do any updates in web view, I direct any update staff to do it in database view.
Even a constituent code update requires clicking a certain box to edit, then clicking the pencil next to the code to edit, and then deleting or editing, rather than just navigating to the constituent codes and updating. I used to hear a lot about "too many clicks," but NXT has way more clicks and unintuitive locations for demographic updates.
While the system looks good for front line team - I like the idea of a back end staff streamlined view - we want our batches to be rapid. We want data entry to be quick and seamless.

Absolutely agree! The UI for gift batch entry in NXT, assuming it will be similar to the UI of all other NXT functions, is *not* designed for the actual user who spends their days doing high volume data entry. Doing data entry in fields/pages that look like current NXT pages will be frustrating and time consuming. Please, please consider this suggested feature and the comments below that are coming from lived experience of people who do this work. THANK YOU!