Hot answers tagged

3

After going through your question(which I must say well described), I figured out that only thing which you have to do is to create a custom Result Type and specify the display template(which you have already created) which this custom result type will be using. Following are the steps to create custom Result Type. Go to Site Settings --> Search Result ...


2

You are missing one approach. If you know all the possible values you can use entity extraction using dictionaries to scan that mp with a multi-value, and have it populate to the WordCustomRefinerX managed properties. If that's not an option, I would go with your options in the order you list them. For the display template option you might want to add logic ...


2

I would go for option number two as I did something similar in the past. It requires some development, but in the end, it is easier to maintain. The approach of the article you linked might work, my approach back then was different. In your refiner display template where you loop over all the available refiners, you split the values based on your delimiter. ...


1

This helped me when I had a problem to make the sort order to behave as I wanted: Why can't I sort the Search Results Web Part by a Managed Property? Basically, you need to remove the JSON in order to make the web part sort according to the settings in the query builder. Otherwise the JSON overrides the setings in the query builder.


1

Managed Properties are agnostic of Site Collections. So "Wiki Category" does not belong to any site collection. They are bound to Crawled Properties that are either "out of the box" or created as the result of creating Site and List columns and then crawling the content. The only way to ensure that the Wiki Category you seek is from a specific site or site ...


1

Since it was created on the SSA level, this property refers to multiple site collections. You have another option to create a managed property on the site collection level and map it to that field and you use it on the site collection level.


1

The reason is when they were created, they were added on the SSA (Search Service Application) level not on the site collection level. I found this article very helpful in explaining the differences and limitations


1

Look in your crawl rules. Last time I did this it also created a crawl rule to exclude the item from subsequent crawls. just remove the rule.


1

Answer: (SharePoint 15.0.4571.1502) If content is re-crawled (eg full crawl, or this item is changed during an incremental crawl) then the item will re-appear in the search results https://technet.microsoft.com/en-au/library/jj219587.aspx does not mention this behaviour. The same behaviour occurs for either of the two remove functions Remove an item from ...


1

You cannot "Query a View". You can evaluate the view filter criteria and replicate the query in search. So if you want to filter on a Hashtag simply query the hashtag, like #SharePoint. If you are using other types of metadata you can query that too. The search engine is actually very controllable and predictable. If you are struggling I recommend the ...


1

Yes, you can. Try adding a search results webpart to you page, and edit the properties. Then click on "change query". You can specify a tag there. If you use SharePoint 2013 Enterprise you can also you the CSWP. Also you can do much more via the advanced view (Switch to Advanced Mode):



Only top voted, non community-wiki answers of a minimum length are eligible