Fired event itemupdating which wasn t iran arbuda dating

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 my first post in 2013, here I just want to discuss about Event Receivers in Share Point 2010 (SPItem Event Receiver class) and an important factor with the Event Receivers.

Let me start with “What is an Item Event Receiver”Item Event receivers in Microsoft Share Point 2010 enable your custom code to respond when specific actions occur on a Share Point List Item.

If you follow the link he uses you'll see the table for lists he uses is different from the one he references. I use these rules of thumb not to have to look at that post all the time: So if you want to test if a specific column was changed you have to use the Item Updating instead of the Item Updated eventreceiver. Is there a reason why do you want to use the Item Updated receiver specifically? Do you absolutely need to do something Asynchronous? If so, indeed the best way to do it is to add a hidden bit column, or an int column if you want to cheaply store changed flags for several columns.

Leave a Reply