Tag Info

Hot answers tagged

2

In your example since HTTP GET request is used, query parameters have to be specified in the URL. You can construct the GET request URL in two ways: http://server/_api/search/query?query_parameter=value&query_parameter=value http://server/_api/search/query(query_parameter=value&query_parameter=<value>) The Search REST service supports ...


1

You can leverage SharePoint Search to create a simple Company Directory. Here are some articles that will help you. 1) You can use any 'template', it would just require adding the right webparts to a page. 2) Here's a good tutorial on building a searchable People Directory: ...


1

I have been migrating profiles from AD to SharePoint list and created a directory for internal reference. 1) For connecting and migrating data from Active directory use the below code in a webpart on page load: DirectoryEntry entry; DirectorySearcher search; SearchResultCollection results; try{ ...


1

(IsDocument:"True" OR contentclass:"STS_ListItem") AND ( (path:"company/Lists/car") OR (path:"company/Lists/plane" title:"airbus") )


1

I had the same issue with the "The input ACL is invalid" one web application. We did a user migration and this migration causes an invalid group claim. The solution was to check the root web for invalid users via PowerShell $web = Get-SPWeb http://mysharepoint $web.AllUsers | Where { $_.UserLogin.EndsWith("|") } The result was an empty group claim ...


1

You need to full crawl, as my experience, continuous crawl will not pick these changes. You dont need to change the schduel the continuous crawl rather manually run the full crawl. From Central admin > search services application > Content Source > click on drop next to the your Content Source and click on full crawl. But if you want to use the ...


1

There are multiple ways to do that, but all those require editing master page or the specific page in question. The easiest way is using CSS. For that edit the page and add new web part. Select "Script Editor" web part. You can find this under group named "Media and Content". Then click on "EDIT SNIPPET" and paste following <style> #SearchBox { ...


1

The simplest way would be to add content editor web part or snippet web part and add the following code to hide it: <style> #titleAreaBox #SearchBox {display: none !important;} </style> Hope this helps!


1

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


1

You can go to that List Settings--> Advanced Settings --> Set "Allow items from this list to appear in search results?" to No.Now these items will not appear in search results. Another option is to break inheritance and set Item level permission in that List. See this blog to know how to set item level permission using designer workflows. This will take ...


1

Since he references my post I figured I should answer your question. After creating your Managed Property you can set the FullTextIndex property like this. $managedproperty.FullTextIndex = "PeopleIdx" $managedproperty.Update()


1

Technically, you are using People Search. I usually use REST for this, but there are analogous Properties in CSOM. You have to set the result source ID to the People Result Source. In your code above remove the HiddenConstraints and add keywordQuery.SourceId = new Guid('B09A7990-05EA-4AF9-81EF-EDFAB16C4E31'); If you really want to emulate the results you ...


1

I think these settings are all set through the Property bag. Try setting some stuff in the UI then inspect the property bag for that web. Here's an old article I wrote years ago about how to do this: https://www.nothingbutsharepoint.com/sites/devwiki/articles/Pages/Making-use-of-the-Property-Bag-in-the-ECMAScript-Client-Object-Model.aspx (in short, in case ...


1

Try isActive=1 this means it equals true. isActive:1 is a contains query.


1

Make sure that you type correct URLs in the search settings. The search center url must be followed by /pages so an example would be http://server/sites/search/pages. The same goes out to the setting to send a users query to a custom result page. Then /pages/results.aspx" must be added to the rest of the URL, like this example: ...



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