We’re currently building an Answers experience for Financial Professionals, and are running into a strange issue for certain search queries that we’re looking to resolve. Specific search terms such as “Aaron” are triggering the NLP filter for builtin.location, rather than name, even though both are configured as NLP searchable fields. We looked in the API response, and it seems that “aaron” is a city in GA, which is causing the distance filter to be applied, even though there are many advisors in the account with the first name “aaron”.
We tried inputting an NLP filter order to prioritize rank over location, but that did not update the search results. We have custom fields for both First Name and Last Name - would we need to explicitly add those as searchable fields in order to have the query “aaron” show name-based results instead?
Thanks so much!