Please add constituent ID to batch!!! We use it on our mailings- enter id and not have to look up constituent each time. We use ID on every mailing list, practically every if not every query, or any list.

I am a huge supporter of having a column strictly for IDs. It's so much easier and can be a time-saver since you'd be saving on clicks.

We are less reliant on ID than some, but Anthony since you mentioned the constituent box/fly out, the ability to see only "important" data and edit it right there is our time-saver. Since you are changing to tab view I don't know how this will roll out but please consider the functionality which allows users to select/see/edit their key fields (i.e. bio, address, phone/email) without having to click around the record. One example for us is a custom field that tells us if the donor does or does not want acknowledgment letters - seeing this at a glance during data entry tells us whether to put a letter code. Or adding a new email right in batch with little hunting/clicking. Thanks for hearing and considering all the input around speed and efficiency!

During any gift entry, batch or grid, especially as Blackbaud and Add-ins keep creating duplicates, being able to quickly see the ConsID when selecting the individual is key, as the brand new individuals are easily identifiable by the newer ConsID. When we can't see that, even two Mahatma Gandhi options are indistinguishable and we simply have to jump through a lot more hoops picking the right one. Of course duplicates are created in many ways, and also many are similar but not duplicates, but seeing ConsID, especially refencing a remit that has the ConsID, is key. Not sure why there is such pushback.

I agree entirely about the need for this. By extension, any commonly used field that cannot be entered and viewed within the row presents a huge problem for batch entry. For example, we use custom fields extensively and those suffer a similar issue in web view. Aside from speed, seeing all of the data laid out in a grid is foundational to the tool. It’s how we catch errors and omissions as we work. For our team, it’s not that we’re stubbornly clinging to database view out of habit, it’s that the changes made to batch entry in web view run contrary to the work it’s meant to facilitate.

I also agree with Jennie. We need to see the Constituent ID displayed to be sure that we have chosen the correct person when multiple people have the same or similar names.

I also agree with Jennie 100%.

Hey, Anthony....this isn't the thread, but since you're on this and the subject was brought up, I'm wondering if there's a way to "keep" database view for viewing purposes only? Disable everything (no one could add, edit, delete or run reports)?

Just keep steering us in the right direction so this concern withers away.

I agree with Jennie. Please don't get rid of database view!

Please keep database view. It's SOOOOOO much better.

I definitely agree 100% with all the comments. We really need the Constituent ID included, not just the donor's name.

The issue is more so, when there are constituents with the same name, and you run a report, its now impossible to know which line belongs to which constituent, unless this has changed recently.

The issue is not just searching by with an ID. It is also verifying that when constituents have the same first and last name we have chosen the correct one.

Part of the slow down with grid batch entry is the need to search for the person first instead of (like in database), you can enter the ID only and then the constituent with that exact ID is populated without having to narrow down search results. We have a constituent record ID that is literally "1". While it's helpful to have the constituent ID shown at any point of the gift entry, I believe the majority of users would prefer to be able to enter by constituent ID first, the corresponding record name populates, and is then confirmed with the pinned fly out window showing constituent details that the correct person was linked

Having the ConsID in all options that have output is critical!!

We are looking at options to show the ID after the constituent is selected. You are currently able to search based on ID in the new batch and a lot of the comments here seem to at least not be aware of that so I wanted to point that out. There is also comments about the constituent box which we are using the constituent fly out for in web view and we are looking at options to be able to pin that flyout so it stays visible.

Having a separate constituent ID field in grid batch is of critical importance. This is the primary field used in database view for gift batch entry.

The majority of our gifts are received by mail. All our remits include the constituent ID to ensure accurate and faster gift entry. We have multiple constituents with similar names and using their ID number is crucial.

Pls add

Please add constituent box like in database view.