Try our conversational search powered by Generative AI!
AI OnAI Off
Best practices for indexing commerce content
Couls any expert help with this? I believe it's gonna be useful for others who is going to use epi epifind
Thanks
Feb 15, 2016 22:43
I haven't used Find for commerce yet so take this opinion lightly. I do generally like to work with poco classes but just as you say, the support for some standard Filters etc will not work. The support for find + commerce is pretty new but something I'm pretty sure they will invest quite some time and effort with. So for upgrading reasons and future I would go with indexing the ootb content items. You will likely get a lot of functionality for free that way and usually someone is paying the bill :)
Feb 16, 2016 6:48
Poco is best if you want to easier change solution in the future. A little more flexible. It's rare though that you get benefits from that kind of flexibility from my experience.
Feb 16, 2016 7:15
A similar question has been asked and answered here: https://github.com/OXXAS/CommerceStarterKit/issues/31
Feb 16, 2016 7:46
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
Hi
I am a newbie to EPiServer Find, I see two different way of indexing the contents
1. EPiServer Find Commerce (OOTB)
2. Indexing the POCO instead of CatalogContent (e.g. Commerce StarterKit use FindProduct poco class)
What's the pros and cons for each of these methods? I want to get the things right at the first place.
One cons of using the POCO is OOTB built-in methods are no longer applicable on POCO. E.g. FilterOnCurrentMethod
http://world.episerver.com/documentation/Items/Developers-Guide/EPiServer-Commerce/9/Search/find-integration/filtering-catalog-content/