Stack Exchange Network

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange

New answers tagged

0

we approved that we can use the snippet from "Item_CommonItem_Body.html" template: <div id="_#= $htmlEncode(id + Srch.U.Ids.summary) =#_" class="ms-srch-item-summary">_#= Srch.U.processHHXML(ctx.CurrentItem.HitHighlightedSummary) =#_</div> We only have to care that "HitHighlightedSummary" is included in the ManagedPropertyMapping <mso:...


0

For people who have "modern pages", the default "search this site" cannot be changed. The default will be the O365 search experience, without being redirected to the search center, and without refiners. Reference


0

This is the same problem we/most of the people are facing too. The issue here is, SharePoint Search uses index based on each entity and its metadata. Document is inside a SharePoint site and it only inherits its SharePoint site url but not all site metadata for each document. So there is no way Search will be picking up the site metadata to a document. The ...


0

There is an option in site settings. In your case it would be Site A. http(s)://<Site A URL>/_layouts/15/NoCrawlSettings.aspx And then select "Exclude" for the column that you want to not be indexed.


1

use the querytext-parameter. It's described in SharePoint Search REST API overview E.g. /sites/OneVSS/_api/search?querytext=(path%3Ahttps%3A%2F%2Fcontoso.sharepoint.com%2Fsites%2Ftest%2FLists%2FEmployee) Also be sure to checkout the nice SharePoint Search Query Tool - it helps to easily test access to the query-api.


0

As Shoban stated. Powershell is your best bet. (Get-SPSite "https://SITECOLLECTION/").RecycleBin | ?{$_.Web -match "Sub Site"} or (Get-SPSite "https://SITECOLLECTION/").RecycleBin | ?{($_.DeletedDate -gt "5/13/2019") -and ($_.DeletedDate -lt "5/15/2019")} You should be able to filter by any of the following. Web ID ItemState ...


1

In my installation this behavior was caused by a hard disk running full. Sharepoint writes into the /Index folder and it can grow rather large. In the moment I freed some space (by deleting some logfiles), the crawler would immediately stop and it freed about 2/3 of the space allocated in that directory. All the other solutions with restarting, IIS ...


0

I know this is an old post, but I wanted to comment in the event other people come across this. I am a support engineer at Microsoft and have seen this on several occasions. The reason dismounting your DB and mounting it back worked, is because when u detach the DB, it removes ALL entries out of the SiteMap table in the config DB. When you mount it, it ...


2

If yo want to remove a specific content type use either the exact name in a equals query (note the quotes and the minus): {searchTerms} Path:{Site} -ContentType="My Content Type Name" Or use the content type ID (replace the ID with your own): {searchTerms} Path:{Site} -ContentTypeId=0x0101006090CA8B789FE54589E1936EEC912F6E01 If the content types are ...


4

Site performance shouldn't really be affected by the size of the documents on document libraries. It's not like SharePoint reads all documents when user accesses the site (unless you have some "latest X documents Content Query Web Part on the front page crawling all doclibs). Obviously you need to pay attention to how documents are browsed - so having list ...


0

The managed property is called "body", but it is not query-able by default. To enable querying, you need to modify the "body" managed property in SharePoint's Central Administration. This works in SharePoint 2016. Open up Central Administration Go to: Search Service Application Click "Search Schema" in the left navigation Search for the "Body" managed ...


0

The managed property is called "body", but it is not query-able by default. To enable querying, you need to modify the "body" managed property in SharePoint's Central Administration. This works in SharePoint 2016. Open up Central Administration Go to: Search Service Application Click "Search Schema" in the left navigation Search for the "Body" managed ...


1

You can try this. Add two search navigation webparts in the page Based on the current page, you can hide/show the search navigation webparts accordingly by writing a simple JavaScript that runs on page load. For example , in case of peopleresults.aspx, show the search nav webpart for only Peopleresults and hide everything else.


1

Have you tried to use refinement filters or wild cards in SharePoint search API? Maybe one of the endpoint given below: _api/search/query?refinementfilters='Title:("micro*")' Reference: SharePoint 2013 REST Api - refinementfilters "Containts" OR "SubstrinOf" operator Or http://server/_api/search/query?query_parameter=value* Reference: SharePoint Search ...


0

So the way to add Managed Properties to the drop downs in the Content Search Web part, is to change the Item display template by adding the following to the ManagedPropertyMapping tag at the top of the template: 'property Name'{property display name}:'managed property' Where property Name is the name used in javascript to refer to the managed property. {...


0

You would have to roll this yourself. There is no API for user query history at this time. As for storing it in a list, that would be easy. Then you can make the queries clickable by linking them to your search center using the k= query string parameter.


Top 50 recent answers are included