Tag Info

New answers tagged

0

I would recommend using a query against the change log. The "Event Receiver" really isn't it's just a timer job using the same approach detailed in the article. You could even run it all external to SharePoint from PowerShell if you wanted. No need to deploy custom code to SharePoint.


0

Just enter the first letter of your domain (or your whole domain) and it will return the results.


2

You can disable the timer job responsible for sending mail for MySite Suggestions Email job. From Central Administration, click Monitoring Under the Timer Jobs heading, click Review job definitions Scroll down (or click through pages) until you find a job called User Profile Service - User Profile My Site Suggestions Email Job


0

There must be a PowerShell cmdlet but if you have access to the Database it might be quicker to find that information through below T-SQL (at least that's how I feel it :-)) replace "SP2013_UPA_Profile" with your UPA database name. Hope this helps! SELECT [PartitionID] ,[RecordID] ,[UserID] ,[NTName] ,[PreferredName] ...


1

Yes, it should work. Personally, I don't use the syntax $userProfile["$property"], instead without the quotes like $userProfile[$property], but it should not make a difference, AFAIK. What I don't see in your code, where the $userProfile variable in the Update-UserProfileProperty method was defined. What is the type of your custom property? String / date / ...


0

I would suggest creating an event receiver on the item added (or item updated) event of the list. You can then quite easily acces the profile manager in code and populate your column with whatever profile value you need. As an alternative you could probably also do this in client side script attached using the jslink property of the list but there might be ...


0

Deleted AD users are not removed from site collections. They will be cleaned out of the user profile service and have My sites cleaned up, but they remain in the site collections. This is by design to preserve contextual information like created by fields. There are tools available to help clean up the user information list and permissions like ...


0

The following applies to any property in the User Profile. If you navigate to the Manage User Properties page of the User Profile Service Application you will see the list of all properties. As you have discovered the Department, Office, and Office Location properties are all candidates for storing employee location information, so you need to check with ...


0

Late to the party here but we have just had this exact problem. In fact more so since we had it working on local VM environments but it failed on deployment. After several hours of teeth gnashing and hair pulling we have a solution. Well a workaround really but it works for us within the scope of our requirements. We surmised that it HAD to be some kind of ...


1

The User Profile Synchronization Service must be provisioned by the farm account. So if you run your Powershell script using another account (the setup account typically), it will fail. The solution is either: 1) To run your Powershell script using the farm account. Try shift+right click on Powershell shortcut -> "run as another user"; or directly log in ...


0

What I noticed in my case.. (not sure if this is a rule or just something my configuration needs) ..was the following: in my Synchronization Settings, I have to use SharePoint Profile Synchronization and not Active Directory Import. If I use A.D.I., I will NOT see the attribute dropdown filled in. If I use S.P.S. the dropdown WILL be filled in, and then ...


0

This should be very easy. When you create the custom user profile property you have to make it "searchable" After this you can crawl the people data in your search service application. The search will create a so called "crawled property". You have to map this crawled property to a managed property. After this the custom user profile property should be ...


-1

You could create another column that is a managed property and copy the values into it.


2

This is just an expansion of @aveenavs answer, which works great for me, unless the user is on the root site of the application. The only difference is using _spPageContextInfo.webAbsoluteUrl instead of _spPageContextInfo.webServerRelativeUrl in the url in the ajax call. So I would change it to this: //Get user's personal MySite url ...


0

If you need to get a reference to user object (either an existing one, or one that is just being created), use the ensureUser method (source from this thread): var context = SP.ClientContext.get_current(); var theUser = context.get_web().ensureUser("DEV\testowner"); context.load(theUser); context.executeQueryAsync(function(){ alert(theUser.get_title()); ...


1

Yes, BCS is what you need to use. You don't actually need to setup an external list you just need the connections setup. Here's a link on how to do this in 2010 (similar steps for 2013): http://blogs.msdn.com/b/alimaz/archive/2011/02/20/importing-sharepoint-user-profile-multi-value-properties-using-bcs.aspx


1

If you deteleted and recreated the User ID(with same user name), in that case you have to run the migrate user command as Pirate mentioned but little differently. You need a temp account on which you migrate the profile first then to the id. First migrate to temp id stsadm -o migrateuser -oldlogin <domain\name> -newlogin <domain\TempID ...



Top 50 recent answers are included