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.

Yes. its offered in BBCRM, so not sure why it wouldn't be moved from DB view to webview

This absolutely is needed. Constituent ID vs Addresses vs other items with a possible number in the name. Some form of exact match versus contains, and the ability to filter the search by deceased yes/no, no valid address yes/no, inactive yes/no, and honor/memorial is key for gift entry and regulsr database administration.

Adding my comment - as using constituent lists take so long. And it doesn't give you immediate results if you add a filter - such as city - you have to wait for the system to update. Or it doesn't seem to work at all! We need the search function like DB View!

I agree with the comments entered by Maya in her post on Jan 9. I also rely on the additional checkboxes at the bottom of the search field in database view (display inactive constituents, check aliases, check contact name, check nickname. etc.). I basically have every box in that area checked EXCEPT for exact match only. Once checked the first time, these additional search criteria boxes remained checked and are applied automatically with every search I run in database view. I don't have to recheck the boxes with every search I run.

Unfortunately, when searching for a constituent in NXT, if you want it also to search relationship records (including spouses), you have to specifically manually select the "search relationship records" button EVERY TIME...just another wasted keystroke that shouldn't be necessary. At a bare minimum, NXT should automatically search relationship records without having to be prompted to do so.

Along that same vein, when matching gifts to constituent records in NXT, searching for a constituent offers 3 checkbox options from which to choose. Again, when any or all of those options are selected, the system doesn't retain the additional search option(s) selected for any future searches. You must choose any or all of the options every time you run a search...once again requiring additional keystrokes with every search instead of offering a very robust advanced search of those additional search fields automatically every time anyone runs a search without having to prompt the system to do so with every search.

Finally, I vehemently oppose the use of AI chat in NXT as a replacement for the advanced search capabilities we have in the database view. I can tell you that using the AI chatbot to try to find out whether NXT has or will have any type of hotkeys available for keystroke shortcuts (the asterisk is my best friend in searches and the f3 key for inserting the current date into date fields), and it had no clue what I was talking about. I had to force it to connect me with a live person, who sent me 2 articles. One said that there wouldn't be any hotkeys because NXT is web based and the database is an app which allowed it to create/establish the shortcuts within the app. The second article was a link to this idea box that has allowed me to weigh in and vote on this particular issue.

Also class year!!!!

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.