This article provides advice on how to debug issues wih auto-completion.
Open up the browser debugger and view the network panel. Start typing into the search box and watch the network panel for any requests to
suggest.json. If you can see requests being sent then view the response from one of these. The response should contain a JSON packet with any suggestions. If the JSON is empty then there are either no suggestions to return, or autocompletion may not have been generated. If you are using concierge auto-completion there will be a
suggest.jsonrequest for each column of the auto-completion. Also check the parameters passed to
suggest.json is returning suggestions but they are not displaying, or are displaying
Also make sure that you check to ensure that all the fields you require are returned in the auto-completion JSON. It is possible that fields were missing in the CSV used to generate the auto-completion.
Non-CSV based auto-completion suggestions are based on words found within the spelling index. Terms can be added or removed from the set of suggestions by editing the spelling black and white lists for the search package that is used to generate the auto-completion.
auto-completion=disabled is not set in the results page configuration.
Also check the
Step-BuildAutocompletion logs for the search package and look for errors and also for the counts of how many suggestions were generated. If the suggestions are CSV based there could be an issue with the CSV file format. Also check the results page options corresponding to the auto-completion data set profile to ensure that the index isn’t scoped in a way that it no longer contains any results. This will cause an empty suggestions file to be generated.
This can occur if your auto-completion is misconfigured to use the deprecated simple json format. If the legacy json format is being used then you will see the trigger value being displayed in your auto-completion instead of the display value. If you have CSV based suggestions you will often have several suggestions triggered by the same trigger word, and this is what’s causing the duplication.
Check your auto-completion configuration to ensure that the auto-completion
fmt is set to
json++ when requesting suggestions from the auto-completion endpoint.
format: 'extended'. (see: Auto-completion widget - data set source configuration)
If you are using your own code to call auto-completion then look at the code that makes the request to
suggest.json and ensure the
fmt parameter is set to