The fact that the first name is not visible AT ALL on the main constituent screen is bonkers!

In the search results, please show the full name, nickname and aliases - not just the nickname. Thank you!

The most basic function of a database is to be able to search for a constituent. RE NXT makes this very difficult, the search functionality in DBV works for ALL. Just gives us that back, please.

Can we get an ETA on when this will be available? We really need the ability to search by city/state. It's hard getting staff to look stuff up in the web view because it's difficult and time consuming to locate records.

Adding to comments: It is not acceptable that voting is still "open" on this necessary function. This should always have been a priority for Blackbaud and not an afterthought. If any of the vital database functions are difficult to implement in webview, that is the fault of Blackbaud in choosing the platform to migrate to, and should never be viewed as an obstacle for the client to adjust to. Especially as our fees have never gone down, they have only gone up. Blackbaud's failure to take into account the base needs of its users is mindboggling.

When is this happening? Why is this still open for voting? It's essential!!!! This should have been one of the first features implements!

I love being able to set a return for my searches through query. This speeds our data entry in batch when we are looking to soft credit the long list of those who are Benevity or United Way donors. It is also helpful when we are working with event data to have birthdates in the search results to help us identify if this is a new person or not without opening the record.

Please, please include searching on the Alias fields. We have spent years putting in multiple naming conventions and now the system creates new records for constituents that are already in the system. And, I have had to spend a lot of time searching and linking records. For instance, on an event form, someone signs up with a name of Her Justice, the system doesn't recognize that name because the name is Her Justice, Inc. The name with "Inc." is saved in the Alias field, but the system isn't programmed to recognize that. It's the same with individuals with two last names or people with nicknames. We cannot control which name a user will use. I need the system to recognize them no matter which name they use as long as it's accounted for in the Alias. This is why we spent years putting alternative names into the Alias field. Now, it's all useless and labor intensive.

In addition to the above, the ability to filter by Fundraiser once you expand into the list of search results would be very helpful in the cases where you don't have exact information to find the person by constituent ID or email/address, and need to expand and go to the constituent list to narrow it down.

Also add the ability to search by MEMBERSHIP ID

Add Constituent Codes to the search results PLEASE!!!!!

Yes! It would be most helpful to be able to do "Wildcard" searches with partial information.

There are a lot of comments, so maybe someone has already recommended this. However, it would also be helpful to add columns to the search results grid. We are a school and often have students that share a name with a parent or grandparent. In DB view I created a search query so I could specifically add and view the constituency of the results returned. That has helped me to distinguish between a parent and a student. The search grid doesn't allow the addition of other columns, which mans having to open each record to find the one that is correct.

When is this going to happen?!!?!? It's essential! It's crazy that we can't quickly and easily search for someone in our database by an email address or a zip code!!

Our largest fundraising initiative relies on hand-written cards that are passed out to prospective donors. The ability to search by partial info is completely necessary for us. If we can only determine partial phone and partial address with a name of "John Smith", being able to search by even partial match, greatly minimizes the number of search results that we have to go through to make a determinization.

The ability to search with multiple fields (Last Name and City) would help pare down the list of potential matches.

Yes, yes, yes. Don't know why we need to lose functions in this 'upgrade' to web view. While there are great strides forward for gift officers, still so many issues for dba.

I would like the ability to search on partial email addresses and other specific partial information as we can do in DBV. This is helpful so we don't receive results from the ID field when inputting a street number. Another example is looking for constituents with the same email domain to link relationships to an organization.

I would also like to see Class of on this list of expanded search options.

We rely heavily on Constituent ID and some of our Constituent IDs are only 3-4 numeric characters long, so result in large numbers of possible matches. Also, these tend to be our most important records as they have been in the system the longest and so are of an age to be major prospects. An 'Exact Match' option would be helpful.