SharePoint People Editor Control Validation

I was recently working on a visual web part in SharePoint 2013. I added a people editor control on the ascx file. And when I tried to enter the user's name and press enter, the text box started behaving like a multiline textbox. It did not validate the user. Even when I searched for the user and selected, the user did not show up in the textbox.

The HTML for the control is simple. I have used this in many other projects.

I went crazy. There is so much to learn in SharePoint. SharePoint makes you feel humble, rookie :)
This is how the people editor behaved...

I tried many things. I even tried to implement Client people picker introduced in SharePoint 2013.
Then I stumbled upon a blog by Bill Daugherty II. He had explained about some issue he is facing. Which thankfully worked for me too.
http://myspexp.com/2011/03/23/using-the-sharepoint-peopleeditor-in-a-gridview/

The solution was to give a script reference to EntityEditor.js file from _layouts.

<script type="text/javascript" src="/_layouts/entityeditor.js"></script>

This worked like a charm for me. I hope it helps others too.

Comments

Working with large xml files in c# .net

Working with large (huge) xml files is always a pain in the … The reason? These files can’t be loaded in to memory. On my desktop, where I have 2 gigs memory, I can’t open the file in even notepad. I was presented with a challenge recently to manipulate one such large xml file. The xml file was of 550+ MB. I know many would say I have seen bigger xml files than this. But the heart of the matter is if I can’t open 550+ MB file in notepad or in xmldocument in c#, then I can’t open any file bigger than this. And hence the logic to play with these files would remain same. The scenario: We have an xml file from which we want to remove a single node without removing its children. In the below sample xml fragment, the node has to be removed. The children nodes, must then be attached to ( node’s parent) node. One Two 100.22 GoodDay 3 4 Five 200.09 Cra...

Error while activating feature - SharePoint 2010

Hi all, While I was working on SharePoint 2010 recently I came across some issues. I am putting them across so that anyone facing the same issue may find solution easily. Error: Error occurred in deployment step 'Activate Features': Feature with Id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' is not installed in this farm, and cannot be added to this scope. Solutions: I was getting this error while ‘deploy’ing a feature from Visual Studio 2010. I searched the entire project for this GUID which is mentioned in the error. I did not find it anywhere. While troubleshooting, I opened the physical folder and opened ‘Feature1.feature’ file in notepad. This xml file was using the before mentioned GUID. I was not able to find it in VS 2010 :( I copied the GUID mentioned in the ‘Feature1.feature’ file and pasted it in the Feature ID section in ‘Feature1.Template.xml’ file. This solved the problem. Why I thought to mention it is because the exception thrown is confusing. It does not tell you...

Upgrade and Migration for SharePoint Foundation 2010

1.1 Introduction Microsoft SharePoint Foundation 2010 has been designed for scale and performance and as such requires new hardware and software requirements. There are 3 major steps while upgrading. 1. Plan and Prepare 2. Perform a database attach upgrade 3. Verify upgrade 1.2 Plan and Prepare Before we run any process to upgrade from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010, we have to determine which upgrade approach to take. In our scenario, Database Attach Upgrade seems to be appropriate approach to follow. We can upgrade the content for the environment on a separate farm. The result is that you do not upgrade any of the services or farm settings. You can upgrade the databases in any order and upgrade several databases at the same time. While each database is being upgraded, the content in that database is not available to users. 1.2.1 Upgrade Approach A database attach upgrade enables you to move to...

Vighnesh Bendre - MS technologies

Search This Blog