20

Try this... Open up the SharePoint 2013 Management Shell as Administrator and run the following command: Enable-SPFeature SearchWebParts -url http://<central admin url>


8

I found the cause of my issue. This may not explain why Path works for some, but this route allowed me to properly filter my results: The Path managed property is configured as Complete Matching, meaning that my Path values of /uk or http://mysite.net/uk were doomed to failure, as they are not complete URLs. My solution was to create a new managed property ...


6

Add the Microsoft.Office.Server.Search.Query reference to your solution Then in your code behind, use this reference as the following using Microsoft.SharePoint; using Microsoft.Office.Server.Search.Query;


3

It is possible to create a result source with CSOM. Basically what you do is: Manually create the result source in SharePoint (in the site, sitecollection or tenant level depending on your requirements) Export the search configuration, which gives you an XML file. Use CSOM to import the search configuration to another site, sitecollection or tenant. Have ...


3

I had gone through the same exercise and a good post by Mikael Svenson on doing just that helped me. If you append -contentclass:STS_List_* to your query template within the query rule or result source, these views will all be excluded. In effect all list landing pages will be removed including: AllItems.aspx AllPages.aspx AllPosts.aspx AllCategories.aspx ...


3

Goto the search page where you are showing the results Edit the Search results webpart Edit the Query change query to speaker:{searchboxquery}


3

I think it is locked Down by default in sharepoint 2013. As a workaround, you can make a copy of that result source the modify it. You can point to the arrow next to an existing result source, click Copy, and then modify the copy as necessary and save it with a new name.


3

You can use following query to get the result path:"https://siteurl" (ListID:{CC6FB9E2-92CE-444E-85C7-2E126DFF9ED0} OR contentclass<>SPListItem OR) The above query will give you all results which are not of type SPListItem. If you observe there is an OR condition where we are including search results from a single list. So in your case you should ...


3

Please check the similar issue in Msdn SharePoint 2013 search analytics reports - 'query text' column value is empty in 'top queries by month' report 1.Run the script to start the timer job: $ua = Get-SPTimerJob -Type Microsoft.Office.Server.Search.Analytics.UsageAnalyticsJobDefinition $ua.GetAnalysisInfo() $ua = get-sptimerjob -type microsoft.office....


2

If I understand your situation correctly you can add a filter to the Search Results webpart on your search page. Put the page in Edit mode, then Click the upper right corner of the Search Results Webpart and click "Edit WebPart" Click "Change Query" in the properties section In the "Query text" box, copy paste this: (contentclass:"STS_ListItem_850" OR ...


2

To set the Type property to People Results, you need to update the Source.ProviderId to equal SearchProvider.LocalPeopleProviderGuid; To set Default Authentication, you need to update the Source.AuthInfo to equal a new AuthenticationInformation(FederationAuthType.LocalNTAuth) object; If you need other credentials, then create a new object of type ...


2

You need to configure separate Result Sources and add them to the search web parts. This blog post shows how to create a new Result Source except that on the Build Your Query step you will filter your query to the Content Source as opposed to the ContentClass or Path that are used on the post. You can then create as many search result pages as you want, ...


2

{Site.Url} will be the URL of the site where the WebPart is, so in your case that's the Search Center. When Microsoft is use the description URL of the site from where the query was issued. then it's due to them expecting you to configure a WebPart file and reuse that in many sites which without the token would require you the edit the WebPart after ...


2

You will need to convert EdwSearchTag into a managed property. After that you can run searches by adding EdwSearchTag as a search term in your query (for e.g. EdwSearchTag contains denials, will return only search results for column values containing denials) Here are the steps: -Choose a field in a list or document library. -Make sure some items in the ...


2

Check into the settings for "trim duplicates". I struggled with this as well, and documented what I found to work, though my findings don't match the official documentation: https://mikesnotebook.wordpress.com/2014/06/03/working-with-the-sharepoint-search-rest-api-on-anonymous-sites/


2

Nickname matching (and phonetic name matching) are passed with the query from the web part or REST request. You can't configure it in the Query Rule. Thinking about it though...you could create a page that does the necessary query and return it as a Promoted Result, but it won't work quite like a result block.


2

Here's why you do get these results: Using a space, an underscore or a dash does not change how the text is word-broken and how the property value is stored in the index. (only storing the value as AdamAndMary may work as you expect) Using Property:A* means "I want results where property contains a word starting with A". This does not force the entire ...


2

As far as I understand, you want to enrich PersonA with PropertyA. PersonA is a user profile in user profile service. PropertyA is a column on a list. Content Enrichment Service is not available in SPO. There is a user voice suggestion open: https://office365.uservoice.com/forums/264636-general/suggestions/9581616-enable-the-content-enrichment-web-service-...


1

Since SharePoint version is not specified, I am assuming it to be SP 2013. You can modify the Search Results web part on the search page to restrict the results based on the content source. Edit the Search results web part and Click on "Change Query". In the Query Text box, use your two content sources, example: ContentSource:"Your Content Source 1" OR ...


1

Without knowing how your farm is created and if you have one search site or multiple ones is hard to say. However, if this condition is true in all environments and all site collections, then your approach is the best approach IMO.


1

I will give here some steps I did: I created my own refiner for the content types. I took the standard one and added the lines: if (ctx.RefinementControl.propertyName == "SPContentType") { var blacklist = [ "Comment", "Element", "Document", "Folder", ...


1

Use the SourceId parameter instead of the "s" parameter. http://server/_api/search/query?querytext='sharepoint'&sourceid='8413cd39-2156-4e00-b54d-11efd9abdb89' You can get more info here: https://msdn.microsoft.com/en-us/library/office/jj163876.aspx


1

You can change search query in search result -> edit webpart -> Change query select property filter as path , select contains option and then select manual option and enter the manual value there.


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

All out of the box Search Crawled and Managed Properties are listed in this https://technet.microsoft.com/en-us/library/jj219630(v=office.15).aspx msdn article To answer your question SPSiteUrl is mapped to ows_SPSiteURL Site is mapped to urn:schemas.microsoft.com:fulltextqueryinfo:sitename


1

For excluding results you can use following query {searchTerms} -Path=https://example.com/sites/test/DeptSiteDec2014/Lists/WorkFlowHistory/*


1

If you would want to set Type="People Search Results", then I recommend you update your code with below. I have created this way. $resultSource.ProviderId = $fedManager.ListProviders()['Local People Provider'].Id


1

The way I understand Result Sources, they are the new Search Scopes. It's more a renaming thing, though there are subtle differences. You may be mixing terms here. You wouldn't normally use a scope as a refiner, but perhaps have different results pages for different scopes, as you'll probably want the presentation of the results to vary.


1

Hi Mark it's hard to find documentation for this but at the end I resolved using this pattern: resultspage.aspx#Default={"k":"*","r":[{"n":"owstaxIdYourManagedProp","t":["cf32e33f-7ca2-470d-956b-29368e54e736"],"o":"OR","k":false,"m":{"cf32e33f-7ca2-470d-956b-29368e54e736":"TermName"}}]} It's important to note that: k:* basically it means "all documents" ...


1

I can't think of a major reason to go with one way or the other from a query standpoint except maybe convencience: ContentSource contentsource:fileserver ResultSource is a property on your KQL object and needs a guid keywordQuery.SourceId = resultSourceId; Also, content sources can be crawled seperately, if you want that level of granularity. Maybe ...


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