In itemupdating

Unfortunately, that makes your project like the Titanic.

I don’t mean that it’s largest and most luxurious application every written, but rather that you may be cruising headlong into a nasty rendezvous with an iceberg that could deal a severe blow to your project.

SPField Lookup Value old Lookup Value = new SPField Lookup Value(properties. To String()); SPField Lookup Value new Lookup Value = new SPField Lookup Value(properties.

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.

Developing a Sharepoint application would have all the fun of a video game, if only you had infinite lives.

(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?

With the exception of feature events, here is a full list of available Share Point events, event receivers, and event hosts for quick reference.

There is a difference between the behaviour of Before and After properties when dealing with document libraries versus when dealing with lists.I’m usually disappointed when writers employ oft-overused metaphors to describe a situation.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.After Properties["Email"] will be NULL in the event receiver code. After Properties will have the correct value, only when Email is also updated through code. Before Properties and After Properties are available for the different event receiver classes.

Tags: , ,