The second time they fire it is in response to the document being checked in.
It appears as though they are firing twice in this situation because Share Point is updating the properties on the document and then checking it in on the same request.
Save Conflict / Recursive call of event handler / Update item in item updating and adding Microsoft. SPException: Save Conflict Your changes conflict with those made concurrently by another user.
If you want your changes to be applied, click back in your Web browser, refresh the page, and resubmit your changes.
Next, let’s look at what happens when the user adds a document when the Require Check Out option is enabled.
The first time the Item Updating and Item Updated events fire it is in response to the document properties changing.
What I want to do is that in item added I want to update the list field. Enable Event Firing();//must enable event firing if we are disable ithopefully this post will help you guys for solving your problem.
So the net result of this is that the document is uploaded and the Item Adding and Item Added events have fired, which is pretty much what you would expect.Additionally, the properties parameter may not be populated with information that you would tend to expect to be present.One major thing you should know about the SPItem Event Receiver class is that while you can implement multiple list item event handlers in a single class, Share Point instantiates a new instance of that class for each individual event it needs to handle.I am looking for a solution where I can set the bit when field value changes in Item Updating.Check this bit if set do the processing in Item Updated.