KN
Kristina Nickel
about 2 years ago
Fixed
Client Search not working as expected
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.
⚙️System
4.0.60.2
🚨Major
😕Incorrect Behaviour
Copyright © 2026 ACRE Consulting
___MESSAGE___
___MESSAGE___
Confirmed fixed in 4.0.60.3
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.
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.
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)"