in

SharePoint Blogs

The Best Place for SharePoint-related Blogs

Aaron Robertson-Hodders SharePoint Blog

Adding additional properties to the MOSS People Search

I figured out how to add additional fields from the Profile Import into the People Search today.

This requirement occured to me after discussing how this might be done with Aaron Saikovshi at the APAC SharePoint Conference.

In this particular case, I wanted to add one of the extended properties from the Exchange Users into both the Search Box control and the results page. I suspect, but have not confirmed that this process would work for extensions to the AD Schema too.

There are several steps to make this happen:

1. Assuming that you have a property with data in it, go to the Shared Services Administration page and click on 'User Profiles and Properties' link.

2. Add a new Profile Property for the property you want to include by clicking the 'Add profile property' link at the bottom of the page. The things to pay attention to are the policy settings (properties will need to be available to all those who need to see them!) and the Property Import Mapping (you need to map your property to a physical property crawled by the indexer - just like Managed Properties in MOSS Search - which is actually what this property becomes). In the case of my Exchange extended property this was extensionAttribute1.

3.  At this point I did a full import, just to make sure I could see the values coming through when I viewed the user profiles.

[Ishai has a nice post with pictures for the remaining steps...]

4. Go to the people search page in the Search Centre (or wherever you put the people search).  Edit the page and then edit the properties of the People Search Box. Open the Properties property and add a new Property element to the list, eg:

<Property Name="NewProp" ManagedName="NewProp" ProfileURI="urn:schemas-microsoft-com:sharepoint:portal:profile:NewProp"/>

where NewProp is the name you gave to the new Profile Property above.

5. In the Results Query Options section of the properties for the People Search Core Results web part, edit the Selected Columns property. If your default value is like mine, it will look like there is nothing in there - which tricked me for a while, but click the ... button and add a new Column element for your property equal to the name of your new Profile Property.

6. Edit the Data View Properties of the People Search Core Results web part to add the new column (in lower case), somewhere in the XSL eg. <xsl:value-of select="newprop"/>. Click Apply and Publish (if you have content management turned on). Don't worry if you get a nasty looking error in the web part unless it happens after you publish! You did backup the XSL before you modified it, right?!

I also had to do some crawling of the Content Sources once I had added the new Property and at one point had to reset and re-crawl. I think there is something strange going on there, because the first property I added only seemed to require a Crawl to be available, but the second would not work as a Selected Column until I reset and re-crawled! I'm not 100% on what requires what level of crawling. I can understand a full crawl being required for new properties because that probably updates the property store, but a Reset Crawled Content?!

If anyone has, or tries to get this working with a custom Active Directory column it would be great to know and complete the puzzle!

 

Comments

 

Ishai Sagi [MVP] said:

I wrote about this a year ago, and included screenshots of how to do it :

www.sharepoint-tips.com/.../found-it-how-to-add-properties-to.html

I don't understand the other problem you are describing. A reset is almost never required (only if you have corruption)

June 19, 2007 7:52 PM
 

Aaron said:

Ishai,

This post was meant to be an end-to-end how to, but I agree that from step 4 onwards the process is identical, and I'm going to add a link at that point to your post if that's ok?!

In regard to the reset, I don't know WHY it happened, I'm just reporting that it DID happen! I agree that it should never be required - especially in a large deployment, but I have seen it several times since RTM. I am definitely trying to determine if there is a pattern...

June 21, 2007 12:24 AM
 

Mirrored Blogs said:

Body: Was configuring the people search and found this article which explains it in great detail. In

September 17, 2007 8:49 AM
 

Abby said:

I'm having a problem getting the Manager field to show up in the People Search Results.  Any suggestions?  I've followed all the instructions to no avail.  Thanks in advance, Abby

November 4, 2007 7:39 AM
 

adrh said:

Abby, I assume that Manager is a field from the Profile (ie. AD)? If so and you followed all the instructions, the only thing I can think of is that you reset the crawled content. I realise a) this is drastic, and b) it should NOT be required, but I am nearly certain that I had to at least initially! Let me know how you get on...

November 4, 2007 11:12 PM
 

Sharepoint said:

I am also facing this problem. I am not able to search on Manager field as well as Assistant.

I think there is some additional settings required for searching fields that contain people picker control (as Manager & Assistant both are filled as people picker controls in user profiles).

March 18, 2008 7:31 AM
 

Jon said:

I'm having the same issue with the Manager property.. anyone figure this out yet??

June 26, 2008 11:49 AM

Leave a Comment

(required )  
(optional )
(required )  
Add

About adrh

I'm a Kiwi, living in Australia (for the past 10 years). I work for MacroView, a consulting firm in Sydney specialising in SharePoint solutions, products (WISDOM Document Management extensions, Custom Search solutions) and consulting around Enterprise Search. My background includes experience developing solutions in VB, VB.Net C#, ASP, ASP.Net, SharePoint (from V1) and Office.

Need SharePoint Training? Attend a SharePoint Bootcamp!

Posts (c) their respective authors. Everything else (c) 2007 SharePoint Experts