{"id":1270,"date":"2012-01-17T00:00:00","date_gmt":"2012-01-17T00:00:00","guid":{"rendered":"https:\/\/test.simple-talk.com\/uncategorized\/managing-itemupdating-and-itemupdated-events-firing-twice-in-a-sharepoint-item-event-receiver\/"},"modified":"2021-05-11T15:56:24","modified_gmt":"2021-05-11T15:56:24","slug":"managing-itemupdating-and-itemupdated-events-firing-twice-in-a-sharepoint-item-event-receiver","status":"publish","type":"post","link":"https:\/\/www.red-gate.com\/simple-talk\/development\/dotnet-development\/managing-itemupdating-and-itemupdated-events-firing-twice-in-a-sharepoint-item-event-receiver\/","title":{"rendered":"Managing ItemUpdating and ItemUpdated Events Firing Twice in a SharePoint Item Event Receiver"},"content":{"rendered":"
\n

I’m usually disappointed when writers employ oft-overused metaphors to describe a situation. With that in mind, SharePoint 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. 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. We may never know about all of the dangers lurking out there, but today we’re going to cover at least one danger you may encounter while writing event receivers – an annoying issue with the ItemUpdating<\/strong> and ItemUpdated<\/strong> events firing twice. I should also point out that I know the difference between a metaphor and simile in case that was bothering you from the opening sentence. I am nothing if not a masterful linguist after a beer or two or more. <\/p>\n

What is an Item Event Receiver? <\/h2>\n

Hopefully you know about item event receiver if you are having problems with them firing twice. If not, kudos to you for tackling the object model with reckless abandon. Sometimes that is the most exciting way to learn, but for those less adventurous I will briefly cover the topic here. You can think of an item event receiver like a database trigger: it has different events that fire during the course of SharePoint running an operation on a list item (or document item). <\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n

Event Name<\/strong><\/p>\n<\/td>\n

\n

Synchronous<\/strong><\/p>\n<\/td>\n

\n

Description<\/strong><\/p>\n<\/td>\n<\/tr>\n

\n

Item Events<\/strong><\/p>\n<\/td>\n<\/tr>\n

\n

ItemAdding<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Runs before an item is added to the list.<\/p>\n<\/td>\n<\/tr>\n

\n

ItemAdded<\/p>\n<\/td>\n

 <\/td>\n\n

Runs after an item has been added to the list.<\/p>\n<\/td>\n<\/tr>\n

\n

ItemDeleting<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Runs before an item is deleted from the list.<\/p>\n<\/td>\n<\/tr>\n

\n

ItemDeleted<\/p>\n<\/td>\n

 <\/td>\n\n

Runs after an item has been deleted from the list.<\/p>\n<\/td>\n<\/tr>\n

\n

ItemUpdating<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Runs before an item is updated in the list.<\/p>\n<\/td>\n<\/tr>\n

\n

ItemUpdated<\/p>\n<\/td>\n

 <\/td>\n\n

Runs after an item has been updated in the list.<\/p>\n<\/td>\n<\/tr>\n

\n

Check-In Events<\/strong><\/p>\n<\/td>\n<\/tr>\n

\n

ItemCheckingIn<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Runs before an item is checked in.<\/p>\n<\/td>\n<\/tr>\n

\n

ItemCheckedIn<\/p>\n<\/td>\n

 <\/td>\n\n

Runs after an item has been checked in.<\/p>\n<\/td>\n<\/tr>\n

\n

ItemCheckingOut<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Runs before an item is checked out.<\/p>\n<\/td>\n<\/tr>\n

\n

ItemCheckedOut<\/p>\n<\/td>\n

 <\/td>\n\n

Runs after an item has been checked out.<\/p>\n<\/td>\n<\/tr>\n

\n

ItemUncheckingOut<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Runs before an item is un-checked out.<\/p>\n<\/td>\n<\/tr>\n

\n

ItemUncheckedOut<\/p>\n<\/td>\n

 <\/td>\n\n

Runs after an item has been un-checked out.<\/p>\n<\/td>\n<\/tr>\n

\n

File Events<\/strong><\/p>\n<\/td>\n<\/tr>\n

\n

ItemFileConverted<\/p>\n<\/td>\n

 <\/td>\n\n

Runs before a file in a doc library is converted to a different file type.<\/p>\n<\/td>\n<\/tr>\n

\n

ItemFileMoving<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Runs before a file is moved.<\/p>\n<\/td>\n<\/tr>\n

\n

ItemFileMoved<\/p>\n<\/td>\n

 <\/td>\n\n

Runs after a file has been moved.<\/p>\n<\/td>\n<\/tr>\n

\n

Attachment Events<\/strong><\/p>\n<\/td>\n<\/tr>\n

\n

ItemAttachmentAdding<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Runs before an attachment is added to an item.<\/p>\n<\/td>\n<\/tr>\n

\n

ItemAttachmentAdded<\/p>\n<\/td>\n

 <\/td>\n\n

Runs after an attachment has been added to an item.<\/p>\n<\/td>\n<\/tr>\n

\n

ItemAttachmentDeleting<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Runs before an attachment is deleted from an item.<\/p>\n<\/td>\n<\/tr>\n

\n

ItemAttachmentDeleting<\/p>\n<\/td>\n

 <\/td>\n\n

Runs after an attachment has been deleted from an item.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Item Event Receivers derive from the SPItemEventReceiver<\/a> class and have a number of methods that can be overridden to respond to various events: <\/p>\n

As you look through this list, you should notice that events have two types of endings: <\/p>\n

    \n
  1. Events ending in ING<\/strong>:\n