If you want to boost field during the indexing time, you can use the "boost" property of field in the index configuration. For example:
Below is another solution how you can boost an item based on keywords, which user entered:
I guess you are going to use multilist type for the Tags field. The multilist field is a reference field and contains IDs of ...
You need to create your Guid variable first before trying to filter FacetCategory on it, Something like:
Guid facetGuid = new Guid(facet);
containsQuery = containsQuery.Or(item => item.FacetCategory.Contains(facetGuid))
It sounds like you are on the right track. What you need is computed index field. You add another field to your index that indexes the parent item name as part of the document that you are indexing. John West has written a blog post about computed index fields here:
You need to check this part of the documentation: https://doc.sitecore.net/sitecore_experience_accelerator/setting_up_and_configuring/configuring/extend_search#_Extend_search_to_3
This explains how to use a link type field in the facets. Add a computed field and use that fieldname in the facet:
Add the following definition to your search configuration ...
To turn the IDs in your facets into real item names, just enable this setting. This will cause Sitecore to translate facets that are IDs into real item names.
<!-- RESOLVE FACET VALUE TO FRIENDLY NAME
If you are storing a field in the index that is being faceted on, it may be stored as an ID. This Setting
when set to true,
will try ...
Based on your question, I think you may have added the config for the facet field to the wrong index. You have given the example:
But you don't say which index this is adding the field too. It ...
You have written that "field is getting added to sitecore_master_index" but SXA is using its own indexes - sitecore_sxa_master_index and sitecore_sxa_web_index.
Check if the field is present those indexes.
There is one more issue. In the field name skip type suffix, it will be automatically added by Azure Search logic (after discovering field type). Just ...
If you want to override how the default script works all you need to do is to override removeFacet() function in component-search-results-filter script of Search base theme.
Few things you need to know:
all search renderings are using/can use signatures (each filter support one or multiple signatures) - so it's not just about unselecting elements in UI but ...
There is an option to do that. Checklist Filter has "Collapse on selection" checkbox in renderings parameters dialogue which when selected will make a filter to collapse when the value is selected.
Take a look here:
There are global and local facet types, if you want the SXATags to be global, there is checkbox Global on the facet item to check, if for specific items (local), you will need to update the facets field on the targeted item, here is the link for Sitecore documentation:
We recently faced same issue on Sitecore 9.0.2 & SXA 1.7.1.
when contacted the Support team, they did mention it is a bug and provided patch for it.
Reference number: 255689
Patch link for SXA 1.7.1 https://sitecore.app.box.com/s/izuju5sf8z8zup9ixnut72gmwl38dlx1
Note: This is fixed on SXA 1.8.1
You will see the differences with the same search criteria for master DB and Web DB, because of the multiple version and workflow states in the master database. If you want to filter out the result based on the latest published version then you need to add new facets in the Sitecore - https://doc.sitecore.com/developers/91/sitecore-experience-manager/en/...
Your query looks good, I test it on Sitecore 9.1, SOLR with a Text field, that work with this adjustment. It is now facetOn "_category" looks like because the field(name: "Category") your field is named "Category" so use
search(rootItem: "92B4F8E7-6324-4C01-B873-7FDC992EDDEE" facetOn:["Category"] )
It is not giving a count per facet. you can do that by ...
The Minimum Number of Items setting that you've used is the correct one. I'm currently in the process of setting up the same filter (but only with single select) in the exact same version of Sitecore and SXA that you are using and currently it looks like this:
Have you double checked that everything is published to the Web DB properly?
In our case we had ...
To quickly fix this issue, you need to go to $Path_To_Your_Sitecore_Instance$/App_Config\Modules\SXA\Z.Foundation.Overrides and open Sitecore.XA.Foundation.Search.Azure.config in text editor.
It is not possible out of the box. You can play with ranges by using Filter (Manage Range) rendering but you won't have a dropdown there, only the following configuration is possible:
You can also define range using Filter (Range Slider) rendering, but again - no dropdowns there:
So in order to manage ranges using dropdowns, you would need some custom ...
There is nothing like this out of the box. I would suggest writing Search Token, SXA has a couple of pre-defined ones. Just click Build query in the scope item, type SXA and you will see something like this:
You can write your custom one which will take data from Contact Database for each user. And the results will be filtered by those values. Take a look ...