Configure the search provider

The search provider is installed using the NuGet package EPiServer.Commerce.FindSearchProvider.

📘

Note

To get the maximum value out of Search & Navigation when developing visitor-facing features for your website, use the Search & Navigation integration for Commerce Connect.

In CMS 12, FindSearchProvider is not used by default. Instead, Episerver.Commerce.Find is used for CMS and front-end commerce searches. FindSearchProvider and any other SearchProvider namespace is legacy Mediachase functionality that can generally be ignored.

Configure the search provider

To configure the Optimizely Search & Navigation provider for Optimizely Commerce Connect:

1. Create an index at find.optimizely.com.

2. On the index's details page, make a note of the values for serviceUrl and defaultIndex.

3. Configure SearchOptions in your appsettings.json file.

4. Set the DefaultSearchProvider of SearchOptions to FindSearchProvider.

5. Update the ServiceUrl and DefaultIndex values to match the values from the index details page at find.optimizely.com:

   JSON

   "EPiServer:Find": {
     "DefaultIndex": "(set the defaultIndex here)",
     "ServiceUrl": "(set the serviceUrl here)"
   }

6. Ensure that the following item exists in the SearchProviders list of SearchOptions:

   JSON

   {
     "Name": "FindSearchProvider",
     "Type": "EPiServer.Commerce.FindSearchProvider.FindSearchProvider, EPiServer.Commerce.FindSearchProvider",
     "Parameters": {
       "queryBuilderType": "EPiServer.Commerce.FindSearchProvider.FindSearchQueryBuilder, EPiServer.Commerce.FindSearchProvider",
       "simulateFaceting": "true"
     }
   }

7. Change the item in the Indexers list of SearchOptions to use the appropriate index builder for the search service:

   JSON

   "Indexers" : [
     {
       "Name" : "catalog",
       "Type" : "EPiServer.Commerce.FindSearchProvider.FindSearchIndexBuilder, EPiServer.Commerce.FindSearchProvider"
     }
   ]

8. Rebuild your search index from the Commerce Connect Admin search interface.

📘

Notes

• The Search & Navigation search provider for Commerce Connect matches only the basic query string against fields of type integer or string. While catalog meta-fields of type float, double, or decimal may be marked as Include in Default Search in the meta-field configuration interface, these fields are not matched against the basic query string.
• Other querying (filters, queries, or faceting against specific fields) functionality works on meta-fields of type float, double, or decimal.
• If you want to match against these data types from a basic query string, store the data in a string-typed meta-field, and mark that field as Include in Default Search.