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
This document describes the EPiServer Find search provider for Commerce.
To configure the EPiServer Find provider for Commerce, you will first need to create an index at find.episerver.com. Once your index is created, 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 only matches the basic query string against fields of type integer or string. While catalog metafields of type float, double, or decimal may be marked as "Include in Default Search" in the metafield configuration interface, these fields will not be matched against the basic query string.
All other querying (filters, queries, or faceting against specific fields) functionality will work on metafields of type float, double, or decimal.
If matching against these type of data is desired from the basic query string, we recommend storing the data in a string-typed metafield, and marking that field as "Include in Default Search."
Last updated: Oct 21, 2014