In search for constituent, use wildcard (*) as option along with search for address, city, and boolean options in results

In the database search, can use multiple parameters to find constituents, including address, city, state and wildcard (*) options.  

For example, you need to find Catherine (or is it is it Kathy) Smith in Denver.  In database view, easy to find:

First Name = *ath  

Last Name = Smith

City=Denver

 

And you can find here . . . that is not an option in NXT so you have to scroll through the list results and hope you find her, the list results are not sortable either . .. which would be nice.

  • Brian Bates
  • Feb 2 2017
  • Planned
  • Attach files
  • Amelia Ketzle commented
    05 Nov 17:49

    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.

  • Guest commented
    29 Aug 16:26

    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?

  • Amy Levitre commented
    December 11, 2023 16:11

    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.

  • Christopher Horn commented
    November 02, 2023 14:49

    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.

  • Steven Peno commented
    September 02, 2020 14:11

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

  • Barbara Martell commented
    August 11, 2020 18:07

    Search by email would also be great.

  • Devan Caton commented
    December 12, 2019 14:35

    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.

  • Rachel Cavalier commented
    May 17, 2019 16:25

    Searching by postcode in NXT would be AMAZING

  • Nilsen Septon commented
    March 12, 2019 19:46

    If you are wanting a more broad acceptance to NXT, then enhancing the search functionality is the best way to go.  I have a hard time telling my users that 'hey - you can do this and that...', but they say...'but I have to find them first.....................'.  This request has already been sitting here for two(2) years - is there any kind of update on this?

  • Guest commented
    September 06, 2018 13:58

    I am having the same problem.  If I search Walmart, but it is entered into the system as Wal-Mart, nothing shows up when I search.  Having those multiple parameters would go a long way to saving my fundraisers adding a duplicate record when one already exists.

  • Guest commented
    March 27, 2018 13:54

    Jarod Bonino - is this stlil planned? We have so many congregations and congregation groups in our database - searching by zip is the only way to narrow them down

  • Lucille Poludniak commented
    March 07, 2017 18:28

    In addition, allow for other typical search options such as " " to search for specific groupings of words or numbers so if we are searching by Constituent ID, we can locate the exact one faster. This is especially helpful since searching for Constituent ID 35 now results in any ID containing the number 35 rather than the exact  ID of "35"

  • Jarod Bonino commented
    February 22, 2017 16:48

    Hey Brian! Great suggestions! We are planning somewhat of an overhaul to our search functionality later this year and each of these suggestions are planned in the enhancement. I don't have a timeline yet for when it will be released, but stay tuned to this idea and I'll try to keep it updated as we progress.

  • +408