Itemupdating event receiver

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.

When dealing with event receivers in Share Point custom code, we use the Before Properties and After Properties to get a hash table of properties consisting of string/value pairs that correspond to fields in the SPItem object before and after the event occurred respectively.

Share Point has a built-in infrastructure that allows certain SP objects to raise events that can be handled by custom code.

Documents are only added or updated in this library from the Content Organizer via a custom Event Receiver/OOTB Approval Workflow combo on multiple Document Center Workspaces--which exist in their own Site Collections.

I've done my due diligence and followed recommendations here and here.

I’ve heard of people running into this issue a few times and it’s not all that obvious what the proper way is to do this.

To work around this issue, I implemented the following code: The code looks for the key (the Doc ID) in the property bag and if it is present, skip the creation of the task and remove the property from the bag.

You do want to make sure to call Enable Event Firing when you are done however.

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

I ran into an issue with an Event Receiver that was deployed to a Document Center Site library.

The requirement is pretty simple, when a document is added to the Documents library or an existing document is updated, create a task for someone to review the document's metadata.

Search for itemupdating event receiver:

itemupdating event receiver-14itemupdating event receiver-56itemupdating event receiver-40

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “itemupdating event receiver”