I am happy to announce that support for "sounds like" in RE NXT web view Constituent search shipped today! We weren't sure it would make it out today so we didn't advertise it in the "What's new!" in Help this week, but for those of you subscribed to this idea, I wanted to let you know asap that it is in Production. It will be advertised in the "What's new!" next Tuesday to bring it to everyone's attention.

I did want to point out that this idea in and of itself has some grown over time and extended in scope, which makes it difficult to resolve. I see references in here to many enhancements to search that have in fact been made in NXT web view over time (more than 8 results, larger link targets, search by constituent id, etc). Since this heart of this original idea was focused around what we refer to as "sounds like" support, I'm going to mark this as Shipped. Feel free to search the Idea bank for existing ideas (or add new ones) for other Search improvements that you may have mentioned in the comments of this Idea.

One other thing that I wanted to mention - we are leveraging an industry standard algorithm to support this feature. Unfortunately (and I was surprised by this), that algorithm does not recognize "Catherine" vs "Katherine" as "sounds like" matches. We are looking into this now and seeing if there is anything we can do to enhance it without impacting performance or adding additional risk, but since that specific example was called out by the OP, I just wanted to mention that it is an exception to the general rule of the functionality we have shipped.

I hope everyone finds the new change helpful!

Thanks,

Jarod

We have a development team working on this now and hope to get something released in coming weeks.

In addition to minor misspellings and wild cards, I would like to see "sounds like" and "contains" added.  Two example:  My own name is very commonly misspelled Conners (it's a West Coast habit) and I can't be found when that happens.  Second, in areas with a lot of "untypical" "American" names like names of Asian origin, users can be uncertain on how to exactly enter the name of a constituent.  The database view finds Connors just fine when searching for Conners; would love to see that added to the web view search.

I missed this when I just posted an idea . . . but the use of wild cards (*) and boolean searches in the results (like you can with RE Database view) would be amazing.  For example, if I need to find Catherine Smith in Denver, but I am not sure if she is in RE as Catherine or Kathy, there is no way to find her except by trial and error.  In RE Database, I can;

Last Name = Smith

First Name = *ath

City = Denver

And boom, there she is!  

Would be nice if the search results could be sorted by columns too (although I prefer boolean search features).

Thanks!

Search address info. E.g. "john seattle" will find Johns in Seattle.

I search by email a lot.  I often use a combination of the last name (or part of a last name if I don't remember the exact spelling) and first few characters of an address or the city (I use this when I have a common name).  The other thing I do a lot is use wildcards.  With long company or foundation names I can't always remember the exact name so might do something like *helen*found - I know that the foundation contains the name helen somewhere but I don't know where. 

Can we have the display show more than 8 individuals at a time?  We have a constituent that has the same name as 29 other people and there is no way to pull him up with the current search bar.

Agree that we need more search options in NXT. It would be really helpful to search by street address or email address, as we can do in RE 7. Would also like to be able to search by contact name and have the organization they are associated with pop up. These are essential search functions.

I don't use Enhanced Search in RE:7, but I do often search by Constituent ID or address.  I agree with Ejbaerg's comment on the searchable fields as well as the maximum 8 records returned.  I would be okay with clicking a button next to the search field and opening a search window like RE:7 if that would allow for the more robust search functions of RE:7 to be in RE:NXT.  (I rarely, if ever, use Quick Search in RE:7, preferring to use the full search window, as it normally saves keystrokes).

I also REALLY would like to see the Constituent ID at the top of the record.  It's one of the most vital pieces of information for me, and I love when our staff reference that ID rather than using the whole name (particularly in Jr/Sr cases or common lastnames).  Having the ConstID hidden halfway down a tile severly lessens the likelihood that anyone will reference it at all.

The Constituent ID in the Search Results and in the Work Center list would also be VERY USEFUL for me.

My needs are mostly in the area of additional address/contact info search fields (address lines, city, state, zip, phone, email...and definitely constituent ID).  But, in classic, I do find it helpful that when searching for a married constituent their spouse's record also shows in the results. Also organizations display if you are searching for a constituent, if that constituent is also the organization's contact.  Beyond that, I just don't like having a maximum of 8 results show in NXT.  And, if we're going to get really nitpicky, I feel like you shouldn't have to click on the blue name to access the record, but that you should be able to click anywhere in that constituent's little box in the search results.  It feels counter-intuitive. Go type a search into Google and look at their suggestions as they pop up...you can click anywhere in the white space or on the actual words to select their suggestion. 

Hey Folks, What other scenarios are you finding difficulty getting to the record you're looking for? 

Hi Anthony - For example, very minor misspellings of names will cause for the omnibar to show "no records found" vs. showing the constituent.  For example, if I type Lous Johnson in my omnibar, it shows "no records found" because i forgot the i in Louis, but if i type it into RE: Classic, while the record might not show immediately, once I press enter again the record will populate in the search because it is utilizing Enhanced Search.  Whereas, with NXT it leaves you to just have to troubleshoot the name spelling. 

Thanks! Definitely need more feedback from more folks on scenarios. We hear you loud and clear on the additional fields to search by, but really appreciate the name spelling issue. Please keep adding feedback around your search experience. Thanks!