7

In order to display search results using custom sorting order the following Search Results customization should be applied: Note: The customization described below are verified with People Search Core Results web part. Important: But before we proceed let me clarify the main limitation of this approach: solution described below allows to sort ...


7

I have done this in 2010 using the ListData.svc and Kendo UI autocomplete. You use ListData.svc to get people from the UserInformationList, by default this will include groups. In my example I limit the query to Person. If you wanted to use the new REST API instead of the ListData.svc REST API you would just point your read operation to the new end-point. ...


6

The 'User/Group' field has two interesting metadata properties: SelectionMode = people only / people and groups SelectionGroup = group to filter the members When searching for users, use the api url: _api/web/siteusers?$select=Id,Title&$filter=startswith(Title, '{term}') When searching for users in a group, use the api url: _api/Web/SiteGroups/...


6

The solution was to change sps3 to sps3s such that the url was sps3s://mysites. I thought I recalled another protocol but I couldn't find any hint of anything other than STS from the SharePoint 2007 days. I eventually stumbled upon this article which provided the answer as well as many other search crawl related issues and their solutions. After I found ...


5

Two things, the start address for Profiles should be sps3://mysitehost. The permissions on the User Profile Service for the default crawl account has to be allowed to "Retrieve People Data for Search Crawlers". Go to Central Administration | Application Management | Manage Service Applications. Select the User Profile Service Application (don't click the ...


5

This is what I have been using to get an SPFieldUserValue from the resolved users and groups in a PeopleEditor control. public static SPFieldUserValue GetPeopleFromPickerControl(PeopleEditor people, SPWeb web) { SPFieldUserValue value = null; if (people.ResolvedEntities.Count > 0) { for (int i = 0; i < people.ResolvedEntities.Count;...


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

I have found the way... this should be refinementfilters = 'and(PreferredName:("kumar*"),Department:("dev*"))'


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

You need to enable cross domain photo setting. Try below code: $wa = Get-SPWebApplication http://sitecollectionurl $wa.CrossDomainPhotosEnabled = $true $wa.Update() Reference- Enable cross domain photo


3

OK, got it. I forgot to set the User Property "Manager" in Userprofile to indexed.


3

The number could change based on when your user profile sync is scheduled. Profiles can be added or removed based on those sync schedules. Then you have the crawl schedules where the profile changes will be reflected in the index. It is possible that a crawl ran, but that something prevented it from reading all of the profiles, but that were picked up ...


3

You need to setup a MySites host in order to take advantage of profiles. You do not need to have mysites enabled for people search to work. If you're worried about MySites being enabled you can keep self site creation turned off and turn off the social features. So as you already have the MySite host configured, you people search will work. I dont see ...


3

As it turns out, I changed over to using FirstName and it worked. In digging around I found the following: Go to Central Admin, Go to Service Application, Search Service Application, Search Schema (left menu) Type in the Managed Property Name, ensure that it has "Sortable" as Yes (Active). And then, I guess, wait for the next crawl for it to work.


3

I do it for Twitter Name in a sample. Create the Managed Property if necessary Full People Crawl Copy the Item_Person.html file Add your property and the code to render it Publish the Display Template Create the Result Type rule Test The whole walk through it here: http://www.ableblue.com/blog/archive/2013/06/05/introduction-to-sharepoint-2013-display-...


3

Could you explain a bit more? What do you want to achieve? If you want to filter the results you could simply go with a modified query in the resultsource / webpart something like JobTitle:Developer {searchTerm}. Configure Result Source https://technet.microsoft.com/en-us/library/jj683115.aspx Or Customize Queries https://blogs.technet.microsoft.com/mspfe/...


3

No, SharePoint online doesn't provide out of the box solutions to acheive this. You can use react script editor! Or create a list for out of office users, calaculate the coming date modify view to show the employee as this filter [coming date] > TODAY


2

The limit is 50 records per page. Try 50 and it will display 50 per page. Changing it to 51 will revert to 10 results per page


2

I had the same problem while trying to use the default Department field as a refinement filter, once I set "Allow this property to be used in scopes" on the Managed Property it started working.


2

There is an additional step of setting permissions on a registry key (if you have your accounts set up a certain way, i.e. not everything is running a the farm account, etc). The keys are mentioned here: http://blogs.msdn.com/b/jorman/archive/2011/02/16/people-picker-why-don-t-you-trust-me.aspx and the specific step is pasted below for convenience: Set ...


2

Finally got this resolved, the issue was with spacing between parameters in setting the peoplepicker-searchadforests property. I previously was using this: stsadm -o setproperty -pn peoplepicker-searchadforests -pv "domain:domain.local, domain\username, password" -url http://spserver I should have been using this: stsadm -o setproperty -pn peoplepicker-...


2

On the same note as Per, because you already have 2 Web Applications for each of "My Sites", after configuring 2 Search SA's you would actually need to use the Service Connections under Manage Web Applications to establish the correct relationship for either the User Profile SA and Search SA (of course each Search SA is targeting apropiate Content Source or ...


2

Found my problem... Instead of a full crawl on the content source, I did an incremental crawl. Silly me... So it worked all along


2

The FIM sync service is by far the most complex service in SP2010. Some things to check: Debugging the synchronization service you can use the FIM Client to check for issues in the sync process. The client is usually located at C:\Program Files\Microsoft Office Servers\14.0\Synchronization Service\UIShell\miisclient.exe Select a full sync and look for the ...


2

I think below link is what you are looking to achieve Click here! Also please check out the technet article link in that post. Hope this helps Cheers!


2

Source: http://englando.wordpress.com/2011/01/07/tip-change-sort-order-in-people-matches-sharepoint-2010-web-part/ The People Matches web part in SharePoint 2010 defaults to a sort order that you may not find intuitive. So in order to change it to something more user friendly you will need to edit the web part and modify the XSL. Edit the People Matches ...


2

Each time a user starts to tag an item in SharePoint 2010, the Keywords portion of the Term Store is queried in real time to see if suggestions can be made to the user about previous keywords that other users have used. If a keyword appears in the list of suggestions and the user deems it suitable, the user can use it to tag the item. If not, the user can ...


2

You have to do several steps for the highlighting Create a search managed property with your flag: http://technet.microsoft.com/en-us/library/ff621097(v=office.14).aspx#section2 Map the crawled property of your flag to the managed property you created Do a full crawl Alter the fetched properties of the core result webpart and fetch your new managed property....


2

Check the result sources: People: {?{searchTerms} ContentClass=urn:content-class:SPSPeople} Local Content: {?{searchTerms} -ContentClass=urn:content-class:SPSPeople} For local the minus in front of the content class excludes the people results. For people the contentclass excludes your list. Create a copy of the people result, add your custom list with ...


2

Everything you describe here is EXACTLY what the User Profile Service is built for. Can you explain that to your client? Tell them that you can use the User Profile Service and be done in a couple hours or spend days, weeks, months working around it and they will never be happy, finally returning to the User Profile Service. Sometimes it is your ...


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