Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
To configure the Episerver Find provider for Commerce, create an index at find.episerver.com; after which, go to the details page for the index, and make a note of the values for serviceUrl and defaultIndex from the sample web.config.
To configure the Episerver Find provider for Commerce, edit the Mediachase.Search.config file for your implementation.
<add name="FindSearchProvider"
type="EPiServer.Commerce.FindSearchProvider.FindSearchProvider, EPiServer.Commerce.FindSearchProvider"
serviceUrl="(set the serviceUrl here)"
defaultIndex="(set the defaultIndex here)"/>
<Indexers basePath="(the preexisting path)">
<add name="catalog" type="EPiServer.Commerce.FindSearchProvider.FindSearchIndexBuilder, EPiServer.Commerce.FindSearchProvider" />
</Indexers>
The Find search provider for Commerce 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 will work on meta-fields of type float, double, or decimal.
If you want to match against these type of data from the basic query string, store the data in a string-typed meta-field, and mark that field as Include in Default Search.
Last updated: Oct 12, 2015