New answers tagged people-picker
Since you are using SharePoint 2013 I would recommend you to consider the following approach. In SharePoint 2013 for rendering of List Views and Forms was introduced a Client Rendering Mode (CSR). How to initialize User field in New/Edit forms to current user using CSR Below example demonstrates how to populate User field (AssignedTo) in New form for a ...
This is known issue with custom forms. Can you try replacing "<SharePoint:FormField" with <SharePoint:ClientPeoplePicker runat="server" ID="MyControlName" Required="true" ValidationEnabled="true" InitialHelpText="text" VisibleSuggestions="3" Rows="1" AllowMultipleEntities="true" CssClass="ms-long ms-spellcheck-true" /> you can also try the ...
Depending on your ActiveDirectory Trust, you have to configure some stuff in PeoplePicker to be able to browse foreign Forests. This need still be done with STSADM.EXE in SharePoint 2013, as there are no PowerShell-CMDlets for this. More Information can be found in Technet: Configure People Picker in SharePoint 2013 ...
I have faced similar issue. Maybe there are multiple types of authentications enabled for the SharePoint zone, for example Claims and Active Directory.
I created new providers for each web application (central admin, application and security token service), but with the same name. Configured the people picker to use that name and now the people picker works. I got another issue, but I'll post a new question.
Top 50 recent answers are included