Add Advanced Search Functionality in Webview (Similar to Database View)

It would be extremely beneficial to enhance the search functionality in Webview by adding an "Advanced Search" option, similar to what’s available in the Database View.

Currently, the Webview search is quite limited and often returns partial or overly broad results. For example, when searching by Constituent ID, the results may include any record where those digits appear in other fields, such as Alias or other IDs — with no way to filter for exact matches.

Suggested enhancements include:

  • An "Advanced Search" panel in Webview

  • The ability to search by key fields such as:

    • Constituent ID (with exact match checkbox)

    • First Name

    • Last Name

    • Address

    • City

    • Postal Code

    • Email

    • Phone Number

  • Inclusion of checkboxes or filters to refine search (e.g., "Exact Match", "Starts With", "Contains")

  • Optional ability to combine criteria for more targeted searches

Why this matters:

  • Improves efficiency when searching for constituents in large databases

  • Reduces frustration caused by unrelated or partial search results

  • Aligns Webview functionality with the more robust features in the Database View

  • Supports data quality, clean-up, and user experience for teams across fundraising, data management, and support

This would be a valuable improvement for organizations transitioning more of their work to Webview and trying to streamline workflows.

Thank you for considering this enhancement!

  • Cherrielyn Eugenio
  • Sep 18 2025
  • Reviewed: Voting Open
  • Attach files
  • Jaclyn Whitelock commented
    December 17, 2025 21:00

    There are many people that I would easily be able to find in DB view with wildcards and partial info that I can't in webview.

    If functionality isn't improved in webview, this will be a significant add to my workload where I would have to go in and query for what is very simplistic information, that shouldn't need a query.

  • Hedy Emery commented
    November 19, 2025 11:22

    Searching in NXT rarely pulls through records. Searching in Database view is still having to take place so we can be more accurate. It is vital that we can search by the same categories, and not just a generic search that only works on names, occasionally email.

  • Tracy Hernandez commented
    November 18, 2025 04:12

    I voted on this a while ago, because it made sense, but honestly I ended up so frustrated trying to search in web view - I often search on address, or parts of an address ...

  • Guest commented
    November 12, 2025 15:41

    I wish I could search based on email or phone number in webview. I also find it hard to search for an alias in NXT. It doesn't seem to search preferred name either, only First/Last Name.

  • Paul Stewart commented
    November 10, 2025 15:49

    This is so, so needed.

  • Rachel Cavalier commented
    November 10, 2025 13:07

    Web view search often really struggles with first lines of address that are flats or apartments (along with other addresses that start with anything other than house number and road name) - if I could search by postcode this would be incredible!

  • Sunshine Reinken Watson commented
    October 30, 2025 18:00

    This is very needed!

  • Rebecca Altes commented
    October 24, 2025 13:53

    This is VITAL! I regularly turn off "enhanced" search, but use "advanced" search all the time, with all of what Cherrielyn said, and wildcard symbols. This is absolutely necessary for functionality.

  • Rachel Griffin commented
    October 21, 2025 18:34

    I completely agree. I've been primarily using DBV, but I've been back in NXT this past week, trying to get myself comfortable with working with the changes. DBV is going away, so I need to be able to work in NXT, right? Well, it's been frustrating trying to find the right record. We have many people with similar names, and I'm slowed down or even 'duped' because I think I'm in the correct record, but I found out I'm not. This feature is so so so so so necessary

  • Karis Morrow commented
    October 15, 2025 14:22

    Sometimes the only way I can find the correct constituent is through the address, email, or phone #. Even if it slows down the results a little bit, it will still be faster than having to create a query to find the constituent in question.

  • Karen Diener commented
    October 13, 2025 12:29

    This definitely can make searching for constituents more time-consuming. Webview is slow enough already - please do not make it slower!

  • Kelsey Greaves commented
    October 02, 2025 16:40

    I completely agree! The advanced search function is also helpful when we are trying to identify a graduate. I use the Class of search in combination with First Name/email address on a regular basis.
    The fundraisers I work with have also been requesting more robust search functions in web view, so this isn't limited to data entry personnel!

  • Maya Rosman commented
    September 19, 2025 20:41

    Yes. This is one of the biggest tools we have in database view to reduce duplicates. The current webview search only allows you to search on one field at a time. I often need to search several fields in conjunction with them to find some records. For instance, when I'm trying to find an employee with an extremely common name (say Matthew Smith), I often use advanced search to search for Last: Smith; First: Matt; Email *@waketech.edu (all employee emails end this way). I need a way to tell the system to search in this robust way to quickly get to the record I need.

    Often there are records that folks who only use webview (our gift officers) cannot find with the search available to them that I am able to find with database view's advanced search. Losing this capability once we're in the Unified View without access to database view will result in a ton more duplicates, and will rob us of a robust tool for finding exactly the records we need.

    Please consider adding this and enabling wildcard search within it so we can continue to avoid duplicates and find the records we need.

  • Maya Stiles commented
    September 19, 2025 20:28

    I agree! Please also include the " " and * search options currently in database view in NXT. For instance, when searching for a fund with fund ID 10379, I should be able to search for 103* in NXT and get all funds whose fund IDs start with 103, rather than all funds who have 103 anywhere in their fund ID (rather than just at the beginning).

  • +181