Skip to main content

SharePoint 2013 People Picker JSON is undefined error after upgrade

Introduction
After upgrading a collaboration site from SharePoint 2010 to SharePoint 2013, an error was received when using the People Picker in SharePoint. A "JSON is undefined" error is received when initiating the People Picker.

Solution
Douglas Crockford has provided the json2.js script on GitHub. Make a copy of this script and paste it into the LAYOUTS directory in SharePoint 2013. Typically, you create a directory scripts before and paste json2.js into that directory. Locate the file pickerdialog.master in the LAYOUTS directory and make a copy of this file for backup. Open the file pickerdialog.master and find the following line
<sharepoint:scriptlink language="javascript" name="core.js" localizable="false" runat="server" />
Above this line, create this entry
<sharepoint:scriptlink language="javascript" name="/_layouts/15/Scripts/json2.js" localizable="false" runat="server" />
Save the modification in the file pickerdialog.master.
Now you can open an InfoPath 2013 form which contains a People Picker Control in Internet Explorer 11. Make sure that the compatibility mode is disabled in Internet Explorer 11 for the SharePoint 2013 domain. Try to select a user with the People Picker Control. The "JSON undefined" error is no longer displayed.

Comments

Post a Comment

Popular posts from this blog

Nintex Web Service call error: Unauthorized

Nintex Web Service call unauthorized (401) Issue: When Nintex web service call fails with unauthorized error (401) Remedy: Ensure all of the SSL certificates have been installed in IIS and SharePoint. SharePoint:  Central Admin Security In the General Security Section, Manage Trust Select New Enter a friendly name. Browse to the saved file. To save a certificate: Navigate to the site. Select the cert icon. View Certificates. Select the Details tab. Copy to file. Next, select DER encoded binary X.509 (.CER) Select/enter a path/filename. Next, and select Finish to save to local filesystem.
Post a Comment
Read more

SharePoint User Display Name Incorrect

SharePoint User Display Name Incorrect Scenario: This scenario occurs when SharePoint pulls the display name value from active directory. At some point later, a change was made to the display name. The change in display name was not pushed down to SharePoint.  Find the SharePoint User Account Identity Go to a site collection/site where the incorrect display name is used. Go to Site -> Site Settings Under "Users and Permissions", select "People and Groups" Locate a group where the user is a member Click on the name of the user to find the user's information You will see the account name to use in the script to change the SharePoint user display name Change SharePoint User Display Name Run powershell as an administrator, and call the SharePoint snapin if you are not using the management shell. Use "Set-SPUser". Specify the account (identity), the new display name, and the site.  Set-SPUser -Identity 'account_name' ...
Post a Comment
Read more

AgreeYa QuickApps for SharePoint Javascript Files Missing

Description: SCRIPT5009: 'xxxJavascript Control' is undefined. Cause: The error happens because javascript files required for the QuickApps Web Parts are missing. This occurrence has been observed to happen when a Web Application is deleted. Resolution: Check to see if the javascript files are found in the following location: %program files%Common Files%Microsoft Shared%Web Server Extensions%wpresources If the files are not found, reinstall QuickApps.
Post a Comment
Read more