Skip to main content

Accessing User Profile details programmatically

When you configure User Profiles, you can get a lot of information of the SPUser. These details can also be fetched programmatically. Let me show you how to do that.

Before we get into the coding, let me first explain you about user profile properties. To check what kind of user profile properties you have in your SSP, open your SSP -> User profile and Properties -> View Profile Properties. Here it displays the list of Profile Properties. You can edit some of the properties and set some conditions like whether user should be able to edit the property or not and so on.

Let's look at the code:

1. First you should add a reference to Microsoft.Office.Server

2. Define the namespace:

using Microsoft.Office.Server;
using Microsoft.Office.Server.UserProfiles;

3. The actual code looks like this:

using (SPSite mySite = new SPSite("my Site URL"))
ServerContext context = ServerContext.GetContext(mySite);
UserProfileManager profileManager = new UserProfileManager(context);
foreach (UserProfile profile in profileManager)
Console.WriteLine(profile["FirstName"].Value.ToString()); //Gets First Name
Console.WriteLine(profile["Manager"].Value.ToString()); // Gets Manager's Name

Here, I'm trying to get the First Name and user's Manager Name for all the profiles who exists in my SharePoint site. As shown in the above code, you can get the details of the profile using the Property Name (FirstName, Manager).

When you run the above code, you may get "Access Denied" error. To resolve this, you should ensure that the credential under which the code runs should have proper permissions. To verify that, navigate to SSP home page, under "User Profiles and My Sites", click on "Personalization services permissions". Under Manage Permissions page, ensure that the user (under that credential the above code runs) has "Manage User Profiles" and "Personal Features" rights. And you got that code working!


Popular posts from this blog

How to update Person field with multiple values using REST API

Person or Group field in SharePoint is similar to a Lookup field. When you are updating this field using REST API, you need to append "Id" to the name of the column in the body construct. For example, the body construct looks like this: data: { "__metadata": { "type": "SP.Data. ListName ListItem" }, "Title": "First Item", " PeopleField Id": "4" }; The highlighted portions should be replaced by the actual List Name and Column Name. In the above example, the REST call is updating a List item with Title and People columns. How to get the value for user ID ("4" in the above example) needs a separate explanation and that will be my next post! The above example works fine if Person field is configured to accept only one value. If we change the Person field to accept multiple values, how do we pass more than one value in the REST call? Since we normally separate user names with semicolon in peop

How to get SharePoint List or Library GUID via REST

Sometimes, you would need List or Library GUID to use that in some operation. In such cases, how do you get hold of GUID using REST API? There is a straight-forward end point which you can use: /_api/web/lists/getByTitle('ListTitle')/Id This will return the GUID of a List or Library. There is also another approach. However this approach works only if a List or Library contains at least one item. /_api/web/lists/getByTitle('ListTitle')/items This is a familiar end point which we use to fetch items of a List or Library. To get the GUID from the response, you would do: var listIDTemp =[0]; var listID = listIDTemp.substring(listIDTemp.lastIndexOf("guid") + 5).split('\'')[0]; As you can see, we are doing string operations to fetch GUID from This contains information only if the response has at least one item.

All about SharePoint List View Styles

Sometimes, there are out of the box features which we tend to ignore and later when we do apply, we are more than happy about the feature which is readily available in SharePoint. One such feature is List View Style. I never thought I would write a post on this. However, whenever I spoke about this with users, people were excited to see the result. That prompted me to write this post. Instead of getting into only theory part, I will basically take use cases where these styles can be applied and also touch up on on some minor limitations with certain style. When you are creating/modifying a List view, you will get an option to select View Style. As shown below, there are 8 options available and Default is always set if you ignore this style. List of View Styles I will take typical Contact List and Announcement List to explian about these styles. Let us go one by one. Default: This view, as name suggest, is the default style in a view. This is one of the widely seen style