Tag Info

Hot answers tagged

6

When an authenticated user, whom has never visited a site collection, first visits a site there are a number of tables within the Content database which must be updated. The SharePoint Content database’s UserInfo table stores user specific information about an authenticated user and this information and really acts as a cache which is updated periodically. ...


4

Your best bet would be to remove that field/column from the Public view and all other views where you dont want to see it. If you still want to see the value, create a calculated column which extracts the value from the lookup column and displays that. use the =TEXT calculated column Hope this helps.


4

The User Information List is alive and kicking in 2010. Whether using it makes any sense in your case would depend on what you mean by "this sort of user data".


2

What you'll want to look into is Forms Based Authentication (FBA) with the SQL Server provider. There is a provider for SharePoint that will actually store the credentials in SQL Server via a IIS Access Control List functionality. Using this method, the users do not have to be set up in Active Directory, yet they are still safely encrypted in the database. ...


2

Tried this? using(SPWeb oWeb = SPContext.Current.Site.OpenWeb(guidWebsite)) { SPUser oUser = SPContext.Current.Web.CurrentUser; } If I misunderstood your question, and you are asking about retrieving the number of currently logged in users, Bjorn Furuknap has previously written about this here: ...


2

Check the GetUserProfile from UserProfileManager. You get the whole object, should be the right spot to search for a list of all custom properties.. i'm working on an almost simliar webpart.. im trying to display only a couple of custom properties.. hope to help ...


2

First of all never ever use LINQ in this way in SharePoint! You will retrieve the full user information list from the database when hitting the .Items property! Instead use a CAML query to "search" for the users using the SPQuery object. I would recommend that you use the U2U CAML Query builder to build your query - using that tool you will get the correct ...


2

Each site collection has its own collection of users. My guess is this is happening because the user belongs to multiple site collections and just happens to have the same ID. Check to make sure that there are no other site collections in the same content database that have users with the same ID.


2

This might be a long shot, but in SharePoint 2003 I remember some web parts needed the user to have visited the site collection / site / page before the information became available. In other words, ask User 2 to visit the page.


2

Users have permission to read other users details. If you take the non-admin user, and have them click on a user name someone in SharePoint, like the Modified by of a list item, the user can view the editors profile. The actual list view, or URL in _catalogs, might be restricted, but the data within is not.


2

I suppose _vti_bin/ListData.svc and _vti_bin/client.svc (_api) endpoints have different logic for permission checks. I can reproduce your problem, while logged as a site admin I can access the list, but not as a normal user: _api/web/lists/getbytitle('User Information List') What I also have found in the result, is a new (third) link to that hidden ...


2

There isn't really a way around this with your company policy. When dealing with records from a user who is no longer there, it is better practice to deactivate their AD account rather than delete it. This would allow the user's profile to remain and you wouldn't have this issue. However, since you are deleting users from AD, you could take a different ...


2

Can you describe WHY you want info in the User Info List? Generally you sync with the User Profile Service and leave the User Info List alone. I think you don't understand the architecture. There are many great guides on the topic, the best by far is Spence Harbar's: http://www.harbar.net/articles/sp2010ups.aspx It says 2010 but applies to 2013 as well. ...


1

I'm pretty sure this article explains exactly what's going on. I'm going to give this a whirl. User Profile Sync Issues


1

Using SPServices' GetCurrentUser function you can get all sorts of fields on the current user. Straight from the documentation, here is an explanation of how it works(which BTW I think is brilliant): How It Works The SPGetCurrentUser function does an AJAX call to grab /_layouts/userdisp.aspx?Force=True and "scrapes" the values from the page ...


1

Microsoft decided for some reason to have a predefined undeletable attribute (column) 'Title'. As this shows up everywhere (visible to the user) by default (if you don't suppress it, which you can), many people use this as 'Name' instead of properly defining a name field (which is bad if you ask me). You / your programmer however defined a real 'Title' ...


1

The People Picker does query the UIL along with authentication resource it is configured against. It will also query the User Profile Service. To restrict users to only pick from users added to the Site Collection, see Peoplepicker-onlysearchwithinsitecollection: Stsadm property


1

in SharePoint 2010, once user profile is setup run the Full Syncronization which should automatically try pushing updates to User Information lists across sites. It is possible to use still the old stsadm -sync command to refresh old content databases. Gary Lapointe shared a script ...


1

The code itself is rather strange. Why are you recreating already existent objects (I mean SPSite and SPWeb)? Based on my experience, this could lead to some rather weird heisenbugs, not to mention possible performance hit (especially if the procedure is called repeatedly from a loop). Thuswise, the first thing I'd recommend is to avoid the needless ...


1

I am getting this Error when I am updating the SPItem as below: NOTE: the Web object is initialized through SPControl.getContextWeb(context); this.Web.AllowUnsafeUpdates = true; this.spItemObeject.Update(); this.Web.AllowUnsafeUpdates = false; so i finally changed the code as below its worked fine: spItemObeject.Web.AllowUnsafeUpdates = true; ...


1

Try this code: private void updateUserProfileChanges(string accountName) { string localLastUpdateDate =""; SPSecurity.RunWithElevatedPrivileges(delegate { string centralAdminUrl = SPAdministrationWebApplication.Local.AlternateUrls[0].IncomingUrl; using (SPSite ca = new SPSite(centralAdminUrl)) { ...


1

In case anyone else is trying to understand why the missing fields: I'm sure you'll find that they are due to feature differences between SharePoint Foundation / Standard / Enterprise. SPF does not have the fields you mention on the SiteUserInfoList, where SPS does. A good quick reference to which fields are available in which version: SPServices: ...


1

The previous answer is really not a solution it is just workaround. You best bet is not to remove field or create some calculated field o just use what SharePoint can give to you. First you should create xsl in mapped folder \14\TEMPLATE\LAYOUTS\XSL for example UsersInfoViewStyles.xsl and add content like in image bellow changing field internal name to you ...


1

Mike is right about the user information list, but the ability to make it read only is in the farm administrators hands too. Per web application, you can block the ability to Edit Personal User Information. This security right is in Central Administration, Application Management, User Permissions for Web Application. That may give you at least one option ...


1

There are no "user profiles" in WSS. The info you are referring to is the User Information List which unfortunately cannot be customized like that. Each site collection administrator is going to have the ability to make changes since it is site collection scoped content.



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