Oh and I need to add this is vital to be able to search for partial email addresses. Email addresses are NOTORIUS for being typed incorrectly. Or worse, when it is handwritten on a donor card or info sheet and you can't tell if that is a 1 or an L or if they mean O or 0. DBV has the ability for me to type the part of an email and use the * to wildcard it out and find if that email is even close to anything we have. It has saved me several times from adding a duplicate constituent.

This is desperately needed for DB managers. We are the ones tasked with keeping the information relevant and accurate for the fundraisers who are the primary beneficiary of the NXT setup. I use the wildcard function all the time, especially as a Core user. When information is updated without review, it results in errors that sometimes only a wildcard search will help find and fix. If I have 8 John Smith's and I know is address his 123 Main Street, it's helpful if I can search his last name and 123 M* to find the one I need when the street name was added as 123 Mian St. Yes, I have issues like this fairly frequently.

A scenario we keep running into is that NXT search in the events module doesn't return folks if you haven't included their middle initial in your search, but with no wildcard, you then have to search by just first or last name. Easy with very unique names, but once you get to names like Robert, Ryan, Lee, or James that are common in both first and last name slots, it can be harder with larger invite lists.

It seems Blackbaud has chosen the "&" instead of the "*" as a wildcard. This is incredibly frustrating, not least because it then confuses any records that have an & in the title. There is a VERY good reason why the * is the standardized wildcard in searches. Blackbaud needs to correct this ASAP.

I am staggered that this post goes back to 2017 and that the search options are still so limited on RENXT Web view.

As I look at the comments below, the first comment came from Jarod Bonino (who I assume works for Blackbaud) in 2017. It is now 2025 and the search function in web view is still much more limited than in database view. When cam we expect to have all of the search capabilities for searching a constituent in web view as we do in database view?

Being able to search for supporters by UK postcode is a key requirement across the charity. So the sooner this option is available in NXT web view (as it is in database view) the better! Is there a planned date for this ?

This was a whole team discussion this morning - took six gift officers away from critical work to discuss how they couldn't find records in NXT because they didn't have exact spelling of a name to locate the correct record and could not use a wildcard like they could in the old days of database. M and M vs M & M or Hanson vs Hansen

I agree this is super important. I frequently need to search by city, zipcode and other fields when trying to locate a specific donor.

we have 500,000 records so searching for Smith seems to be a problem. How is this issue lingering since 2017. This is DB 101! who can we tag ?

This was originally posted in 2017!! what?!

WHEN is this planned for?

yes - multiple fields allowing wildcards! Haven't migrated yet, but we have 500,000 records - sifting through all the Smiths will be fun! Any tips?

In Canada, we use Postal Code as one or our main searches for Constituent records. This is very helpful especially if there are common names.

Many more search options are needed in web view before we can solely rely on it. We need a way to filter constituent searches by many possible fields on the record, in case we aren't sure of name spelling.

We need advanced search options like that in database view. It is so cumbersome to have to search in DB view to get the correct matching record in NXT all because we do not possess advanced search options.

How many votes and comments are required for R&D to make necessary enhancements?

This idea is almost 6 years old now? That is crazy to me. If Blackbaud wants to get rid of Database view, you have to let us be able to search for other fields besides just the name. Sometimes I only have an email address to work with or last name and city, etc. We're not always going to have a complete name and need to be able to search for other fields.

Our fundraisers are constantly dealing with difficulties in searching for organizations in our database with common names like "Trinity" or "First." The search feature won't even load all of the Trinity Lutherans in our database, and there's so many results that the 'find in this list' bar just pulls blank results for over half of the results. Our staff in web view shouldn't have to make a constituent list just to look up a record. At minimum, please add the ability to use constituent filters on search results, but it's reasonable to expect multiple parameters and wildcard options.

What happened to the search enhancements Jarod mentioned 3 1/2 years ago? Not having a wildcard function makes NXT useless for many purposes.

Search by email would also be great.

Any update on this?  We really need some kind of advanced search or smart search option.  Our organization serves one of the Presbyterian denominations.  There are over 2400 "First Presbyterian Church" constituents in our database.  Finding them is no fun in the web view.