Client Search not working as expected
complete
Kristina Nickel
The Client Search is really different than in our current production version (4.0.59.4). Is it working the way you expect it to? For example, to get to my client John William Test (Alias 1 Jonathan Silly Pants), it no longer works to search jo te or wi pa. john test doesn't work either, you have to type in test, john. But jonathan silly works. Is that by design? Absurdly, han sil works.
Ali Ryder
We have learned that this issue is a side-effect. "The reason the original change was due to performance issues for large databases...the existing search function was inadequate." So this issue now exists because they were trying to fix the search function being really slow for large communities.
Ali Ryder
complete
Confirmed fixed in 4.0.60.3
Ali Ryder
Ryan: I just tested client search in our HIFIS 4.0.60.2.1 install and itâs not behaving as expected. For example, searching for âJohn Doeâ in HIFIS 4.0.59.7.1 returned 5 results. The same search in HIFIS 4.0.60.2.1 did not return any results.
Digging into this further, HIFIS 4.0.60.2.1 no longer uses the full text search CONTAINSTABLE function that was used in HIFIS 4.0.59.7.1. Instead, it uses the LIKE operator.
MetaDataSearch LIKE '%John Doe%'
Looking at our HIFIS data, there isnât any consistency in the way client names are recorded in the MetaDataSearch field; some use the Lastname Firstname format (Doe John), some use the Firstname Lastname format (John Doe).
A search for âJohn Doeâ in HIFIS 4.0.60.2.1 will only return results when the MetaDataSearch field also contains the text âJohn Doeâ. In our case, the MetaDataSearch field for all John Does in the HIFIS database contained the text âDoe Johnâ and no matches were found.
Ali Ryder
We have learned that this issue is a side-effect. "The reason the original change was due to performance issues for large databases...the existing search function was inadequate." So this issue now exists because they were trying to fix the search function being really slow for large communities.
Ali Ryder
Merged in a post:
Clients Not Appearing when Searching (Using different formats)
Peter Nguyen
When searching for clients in our current HIFIS build,(4.0.59.6.5), we are able to find the client regardless of how we input their name or their Client ID in the search bar (FirstName LastName, or LastName FirstName, or FirstName, or LastName). In 4.0.60.2.1 there are issues finding a client depending on how you search for the client. An example is my client's name is Ben Parker (FirstName LastName). When searching for this client in 4.0.60.2.1, the following will work:
- Parker Ben
- Parker
- Ben
But this will not work:
- Ben Parker
EDIT: This post is directly related with Brenna's update regarding how to search for clients, and it mentioned that we sent in a ticket. I just forgot to post this on the website.
Ali Ryder
Brenna: "Update on the Client Search in the newest bug fix - You can't search FirstName LastName but you can search LastName FirstName or FirstName or LastName. (we've sent in a ticket)"
Kat LeBlanc
Ali Ryder I'm curious if there is any movement on this ticket?!
Ali Ryder
Kat LeBlanc We're not going to see a maintenance patch, if that's what you're asking. Hopefully it'll be addressed in 60.3