We definitely need this. We often search by address rather than name because we have many families with multiple people who have the same name.

Absolutely critical, especially for larger organizations with the possibility of several people with the same name, for male-centric organizations like Rachel's boys' high school, and for those organizations that have many churches as constituents.

Can't believe it's still an issue to build these features into a search function. Not being able to search for different database objects other than constituents is frustrating, especially when I have gift IDs ready to go.

A great example of why this is so important. I worked for an all-boys school where as many as 4-5 generations have the same name! But if I knew the alumni year, I could drop that in the advanced search and quickly find the right person instead of clicking in and out of 5 people (sometimes multiple times in confusion) trying to find the right one. This is my biggest pain point with doing searches in NXT. People with similar names, and having to manually check each one until I find the right one because there isn't an advanced search function.

Yes!!!!! We desperately need this. Our org serves the Presbyterian denomination, including all of its churches. That means we have thousands upon thousands of records with the same name, such as "First Presbyterian Church." We need to be able to search by city/state. Not to mention, this would be helpful with individuals as well when looking for a common name such as a "Robert Smith." It would be much better to search for the Robert Smith in a specific location instead of having to skim through a lengthy list of constituents looking for the correct person.

Adding my voice to the absolute need for advance search in WV and the ability to use wildcards. All the reasons others have already eloquently enumerated. The more one is required to type out, the more chance for a typo which will return no results (happens to me and my colleagues all the time) or conversely the name/address in RE may be misspelled and the more characters have been entered to search for it, the more chance to not find the record.

piggybacking to add - please make the unique ID of everything searchable. If I've exported a list for cleaning, presentation, or verification, it adds a lot of drag to click into a constituent record and scroll and click to get the one gift I need to see - especially for soft credited gifts.

I came here to find this idea, because of all the reasons below (especially Tracy Hernandez and Maya Rosman). Please understand the need for efficiency in our jobs - we are in the system all day doing our work and need this functionality!

I was recently told that webview searches do include more than just name, but I definitely am not finding that to be the case. It would be so helpful to be able to search by preferred name, email, zip, etc!

For those with Alumni/Education, DBV search includes Class Of which we often use with common names or in cases of a name change, searching first name and class. We also use the address search fields to help narrow results. Seconding the need for wild cards!

Applying a query to constituent searches to narrow results customize the results output is an important piece of the robust searching capability in DBV. Please also vote for this idea: Apply query to constituent search in webview

I agree. I think the base search functionality on WebView is much more helpful than on database view but it's important to further filter out records especially for common names.

Definitely agree a power search in webview would be great. It would also be wonderful for it to search gift records. In so many instances I have to create queries when I think a search should be available. For example, searching a check # or transaction ID.

I use this all the time - especially regarding being able to search by email address - it helps find associated records

This is essential for handling duplicate records. I find it so much easier to search for constituents in the database rather than in web view because of all the options available. AI is not the solution for this.

This is essential! AI is not the answer for everything. Searching using more than one field is key especially when searching for a constituent with a common name OR we may need to search on the email field if we have an email address but not a full name of the constituent. Having to run a query to locate these records is not efficient.

I also second Sunshine's examples in her post of Jan 7, 2026.

This is absolutely essential for handling dupes and spouses. Database view Deduping tool could find unconnected spouses, but the webview version cannot. Advanced search fields help me find them as they come up. Please!

Advanced search is a core functionality, and needs to be treated as such.

And to reiterate others' comments, AI is a non-starter as a solution for this vital need.

Need - AI is not a viable alternative - Maya Rosman has got it exactly right in post below!

This is essential! I use the search by email address often to search for all constituents with the same email address on their records, including non-primary email addresses, to check for duplicate emails.

Also, orgs names can change, so to be able to search via aliases/past names, is very important in avoiding duplicates.