Sitecore sxa custom filter based on content tree multiple node selection as datasource

Question

We have a specific requirement in sxa search, we want to create a facet based on datasource selected from one of the treelist field which hold some node from content tree, for example Article and Product node. So we need Article and Product in facet and based on selection we want to show the children item in search. Let say if user select Article node then in search result show all children node of Article.

Let say All items under specific node which selected in treelist but how can we make it as facet. Assume we have below content tree structure :

Home

• Products
  • Product 1
  • Product 2
• Articles
  • Article 1
  • Article 2
• Events
  • Event1
  • Event2

If we select below node from treelist for facet source : Products Articles

Facet must be look like

Section (facet title) Products Articles

Assume if user select "Products" then search result must be:

Product 1 Product 2 Suggestions will be appreciated :)

Answer 1

Facets work on fields. So you should have a field in your items that determines if the item is a product or an article (or ...). This could be the template, but that is rarely named as you want it.

I solved a similar issue with a computed field. I added a computed field into my (sxa) index that contains the text you want as facet based upon the logic you need. So, in your example you should store "Products" for each product item, "Articles" for each article item and so on...

Once this is done (don't forget to rebuild the index to populate the newly created computed field), you can create the facet on this computed field.

Update

Based upon your comment, the question became a bit more clear. If you want the content authors to select which results a search should contain, you don't need a facet but a scope. You can read more on those here: https://doc.sitecore.com/users/sxa/93/sitecore-experience-accelerator/en/sxa-search-facets,-scopes,-and-tokens.html

You could use the same computed field for the scope(s) - but for scopes you probably won't need it. You are able to define the scopes easily based upon the location and/or the template. Your editor should pick the scope in the search result component.