Until about FEP4, the search facets data was in SRCHATTR and
SRCHATTRPROP tables. SRCHATTR defines the search attributes and SRCHATTRPROPS
defines the properties for the attributes (like facetable, displayable,
searchable etc).
In Feature pack 5, two new tables for facets are available namely, FACET and FACETDESC.
As an example, to make price facets work for a different currency that is not supported out of the box, like AUD, we first need to create a search attribute (SRCHATTR table) with IDENTIFIER _cat.OfferPrice_AUD
For the above search attribute, create a search attribute property name “facet” and property value “price_AUD:{* 100} 100;{100 200} 200;{200 300} 300;{300 400} 400;{400 500} 500;{500 *}” (adjust the range of facet as required)
Now add a row in FACET table with a reference to SRCHATTR_ID created in previous steps. Add appropriate descriptions to FACETDESC table.
Update registry and clear cache and should be able to view the facet on the storefront.
In Feature pack 5, two new tables for facets are available namely, FACET and FACETDESC.
As an example, to make price facets work for a different currency that is not supported out of the box, like AUD, we first need to create a search attribute (SRCHATTR table) with IDENTIFIER _cat.OfferPrice_AUD
For the above search attribute, create a search attribute property name “facet” and property value “price_AUD:{* 100} 100;{100 200} 200;{200 300} 300;{300 400} 400;{400 500} 500;{500 *}” (adjust the range of facet as required)
Now add a row in FACET table with a reference to SRCHATTR_ID created in previous steps. Add appropriate descriptions to FACETDESC table.
Update registry and clear cache and should be able to view the facet on the storefront.
Hi, thanks for the post, i am getting the below error :
ReplyDeleteundefined field price_AUD:{* 100} 100;{100 200} 200;{200 300} 300;{300 400} 400;{400 500} 500;{500 *}
Could you please clarify.
Thanks.