Take the community feedback survey now.

Jonas Bergqvist
Nov 4, 2015
  3273
(0 votes)

New version of EPiServer.Find.Commerce

A new version of EPiServer.Find.Commerce (9.3.0) was recently released. This version makes it easier to use Find together with Commerce. We now listen to ecf events, price updates, and inventory updates. We also index markets and relations. More features will be released soon, as the nested querying is being developed by the Find team.

Listening of ECF events

We listen to ECF events. We add your typed content to the indexing queue when a change is made in the ECF layer.

Service API

Your typed content is now indexed/reindexed/removed from the index after a request is made to the service API.

Commerce manager

We listen on remote events from commerce manager, and index your typed content when something changes in commerce manager.

It's not 100% sure that the front end site will receive the event from commerce manager. If the front-end site is down when an event is triggered, the typed content is not  added to the indexing queue. A safer approach will be developed later.

Indexing prices

We index both the default price and the whole price collection for variation content. Performance will be a lot better when receiving prices from the index, instead of using the price provider. It will be possible to make price filters for a specific user when nested query support is released in EPiServer.Find.

Reindex content on price updates

If your document indexes a property of type Price, or IEnumerable<Price>, the document is reindexed when prices are changed, if the price provider raises the price update event. The default provider raises the price update event. More information how to raise the event from a custom price provider can be found here: http://world.episerver.com/documentation/Items/Developers-Guide/EPiServer-Commerce/9/Search/find-integration/raise-price-and-inventory-event-updates/

Remove prices from index

It's easy to remove the indexing of prices for variation content. Documentation how to remove the extension can be found here: http://world.episerver.com/documentation/Items/Developers-Guide/EPiServer-Commerce/9/Search/find-integration/overriding-default-conventions/

Indexing inventory

We index the inventory collection for the variation content. Performance will be a lot better when receiving the inventory from the index, instead of using the inventory provider. There can be a problem indexing inventories if the inventory is changed too often. In that case, the inventory should be removed from the index.

Reindex content on inventory updates

If your document indexes a property of type Inventory, or IEnumerable<Inventory>, the document is re-indexed when the inventory is changed, if the inventory provider raises the inventory update event. The default provider raises the inventory update event. More information how to raise the event from a custom inventory provider can be found here: http://world.episerver.com/documentation/Items/Developers-Guide/EPiServer-Commerce/9/Search/find-integration/raise-price-and-inventory-event-updates/

Remove inventories from index

It's easy to remove the indexing of inventory for variation content. Documentation how to remove the extension can be found here: http://world.episerver.com/documentation/Items/Developers-Guide/EPiServer-Commerce/9/Search/find-integration/overriding-default-conventions/

Relations

We now index relations between different catalog content.

  • Products: Variation references for a product
  • Variations: Product(s) the variation are related to.
  • Packages: Package entries for a package, and the related package(s) for the entries.
  • Bundles: Bundle entries for a bundle, and the related bundle(s) for the entries.
  • Nodes: Both parent node relations, and child node relations.
  • Associations

Markets

Markets are indexed for EntryContentBase, which makes it easy to filter content based on a market. The filter "FilterOnCurrentMarket" only receives entries that are available on the current market.

New version of Brilliant cut

There is an updated version available of Brilliant cut, which uses the new EPiServer.Find.Commerce package.

Github: https://github.com/jonasbergqvist/BrilliantCut

Site: http://www.brilliantcut.se/

Documentation

Documentation about the find integration can be found here: http://world.episerver.com/documentation/Items/Developers-Guide/EPiServer-Commerce/9/Search/find-integration/find-integration/

Nov 04, 2015

Comments

Please login to comment.
Latest blogs
A day in the life of an Optimizely OMVP - Opticon London 2025

This installment of a day in the life of an Optimizely OMVP gives an in-depth coverage of my trip down to London to attend Opticon London 2025 held...

Graham Carr | Oct 2, 2025

Optimizely Web Experimentation Using Real-Time Segments: A Step-by-Step Guide

  Introduction Personalization has become de facto standard for any digital channel to improve the user's engagement KPI’s.  Personalization uses...

Ratish | Oct 1, 2025 |

Trigger DXP Warmup Locally to Catch Bugs & Performance Issues Early

Here’s our documentation on warmup in DXP : 🔗 https://docs.developers.optimizely.com/digital-experience-platform/docs/warming-up-sites What I didn...

dada | Sep 29, 2025

Creating Opal Tools for Stott Robots Handler

This summer, the Netcel Development team and I took part in Optimizely’s Opal Hackathon. The challenge from Optimizely was to extend Opal’s abiliti...

Mark Stott | Sep 28, 2025