An advantage of using Item Updating to set field values is that the values will be visible to the user after they submit their changes in a non-datasheet view.Because Item Updated is asynchronous, the user may not see their new values when they see the list after submitting the edit.First, we declare a boolean to hold the original value of the Event Firing Enabled property.Now, in our constructor we save off the Event Firing Enabled value, then set it to false.(no updates required since you are changing the value before it gets saved) I would verify that your Event Receiver is attached to the list.Are you able to debug your Event Receiver when you modify an item in the list? It appears no matter what you do to the after properties it doesn't change anything It is nice to update Title in Item Adding and Item Updating events since extra Updates are avoided (without Disable Event Firing), and the "Edit Properties view" will already have the Title filled in Some code example to update title based on filename. For working with Title in Lists, ["Title"] needs to be used. In Item Updating event, I want to do the processing, if value changes.
property is set to "Update".) This enables you to perform a custom routine whenever this event occurs, such as canceling the update operation. The processing includes few jobs and sending e-mails after completion. I cann't do comparision here because before properties does not provide old values in the list item.//the list item you want to update (typically SPItem Event Properties.List Item in an event receiver SPList Item special Item = list. Properties["some_persisted_key"] = "Some Value here"; special Item.