Itemupdating vs itemupdated mate1dating
Here we will discuss Before Properties and After Properties in Event Receiver in Share Point 2013.These properties are used to get previous values and the current value in the event receiver events.Writing that makes your world pink and sparkly again.But this is the barren end empty world of the remote event receiver and no such this is available.The event receiver was nicely attached and got busy when I uploaded a document. I was trying to change permissions on an item and this was the part of my code that was creating the problems: Inside my SPRemote Event Type.Item Updated I did an Update and making it trigger itself. If you’re dealing with a event receiver with access to server side code, this is not a problem.Previously I also worked as a Premier Field Engineer for Share Point @ Microsoft Belgium.For 5 successive years I’ve been rewarded as Share Point Server MVP for my contribution to the Share Point community: I developed the U2U CAML Query Builder and its successor the CAML Designer, which I develop together with Andy Van Steenbergen.
If it doesn’t, the updating event should not happen again.
You could think that the current values are stored in the Before Properties of the item but that’s not true: the Before Properties are unreliable at this point. When the name of the planet is changed, the update is canceled and an error message is returned to the user.
If the name isn’t changed, the changes are saved to the Share Point list.
After properties are used to get current values in the event receiver events in Share Point 2013.
Recently we got a requirement to get the save the previous value before updating in Share Point 2013.