Use the SharePoint peopleeditor Control

This article provides some references for developers who need to use the peopleeditor control.

The following describes the problems and solutions I have used.

Usage 1: add the peopleeditor control to the page of the SharePoint system master page.

When the system master page is used, the corresponding CSS and JS files will be introduced, so the peopleeditor control will work normally.

This situation does not need to be considered.

Usage 2: Use the custom mother page

If the custom parent page is used on the page, it is possible that the peopleeditor control is not displayed properly because of the lack of reference to CSS and JS files.

In this case, four files in SharePoint are introduced:

 <  SharePoint: csslink  ID  = "Csslink1"  Runat  = "Server" Version  = "15"  >      </  SharePoint: csslink  >      <  SharePoint: scriptlink  ID  = "Scriptlink1"  Language  = "JavaScript"  Name  = "Core. js"  OnDemand  = "True" Runat  = "Server"  Localizable  = "False"  >      </  SharePoint: scriptlink  >      <  SharePoint: delegatecontrol  ID  = "Delegatecontrol1"  Runat  = "Server"  Controlid  = "Additionalpagehead" Allowmultiplecontrols  = "True"  >      </  SharePoint: delegatecontrol  >      <  SharePoint: cssregistration  ID  = "Cssregistration1"  Name  = "Themable/corev15.css"  Runat  = "Server"  >      </ SharePoint: cssregistration  > 

After these files are introduced on the custom page, the peopleeditor control can work again.

The peopleeditor control has some attributes used to control display and verification. common attributes include:

Allowempty: whether to allow null

Validatorenabled: enable verification

Selectionset: set user or group

Multiselect: Can I select multiple

To obtain the control value, you can use the leleeditor. resolvedentities attribute to obtain the verified entity.