Properties beforeproperties itemupdating Websex cam online now chast

Posted by / 26-Jun-2017 10:53

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.

Declare the correlation token for the workflow in the On Workflow Activated activity.

Then, for each activity that affects the entire workflow, bind that activity’s correlation token to the correlation token of the On Workflow Activated activity.

One small difference between Share Point 2010 and Share Point 2013 is that in Share Point 2010 even if the user field is not changed the After Properties in Item Updating event will have the value “-1;#i:0#.w|domain\user1”.

In Share Point 2013 if the field is not changed then the After Properties in Item Updating event contain the user ID.

When accessing a user field in event receivers there are few differences in the returned values when Classic mode authentication is used from the value when Claims based authentication is used.

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.

To solve the problem I changed my code for getting the user from After Properties so it would work for Claims authentication no matter is the field changed using the Peaple Editor control or programmatically.

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.

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.

properties beforeproperties itemupdating-54properties beforeproperties itemupdating-26properties beforeproperties itemupdating-70

This is true for Share Point 2010 and Share Point 2013 and its present only for custom lists but not for document libraries.

One thought on “properties beforeproperties itemupdating”