Problem statement:   When we create new Document set in Documents library which is having default values for a people and group column, getting following X X X X X X kind of characters in people and group type column value. (Find below screenshot).

Steps to reproduce:

1.        Go to Document library, in my case Documents
2.        Go to Library settings
3.        Go to Advanced settings and set Yes to Allow management of content types?
4.        Add Document set content type to library. As shown in below screen shot.
5.        Go to Create column in library and create new column of type Person or Group with some name. In my case I have given name as TestPeople

6.       Now set default value to the newly added list column using PowerShell script

$w = Get-SPWeb "http://myspmachine/";

$l = $w.Lists["Documents"];

$fld = $l.Fields["TestPeople"];

$usr = $w.EnsureUser("myspmachine\prasad.pathak");

$spFieldUserValue = New-Object Microsoft.SharePoint.SPFieldUserValue($w);

$spFieldUserValue.LookupId = $usr.ID;

 

$fld.DefaultValue = $spFieldUserValue.ToString();

$fld.Update();

 

$l.Update();

 

8.   Confirm or add this site column is part of Document and Document Set content type both. As shown below.

   9.   Now got to Documents library, File tab and select New Document and Document Set

10.       Now you can see the error appearing like following.

      11.   Same way if you upload some document with Document content type and check for the same column you will not find any issue with document content type.

 12. So this issue with Document set content type only.

• Edited by Prasad Pathak Thursday, May 28, 2015 5:49 AM removed the first image

Hi Prasad,

Since People and Group column in SharePoint 2013 differs from that in SharePoint 2010.

Please test the issue with this:

http://www.sharepointcolumn.com/sp2013-setting-people-picker-value-in-newform-aspx/

As workarond, you could

use Event Reciever to add value field with Add Item action

Or

use workflow to add filed value when new item created.

If this is an emergency, you could contact Microsoft support engineer or provide feedback to Microsoft Developer Platform. For your convenience:

http://officespdev.uservoice.com/

Regards,