Itemupdating beforeproperties null
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.Damon gives just one example of a poisoned dagger in the game of Sharepoint Development: The Item Event Receiver.I’m usually disappointed when writers employ oft-overused metaphors to describe a situation.
Perhaps you need to create, update or delete an item somewhere, or perform some other action related to sites, users or data in Share Point. Before we dig into the “Why it happens” and “The workaround” sections, it’s worth reminding ourselves of some aspects of remote code and authentication in particular.
With that in mind, Share Point 2010 is like a sea of icebergs – there is a lot going on under the surface that you may not notice until it’s too late.
Unfortunately, that makes your project like the Titanic.
Vesa Juvonen (Microsoft) got in touch with me to say that he and the Share Point engineering team had been doing some testing around this, and that whilst the "app-only" workaround I discuss below does indeed work, it's actually only necessary under certain conditions.
It turns out that the problem I describe in this article ONLY occurs if the event receiver is NOT registered *using app authentication*, e.g. If the RER is registered using *user authentication*, e.g.