There is a little puzzlement among Asynchronousand Synchronous events, however I believe after reading this article, there will be no place for confusion in your brain, the reason for that I go behind a childlike practice to memorize The same babyish method, I want to share with you.A for Apple, A for Asynchronous and A for After events, so all Asynchronous events occur after the event, which does not stop the code to execute.The List Instance made from this list definition is a Hidden List (Not sure if this can be issue) Following is file for Event Receiver: What have I confirmed/tried? Confirmed that Custom List Definition List Template is "10101" .Confirmed that the Event Receiver is deployed and feature is activated .All Synchronous events end with ‘ing’ letters like Site Deleting, Field Adding, Item Adding etc.SPWeb Event Receiver Asynchronous Events Share Point Foundation 2010 New Events Microsoft added several new events to Share Point Foundation 2010 on Site, List and Item level.There is custom list definition and I have attached an event receiver on Item Updating of list instances from the custom list definition.
For example I have a column for approve/not approve and I want that to be the trigger not the other values in the item.
How I solved it Googleing this helped me not one bit and my first solution was something I would like to hide at the bottom of some server (I don’t want to talk about it, let’s just say it had something to do with counting the seconds since the last update).
At your disposal on SPRemote Event Properties you have after Properties and before Properties, found by doing this: And those were the key to the problem: how to act on the firing only when the user changes something and not when it updates itself?
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.