2016 itemupdating


19-Sep-2017 01:51

tl;dr: If you have trouble with stopping the updated-event from firing, compare what you want to change in the before Properties and after Properties.

If they are different, you should go ahead with your update, otherwise not.

In Share Point 2007 the after event was always asynchronous and fired on a separate thread as it allowed to perform some post processing work after the operation has been completed.

But this is the barren end empty world of the remote event receiver and no such this is available.The easiest way to achieve this is to modify the file of the feature which registeres the event receiver as outlined in the following article: case that the event receiver is registered programmatically you can achieve the same result by setting the Synchronization property of the SPEvent Receiver Definition object to SPEvent Receiver Synchronization.Step 1Open Visual Studio 2013 and create an Empty Share Point Project. Go to the Employee Documents library and update the document. Go to Employee Documents library and delete the document. The deleted document log will show as in the following: Summary In this article we saw have how to create an event receiver for a Document Library and custom list level in Share Point 2013.To overcome this limitation Share Point 2010 has additional functionality to allow synchronous execution of after events.

The default is still asynchronous but you can now configure your after event explicitly to execute synchronous.

Ali, Thanks, but this is something I already have set up.