I would like there to be the ability for the search widget's suggested results to be defined via a field selection. This can then be displayed to the user instead of the default source of suggested results which is configured by the user as the "search field".
The rationale behind this is this. I have a single "School_Address" field which contains a full concatenated address of schools in the country. These school addresses have punctuation (apostrophes, hyphens), special characters, abbreviations for wording such as "St" (Saint), and "CofE" (Church of England). The presence of these result in cases where users cannot yield any search results (using the fuzzy setting here, not exact). A case in point is a common user search entry of "st stephens cofe" - zero results are found via the suggested results, but in the source feature layer there are hundreds. They actually exists as "St Stephen's CofE" - the fuzzy search logic / matching can't seem to see it as a match due to the casing and other characters.
However, I have found that by creating a duplicate of "School_Address" and making everything lower case, removing punctuation and special characters, the search ability is massively improved - users can actually find what they are looking for. The issue is that the suggested results displayed to the user is this cleansed, punctuation free variant which is simply not how they know the school in question. It does not look right cosmetically and in cases can read differently - its purpose however is to yield a high match rate which it does, but it is wrong to display this as the suggested result to the user.
Instead, I would like the ability to display a field of my choice to be presented to the user - in this case it is the cosmetically correct variation of "School_Address", not the "cleansed" version of it. That way the user can search and the widget will have high performance using my cleansed field version and be displayed a correct looking address. So essentially the search is driven by a "search field", and the suggested results are driven by a "Suggested results display field".
One option could be that the fuzzy search does this string cleansing and punctuation removal behind the scenes during the indexing, so the suggested results are cosmetically correct - but i don't now if that's even possible or correct.
I want to stress that the user journey / UI for my scenario cannot involve the results panel. Whilst this allows me to select a field to display to the user, it does require them to enter a search term then press enter, to see a range of possible results, then select the most suitable. This is too protracted and a bad user experience for my use case - we simply want the user to type a search phrase in the search bar and select from the suggested results the record they want to drill down on. No pressing of enter, no results panel and no selection from the results panel.
