Tag Info

Hot answers tagged

12

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" ...


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 ...


6

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

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" ...


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

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

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 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

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

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. ...


3

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 ...


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

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 ...


2

you can use only AddFieldAsXml because Multiselect User Field is marked as non-UserCreatable :) list.fields.AddFieldAsXml(<Field Type="UserMulti" DisplayName="My_User_Field" Required="FALSE" UserSelectionMode="PeopleAndGroups" UserSelectionScope="0" Mult="TRUE" Sortable="FALSE" ID="{7293d78b-f9b3-4cce-b85f-ac499fc4fcf2}")


2

Cast it to an SPFieldUser, or create an SPFieldUser in the first place, and set AllowMultipleValues to true.


2

I would assume that you have some custom CSS in place because this won't happen by default. It's hard to tell from your image, but the People Picker looks like it's not the normal size, so there's something custom. I'd peel back those customizations and layer them back in one step at a time until I found where I was going astray.


2

Short answer, no, you can only select users in the profile database. The People Picker you get in InfoPath 2007 is an ActiveX control there's little option for customization. The selection of people comes from the users in the profile directory so you can't direct or configure it like you can with the browser picker. The two are different beasts so don't ...


2

You have alternative. You can write your own Custom Claims Provider. Sole purpose would be to provide better People Picker experience. Your custom claim provider would be responsible for searching and People Picker look and feel but at the end it would save resolved entities as default FBA claims. I did some researching in this direction and I even made ...


2

There is a global function that gets invoked named "EntityEditorCallback". If you want to have your own code run after that function is complete, you can override the function so that your own events get run after it. Note this function runs after the people picker has resolved value of the field to an actual sharepoint user. See this stack overflow post ...


2

It took me some time and I lost some hair in process, but I managed to solve this one. And it's so simple that it hurts. When developing custom claim provider you are overriding method FillSearch. Here you are filling search results with your custom entities. When creating new custom entity just add new key to your EntityData hashtable and call it .... ...


2

AFAIK, the send email activity will try to resolve the string into a principal and get its email address. Please try giving valid user names and check it. There is also a OTB condition available in SharePoint Designer which checks if provided value is a valid sharepoint user. You may want wrap sending email under that condition. UPDATE: I tested that if ...


2

Looks to me like there are some rogue configurations in your web.config. Did you ever set a custom membership/role provider manually or in IIS? Did you ever use FBA? The error message you're getting looks like there is a custom membership provider set which uses a non-existing (or no longer existing) connectionstring for a local SQL server instance. So when ...


2

Could you just override the style the people/group input field to be taller? I don't think you're going to be able to mimmic the functionality of the people picker easily. Looking at both 2007 and 2010 person/group fields, you'd just need to apply a height property to the .ms-inputuserfield in your application page CSS to set a height to say 100 px. This ...



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