Indexing catalog content
This topic describes the indexing of catalog content using the Find search provider EPiServer.Find.Commerce with Commerce. In a Commerce solution, Find indexes typed catalog content in the same way it indexes CMS content.
How it works
To index typed catalog content on a site, install the NuGet package EPiServer.Find.Commerce. Catalog content is indexed in the same way that pages are indexed in CMS. Use the indexed items when you make queries against the native Episerver Find API. The FindSearchProvider, which is used by the search provider system, does not get any hits from the items that are indexed using EPiServer.Find.Commerce.
Event indexing
Catalog content is indexed when content is published through the catalog UI, the content repository API, the ICatalogSystem API, or when updating pricing or inventory.
Indexing scheduled job
The scheduled job EPiServer Find Content Indexing indexes catalog content as it does with other site content.
Index conventions
The catalog search attributes IncludeInDefaultSearch, IncludeValuesInSearchResults, SortableInSearchResults, and Tokenize have no effect on content indexed by EPiServer.Find.Commerce. You can only use these attributes when you index data through the search provider system.
To exclude properties from the index, or add extension methods for indexing, use the EPiServer.Find conventions as you do with CMS pages.
Search text field
You can use the [Searchable(false)] attribute to prevent a property from becoming a part of the search text field during indexing. This field adds the values for all properties that are marked as searchable. Public virtual properties with an empty get and set of type string and XHtmlString are automatically marked as searchable.
Search text is used for the free text search:
client.Search<T>().For(q).GetContentResult()
Do you find this information helpful? Please log in to provide feedback.
Last updated: Nov 03, 2015
