Sharepoint itemupdating beforeproperties null
From the results it turns out that when getting the value of a user field from After Properties in Item Adding and Item Updating events the value is different when using the New and Edit form from the value when adding and updating the field pragmatically.
This difference is present only when using Claims based authentication.
Afeter Properties[“User Field”] is “-1;#i:0#.w|domain\user1” Because its happening only when adding and modifying a user field using the New and Edit form it seems that the problem is with the Peaple Editor control.
For some reason it doesn’t work as well with claims based authentication as it does with classic authentication.
In the tests user1 and user2 are used and they happen to have ID of 41 and 42.
For example with classic based authentication in Item Adding and Item Updating events the modified value of a user field can be retrieved as below: This code will not work when using Claims based authentication because the value of properties.
Learn about before properties afterproperties itemupdated in Share Point 2013.