Itemupdating properties afterproperties null dating halloween
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.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.But that option exists to be used, and some people really do need it.
So I fired up the debugger and noticed that the second property that I was trying to access returned null values in the Datasheet view even though it returned the valid objects in the Edit Form.
Scenario Overview: Custom event handler for a Share Point List with lots of columns.
The Item Updating logic needs to compare various dates and number fields to determine if the data could be submitted.
This is not either issue with Share Point or issue with Custom Code.
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.