12

If you export the web part and locate the JSON string that contains the "refinerConfigurations" you can change the "useDefaultDateIntervals":false and then set your own intervals like "intervals":[-365,-180,-30,-7,-1]. Dates in the past are negative and the future are positive. If you don't know how to export and import a web part let me know and I'll add ...


11

Is this 2013? Not sure about 2010 but in 2013 SharePoint tries to helpfully trim out search results it considers duplicates, and in my experience it's not always accurate. You can tell SharePoint to allow duplicates from the query settings page in your Search results web part:


8

As Vadim mentioned, you cannot create new managed properties in SPO with Refinable option enabled. However, you can map the crawled property (ows_SiteName) to an already created Managed Property in SPO (RefinableString00) as shown in the below image: You can then set an Alias (SiteTitle) to the RefinableString00 property and use it in search just like you ...


7

Christopher, Change how search results appear in the Search Core Results Web Part Excerpt from the article: Change the number of results that appear on a page Under Display Properties, in the Results Per Page box, type the number of results that you want to appear on a page before pagination is required. The maximum is 50 results. The default is ...


7

Continuous crawl is created to try to help keeping your search index more up to date. The problem with incremental crawl is that only one can run at a time (for a content source) and it only updates the index when it's done. Multiple continuous crawls can run at the same time (for the same content source) and they update the index continuously. The main ...


7

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 ...


7

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 ...


7

You need to change Search Display Template. Search Results web part uses the "Control_SearchResults.html" display template that is available under the Master Page Library/Display Templates/Search. Download a copy of that template (preferably, if you don't want to change the ootb one) Open the file in Notepad (or any other text editor) Replace the following ...


6

It depends what exactly you want, but yes that is entirely possible. You want to add to your search query the term: path:http(s)://domain/path/to/site/collection That will restrict your results to only include results who's url contains the path specified, or in other words, who are part of the specified site (or site collection) or it's sub-sites. To ...


6

I solved using CSS: .ms-srch-hover-outerContainer { display:none !important }


6

I'm afraid your hypothesis: Does it recognize search result webparts and skips indexing those? is the good guess. Actually, to be precise, the Web part does recognize the crawler, not the other way arround! Looking at the SharePoint code with ILSpy, we can see that: ContentBySearchWebpart inherits from DisplayScriptWebPart DisplayScriptWebPart has a ...


6

You can use following code in the display template <div title="_#= $htmlEncode(line4.defaultValueRenderer(line4)) =#_" id="_#= line4Id =#_"> _#=STSHtmlDecode(line4.value)=#_ </div> Source - https://ingessharepointnotes.wordpress.com/2014/03/04/sharepoint-display-templates-display-enhanced-rich-text-field/ Another example var desc = $...


6

Either add the safecontrol to your config file or update the SearchResults.aspx page layout's top section. <%@ Page language="C#" Inherits="Microsoft.SharePoint.Publishing.PublishingLayoutPage,Microsoft.SharePoint.Publishing,Version=15.0.0.0,Culture=neutral,PublicKeyToken=71e9bce111e9429c" %> <%@ Register Tagprefix="SharePoint" Namespace="...


6

In the Sorting tab of the webparts "Change query" menu (you need to enter advanced mode to find the sorting tab) set Sort by to ViewsRecent Descendant. This will sort your result on the number of views it has had in the last 14 days (the nubmer of views is by default calculated once a day by a timer job)


6

I don't think it's possible. However, you could add the ID as a "column to show" in the List: after which you will have a corresponding crawled property: which you then can map to a managed property After this you can use that managed property to retrieve the id of the linked company: { "__metadata": { "type": "SP.KeyValue" }, "Key": "companyid"...


5

You also need to install the iFilter from Adobe in order to allow SharePoint to index the PDFs. The configuration changes you made simply tells SharePoint to index PDF, but the iFilter is actually what does the work. Start here: http://support.microsoft.com/kb/2293357


5

Item appears in search only after SharePoint performs a search crawl, so when you add a new item, incremental crawl is not yet performed, so the item is not shown in your search result


5

Incremental Crawls are search crawlers that gather the changes made since the last crawl. Incremental Crawls and Full Crawls cannot be run in parallel. They take charge and hog the whole crawler resource. This also makes it possible to have very outdated search results. An incremental crawl may not pick up changes that happen while the incremental crawl is ...


5

This is how the search in SharePoint works, if you want to include partial matches you need to use prefix matching, that is adding a * at the end of your word like Frank* Note that SharePoint does NOT support suffix matching, like *martin This will not work as expected


5

i applied the october CU and all the previous patches in their order of release. After that i went to Central Admin >> Search service Application >> Search Schema and searched for the "Title" Managed Property and moved the "MetadataExtractorTitle" towards the lowermost order and gave a full crawl After that when i did a search it worked as expected. ...


5

The real answer here is to create a result source where you for "Type" choose "People Search Results". You don't need to add ContentClass=urn:content-class:SPSPeople For example: {?({searchTerms})} {?OR (({searchTerms}) spcontenttype:contact)} will give people + results of contenttype=Contact When testing this in the query wizard it will append ...


5

Yes, you can. Crawling file shares is very easy to set up, and permissions are accounted for - so there is no risk that users find information they don't have access to. In Central Admin Search Service Application, add a new Content Source. Specify your file server and set up a schedule. Do a full crawl and you're up and running in no time.


5

Could very well be a problem related to "TrimDuplicates". This functionality is activated by default and tries to remove duplicate items from your search results. You can turn it off by editing the query with the query builder, going to Settings and turning off duplicate trimming, as per your comment :)


5

To make this happen you need to add a Managed Property in your Search Service Application. You find the existing Managed Properties in the Queries and Results section named Search Schema. Type isDocument in the filter section and hit the green button with a white arrow. You should see this: It tells is that the isDocument managed property returns all ...


5

We noticed this in our tenant. To fix this, we: Went into the search settings of SPO Central Administration Went to Manage Schema Search for the managed property Title Move MetaDataExtractor to the bottom of the list and Move Title to the top Then in the site experiencing the issue, go to Site Settings and go to Search and offline availability. ...


5

Search queries the data from the User Profile Service. Deleting the User Profiles from the SharePoint Admin Center will (eventually after a crawl) remove the users from People Search results.


4

The quickest way is to add the wildcard into the Query Template in Federated Locations. Go to Central Administration->Manage Service Applications->Search Service Application and in the left-hand menu goto Federated Locations. Click Local Search Results and in Location Information, change the Query Template from {searchTerms} to {searchTerms}* If you need ...


4

If you have a high ratio of queries compared to deletes, then you might want to add an event receiver which calls CrawlRuleCollection.RemoveFromResults upon deletion of an item


4

Sanghoon, this message comes from resource file embedded into assembly microsoft.office.server.search.intl.dll and for Core Results web part this message renders when Query Error occurs instead of displaying actual search result, this is why for message XSLT customization could not be applied as for regular search results. But it could be customized ...


4

The user account that operates the search crawling has to be given read permission to the file share you wish to crawl.


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