Timeline for Handling ItemUpdating event receiver firing more than once
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 6, 2014 at 9:27 | vote | accept | variable | ||
| Aug 6, 2014 at 8:00 | comment | added | Robert Lindgren | The one you talk about first (check-in / check-out), it's quite clear in my post I think | |
| Aug 6, 2014 at 7:59 | comment | added | variable | Robert, what did you mean in your answer by "The other scenario is tougher", which scenario? | |
| Aug 6, 2014 at 7:52 | comment | added | Robert Lindgren | You really should not add more questions to a question after receiver answers (it could mean the existing answers looks strange if oyu know what I mean). But yes, you can use the EventFiringEnabled in ItemUpdated to, but you can not use AfterProperties (since the item is already updated when this event i triggered) | |
| Aug 6, 2014 at 7:50 | comment | added | variable | Is this also applicable to item-updated events? | |
| Aug 6, 2014 at 7:38 | history | edited | Robert Lindgren | CC BY-SA 3.0 | added 52 characters in body |
| Aug 6, 2014 at 7:11 | history | answered | Robert Lindgren | CC BY-SA 3.0 |