the actual Add / Update operation for which the Adding / Updating event is being fired).Do NOT try to manually get the list item in code and update a property on it because the optimistic locking mechanism in Share Point may throw an error later on when the operation associated with the event to which you are responding attempts to complete.So the net result of this is that the document is uploaded and the Item Adding and Item Added events have fired, which is pretty much what you would expect.Next, let’s look at what happens when the user adds a document when the Require Check Out option is enabled.The first time the Item Updating and Item Updated events fire it is in response to the document properties changing.The second time they fire it is in response to the document being checked in.To prevent users from changing the name of the planet, you can develop a Item Updating event receiver.This event occurs before the data is saved to the Share Point list.
Remember that if you want to develop event receivers for specific lists, you will have to work with content types.
This walkthrough is based on the first one where I have a custom list with planets of our solar system.
Users can change data like the number of moons or the distance to the earth, but they are not able to change the name of the planet.
I’m Karine Bosch and currently I’m working as Share Point Solution Architect for Recomatics, a company located in Destelbergen near Ghent.
Previously I worked as a Premier Field Engineer for Share Point @ Microsoft Belgium.