Itemupdating event

posted by | Leave a comment

At the end of this post you can find the complete test results for Share Point 2013.In the tests user1 and user2 are used and they happen to have ID of 41 and 42.When adding, modifying and deleting item using the UI: You can see that the problem is only with claims based authentication while with classic authentication the results are the same when the item is added/modified using the UI and when it’s added/modified programmatically.

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.In Share Point 2013 if the field is not changed then the After Properties in Item Updating event contain the user ID.Because of these differences it’s possible that your old code which has worked fine with classic authentication will not work with claims based authentication.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.

Leave a Reply

  1. Horney chat without subscribing 20-Aug-2017 13:03

    It was purchased on a date in 2013 – the year that was embodied by so many life upending events.

  2. Hindhi sex info chat 10-Jun-2017 05:32

    Onze cameramensen reisden weer heel Europa door op zoek naar de heetste en geilste meiden...daar slaagden ze ook in!

  3. Sex mobile strangers chat uk 18-Jan-2017 16:26

    Our anonymous text chat service is fast, live and instant.

Free sex chat without without payment