Not seeing dropdown options in Homepage Search widget search bar with AI Search enabled

[Patrick Latella]

Hi all,

we've configured AI Search in one of our portals in DEV, and I see the new dropdown in the Homepage Search widget correctly.  However, after moving all the updates to TEST, I do not see the dropdown.

I've reviewed and all the records associated with the portal in DEV are in TEST match.  There are no instance options on the widget in either DEV or TEST.  Everything appears to be exactly the same between DEV and TEST.

Anyone else have this issue?  Any suggestions?  Thanks all! 

See my screenshots, in DEV I see the dropdown.  In TEST I don't.

[Tony Chatfield1]

Hi, have you checked and confirmed that any plugins\applications required have also been enabled in your test instance?

[Riya Verma]

Hi @Patrick Latella ,

Hope you are doing great.

1. Verify Portal Configuration: Double-check the portal configuration in both DEV and TEST environments. Ensure that the relevant records associated with the portal, such as Search Sources, Search Categories, and Homepage Search widget, are properly configured and match between the two environments.

2. Check Instance Options: Confirm whether the instance options for the Homepage Search widget are correctly configured in both DEV and TEST environments. Ensure that the dropdown functionality is enabled and configured consistently across both environments.

// Example code for Homepage Search widget instance options
var searchOptions = {
  showDropDown: true,
  dropDownOptions: ['Option 1', 'Option 2', 'Option 3']
};

// Apply the instance options to the Homepage Search widget
var homepageSearchWidget = new global.Widget('homepage_search');
homepageSearchWidget.setOptions(searchOptions);

1. Check System Properties: Review the relevant system properties related to AI Search. Verify that the necessary system properties, such as glide.search.use_ai   and glide.search.use_new_ai_search, are set appropriately in both DEV and TEST environments.

2. Test Permissions: Ensure that the user roles and permissions in the TEST environment are configured correctly. Verify that the user accessing the portal in the TEST environment has the necessary roles and permissions to view and interact with the AI Search dropdown.

3. Review Upgrade History: Examine the upgrade history of your TEST environment. There might be a specific upgrade or change that has affected the AI Search functionality. Check the release notes, upgrade logs, or any specific documentation related to the version you're using in the TEST environment.

[Patrick Latella · Accepted solution]

Thanks Tony and Riya for the feedback.

The issue was with the [m2m_sys_suggestion_reader_sys_suggestion_reader_group] records associated with the Autocomplete Suggestion records.  These records are not captured in update sets.

So the big take away is I learned from ServiceNow support that AI Search should be configured directly in PROD as certainly elements are not captured in update sets...for example these M2M records.

We're up and running now though, thanks!