Thank you for introducing Smart Services. I looked into it, and it seems well-suited for handling requirements like searching nicknames, abbreviations, and fuzzy matches. However, I noticed that it only supports record types, which we are not currently using.
Our design involves making API calls through the integration layer, manipulating the data in ER, and then mapping it to the interface. Given this architecture, how would you recommend implementing Smart Search within our setup?
No built-in function dedicated exclusively to fuzzy matching Plugin Provides the levenshtein() for edit-based similarity. Use soundex() for phonetic matches. Use regex for pattern-based partial matching (regexmatch()). You can useincludesoperator for record field search.
If you could help more what exactly you are looking for with example could help better.
Thank you, Shubham — that was helpful. I'm looking to capture variations in search terms, such as matching 'Street' when someone searches for 'St', 'Drive' for 'Dr', or 'Junior' for 'Jr'. Additionally, I want to account for nicknames, like matching 'Benedict' when searching for 'Ben', or 'Meghan' when searching for 'Maggy'. However, I want to ensure that we avoid capturing unrelated or incorrect matches that simply follow similar patterns, so we maintain accuracy and avoid false positives.