Batch in NXT needs to be as robust as DB view!!!
The Batch feature in DB view is formatted to help SPEED up & SIMPLIFY multiple gift entry & for organizations with hundreds of gifts a month to enter, this is essential.
Gift Data Entry as is currently available in Batch for NXT is equivalent to entering gifts within individual records & then showing them in a list off to the side. This is not actually helpful & feels more like window-dressing. Anyone who has ever been tasked with a large amount of data entry for their organization [Gifts or Constituents] would agree.
The DB options allow for
-
creating Templates
Essential! Especially when you are asking someone to do data entry who is not fully trained in RE... which a lot of people who "help out" with big data entry tasks during peak points of the year are not.
Selecting relevant Columns
Hiding Columns to speed up data entry
adding Defaults to speed up data entry
the ability to select constituent fields [per org policies & procedures] for easily entering a New Constituent entry along the way - without opening the record itself.
-
the ability to create Constituent Batches! Hugely helpful for schools for example, who are tasked with adding newly enrolled students & their families each year.
if a school cannot afford the complete BB suite of software, this is a gaping hole in NXT's batch capabilities
PLEASE ensure NXT is equal to DB in Batch before we lose the DB view option altogether!
-
Tracy LeClair
- Apr 9 2025
I agree! Two other key features:
The ability to globally add/update a value for a column (like appeal or fund).
Bulk adding constituents to a gift batch via query
I agree. I did a test batch in NXT and although it was usable it was not up to standard. I do large batched and being able to add defaults and use templates is very important. I also need to see the whole batch on screen. Also, during peak seasons I have less experienced staff help and batch entry in NXT is not as user friendly for those staff. We need the control report and a fund report when the batch is committed and that is not really available in NXT.
If it hasn't been done already, I'd honestly, non-sarcastically suggest all development staff take a "Data Entry Appreciation Day" with fun activities like "import this inconsistently formatted data from a PDF scan!", "Please add this custom field to these 75 names. No, I didn't get the addresses or constituent IDs, just names." "add this stack of 250 handwritten newsletter signup forms!", "enter 150 paper checks as gift records, 50 of which are irregular or require data updates!", "Fundraiser Bob sent in a word doc with his action notes for the last 6 months - can you add them to the database? No, I don't know why it's formatted that way." (Bonus points too if you can get someone over the age of 90 who writes in really non-distinct cursive handwriting for at least half the handwritten documents too so it basically looks like "C|^~--~|^ ^. H~~~.")
Run through a bunch of data entry tasks one day with web view tools, and another day with database view tools. I think it would help web view UI and UX design decisions be user oriented.
Currently, NXT batch is UNUSABLE!!! We cannot use it at all. So I would upvote this a million times if I could!
Agree. I HATE NXT batching and refuse to use it, it's a nightmare and takes so much longer to do. It's useless without giving a Control Report which we use to match the bank statement, it's useless in that you can't see the lines that you've already entered, it's useless given that it doesn't allow an option for Consitituent Code to be added as a column.
And I HATE how you can't delete records entered into NXT that may have been put on the wrong account, how pointless!