Tag Info

Hot answers tagged

13

Alex, This really is one of the more vexing issues of upgrading the branding/master page of a SharePoint site. Please try this solution: I created a javascript file called entityeditor.ie9fix.js, added the javascript code that will follow, and saved it in /layouts/1033. In my master page I added <script type="text/javascript" ...


9

Here is the solution: [Microsoft.SharePoint.SPUser]$spuser = $spWeb.EnsureUser("domain\username") $spListItem[$newSMTName] = $spuser $spListItem.Update()


8

I'm working with my PeopleEditor control this way: foreach (var loginName in peopleEditor.CommaSeparatedAccounts.Split(';',',')) { SPUser user = SPContext.Current.Web.EnsureUser(loginName); // user.LoginName is now returns "domain\login" } This code works fine for me. Update: Note 1: EnsureUser will add the user to your site (thanks Ivan Padabed ...


8

I found a solution for this problem. below code should be added to ascx file <%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <SharePoint:ScriptLink name="clienttemplates.js" runat="server" LoadAfterUI="true" ...


7

I believe you might also be able to use: SPUtility.ResolvePrincipal(webApp, null, login, SPPrincipalType.User, SPPrincipalSource.All, false); That said, this is slower than the suggestions using EnsureUser, but does have the benefit of not adding the user to the site, and is a bit more flexible, if you need that sort of thing.


6

I havent tried this for claims in SP2010, but in SP2007 this was done for FBA by adding PeoplePickerWildCard element to membership provider in web.config <PeoplePickerWildcards> <clear /> <add key="AspNetSqlMembershipProvider" value="%" /> <add key="fbaMembers" value="%" /> </PeoplePickerWildcards> ...


6

Active Directory Import is similar to the Profile import mechanism we had back in SharePoint Server 2007. It's an awful lot easier and quicker to configure than "SharePoint Profile Synchronisation", AKA "User Profile Synchronisation Service" (in services on server) AKA ForeFront Identity Manager (FIM) for SharePoint Server 2010. Enabling AD ...


4

Here is a plain jQuery example. I can't take credit for it, I believe Marc Anderson came up with it. Just change the column variable with the display name of your column. var columnName = 'Assignee'; // There's no easy way to find one of these columns; we'll look for the comment with the columnName var searchText = RegExp("FieldName=\"" + columnName ...


4

To leverage your work, you can use SharePoint jQuery based library to work with your forms and fields: jPoint - jQuery for SharePoint forms, lists, webparts, and webservices And then you just do: jP.Form.readForm().MyUserField.val();


4

Chrome is not a supported browser. This is not a bug.


4

Where is your code running? Web part, application page etc? Regardless, you can probably do something similar to the following try { //first get the SPGroup you want to add users to SPGroup addToGroup = SPContext.Current.Web.AssociatedVisitorGroup; //now loop through each entity in your user picker foreach (PickerEntity entity in ...


4

Working as designed. :) I discussed this at TechEd last year: http://channel9.msdn.com/Events/TechEd/NorthAmerica/2011/OSP308 (about 40 minutes in) The fix is custom development.


4

This is my solution: http://blog.vitalyzhukov.ru/peopleeditorand-internet-explorer-9.aspx (in russian). Translated page by Google translator: http://translate.google.com/translate?sl=ru&tl=en&js=n&prev=_t&hl=en&ie=UTF-8&layout=2&eotf=1&u=http%3A%2F%2Fblog.vitalyzhukov.ru%2Fpeopleeditorand-internet-explorer-9.aspx


4

If you mean the width, you just set the width of the PeopleEditor control. <SharePoint:PeopleEditor Width="300" ID="myppl" runat="server" AllowEmpty="false" MultiSelect="true" />


4

If you just want to add all users, just add NT AUTHORITY\authenticated users If you want to add every user individually, you have to get users (maybe as Principals) from AD, and add them to a group in SharePoint. var principal... var loginName = @"MYDOMAIN\" + principal.SamAccountName; var name = principal.DisplayName; ...


4

The client object model uses the standard SharePoint security and don't allow you to run with elevated priviledges. Who has access to see members of groups are defined at the group and the default is only members can see who are members. You can change this by going to: Site Actions -> Site Settings -> People and groups -> Click the Groups header in ...


4

add this code in your .ascx page <SharePoint:PeopleEditor ID="spPeoplePicker" runat="server" Width="350" SelectionSet="User" /> You can also refer to link below. it is showing same problem you have now. there is no difference to take PeoplePicker in SP 2010 and SP 2013. ...


4

David, I guess there is a MultiSelect property which you can set to false to allow only a single entry of User/Group For example: PeopleEditor Control - The article is for SP 2007 but I hope its the same in 2013


4

You can compare the token value of the account to determine if it is equal to the one of the system account. Note that in the following you get the SPSite object under elevated privileges and that comparing tokens only works when the actual account in SharePoint is already listed as the system account. SPUser user = <<your code here>> SPSite ...


3

You need to have Use Client Integration Features permission enabled. By default this is enabled for everybody, but your SharePoint permissions were probably customized and this was disabled. To change this, contact you administrator and ask him to customize permission levels for your group(s).


3

Sounds like you want the PeopleEditor control. If you google around, you'll see some examples of it in use in an aspx page, but the principles are the same, it's just a .NET control.


3

Copying the original poster's answer so we can mark this answered: Installing latest MOSS 2007 CU did the trick and all are well. Thanks for your answers


3

Sounds like maybe you didn't configure the People Picker Wildcards in the web.config file? (I'll delete my answer if this turns out to not be the case as FBA is VERY finicky about how its configured and it could be a million different things!) http://msdn.microsoft.com/en-us/library/bb975136.aspx <PeoplePickerWildcards> <clear /> <add ...


3

Just checking, when you specific the Value Assignment. Do you set your people picker's Return field as: "As String"? Try setting the return field as "Email Address" and give it a try. I want to put this as comment instead of answer but i can't do that yet.


3

Directly the "People Picker" column will not be supported as a lookup in another list. For this scenario, you can create another column of "single line of text" type. Then by using a simple workflow you can update the newly created column with the value from "People Picker column" (Workflow should be triggered on new item added/modified). Now you can refer ...


3

Get Users from People Picker In the MSDN article you already probably know: http://msdn.microsoft.com/en-us/library/jj713593%28v=office.15%29.aspx In this article you have the function: // Query the picker for user information. function getUserInfo() { // Get the people picker object from the page. var peoplePicker = ...


3

I may be wrong, but I don't think there is an easy/elegant way to fix this without some sort of code. The easiest way to fix this, IMO, would be a post-import powershell script which iterates each item of the list, and for each field that needs a fix-up, it reassociates it with it's correct user. If you could get an export of the original site's ...


3

Looks like the issue is with the UserInfo list ID. Can you export the list data and store the User as ID or Email? Then when you import the info call EnsureUser. This will re-associate the user with his correct (or new) userID record in the new site collection.


3

The working code (etension on slashes): var ctx = {}; ctx.Templates = {}; ctx.Templates.Fields = { 'Sponsor': { 'EditForm': function (ctx) { var formCtx = SPClientTemplates.Utility.GetFormContextForCurrentField(ctx); formCtx.registerGetValueCallback(formCtx.fieldName, function () { return ...



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