The changed values can be retrieved from the After Properties of the incoming properties argument.
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.
You can also use event receivers to validate the data that the user wants to change.
This walkthrough is based on the first one where I have a custom list with planets of our solar system.
This event occurs before the data is saved to the Share Point list.
To check if the name of the planet is changed, you can compare the Title column before the changes with the Title of the changed item.
Together with Patrick we developed the alfa and beta versions of the Silverlight Blue Print for Share Point which contains several samples on how to integrate Silverlight with Share Point. I’m also board member of the belgian user group BIWUG.
And proud MEET member If you don’t find the answers to your questions on this blog, you can always post your questions to the Share Point 2010 forum or the Share Point 2013 forum.
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?
By comparing the values in the before Properties with the after Properties I could see if they contained a difference.
The initialization of the event receiver looks like this: And all was fine in the world.
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.