I made sure to Disable Event Firing() before creating the task item.Regardless of what I tried, I really couldn't track down exactly why it was getting fired twice. And Item Updated gets called after the item is updated. Sequence = 5000; // put any number here sp Event Receiver Def. Item Updating gets called synchronously just before an item is updated.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.The problem is that the Item Updated event in this custom Event Receiver will fire twice under certain circumstances--such as having require document checkout set on the Documents library.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.On one list I have a workflow, which is changing columns in that list.
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.BTW : This Code isn't written in the itemadded method nor in the itemupdated method, actually it's the code in a user control for a webpart development. Developing a Sharepoint application would have all the fun of a video game, if only you had infinite lives.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.So when I edit an entry in that list, the Item Updated-Event fires two times.