Tag Info

Hot answers tagged

2

In the query builder, try using the Sorting tab and sort by rank then use the Dynamic Ordering property and set it to Demote to bottom. As long as you can get the query to hit that one page it should show up as the last result. I know it is not getting rid of the link, but at least the user would have to wade through everything before getting to it.


2

You can look at this post below, demonstrating how to custom sort your results using display templates. The managed property must also be sortable. http://www.eliostruyf.com/add-sorting-display-templates/


2

According to Search limits for SharePoint Online SharePoint Online search has the following limit: Limit: Number of rows in a result set Maximum value: 500 Limit type: Boundary(*) Notes: To display the entire result set, issue more paging queries Boundary - A number that can’t be exceeded Since 500 RowLimit cant be exceeded you ...


1

Is this happening with only one document? Because it might be that you will start seeing every document like this in the future. In this case, it is probably a misconfiguration of the Alternate Access Mappings. Can you check that the http://domain is still configured correctly in there?


1

This is a well identified issue which was fixed with the Oct 2013 CU update to SP 2013. This happens because the managed property ‘Title’ is mapped to crawled property ‘MetadataExtractorTitle’ by default as first priority and there was no way to change the order of this crawled property unless October 2013 Cumulative Update was applied. However, this issue ...


1

Sure, create the rule and use: Advanced Query Text Match Query contains one of these phrases (semi-colon separated) = Programmer On a side note you know you can also configure "Query Client Types" and give the developers an ID to pass with their query for logging and performance tuning.


1

Yes, Result Sources are supported for Standard Edition. In order to configure it, Please check this Technet Article Configure result sources for search in SharePoint Server 2013


1

It causes due to query string variables. if your page is having URL with query string #k=YOURKEYWORD then it will reflect in any content search web part. Find a way that would pass query string in this format #Default={"k":"test"} where test is your actual keyword. I took a hint from this article ...


1

I don't believe stemming is the answer as numbers would not have recognized stems like "run, runs and running". You could use "701*" for a free text wildcard search. I would also try creating a Managed Property out of your crawled property and then try a contains search "PartNumber:701". The Content Processor may also be performing word breaking on the "." ...


1

We had the same issue in one of our SharePoint 2010 farm. The issue was present when the search is made on the portal web application and the request is being accepted from a particular Web Front End form the NLB that is running the Query Component. When the Search Proxy get the information for the Round Robin from the Topology.svc it returns the endpoint ...


1

Well we found something, that is not a real solution (We think). Once you create a new template, you add your mapped properties to <mso:ManagedPropertyMapping> tag BEFORE anything else (that means uploading this custom template to library, publishing it and so on). You must do everything locally and after all desired changes are made, than you upload ...



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