Sharepoint event receiver itemupdating beforeproperties
Below are shown the results only for the events that have this problem.At the end of this post you can find the complete test results for Share Point 2013.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.
For reference below are all the results from the tests for Share Point 2013 for Claims based authentication and Classic authentication, both when working with a list item using the UI and programmatically.
This is true for Share Point 2010 and Share Point 2013 and its present only for custom lists but not for document libraries.
I’ve done some testing and the results are presented in this post. The test is performed when adding/changing/deleting the item’s user field using the UI (New and Edit form) and when adding/changing/deleting the field pragmatically.
For testing I created a custom list that contains one User field, added the event receiver and overrode all the list item event handlers. The test is repeated when using Classic authentication and when using Claims based authentication.
For every event I tried to get the value of the user field from properties. Also the test is repeated for Share Point 2010 and Share Point 2013.