In itemupdating event 5 dating lessons learned my sisters
Share Point as most us know, has built in workflow capabilities.
In SP 2010, workflows have been made pretty obvious.
Custom Content types help us with defining the data-structure while layouts help us define the presentation.
What if these documents were to require review and approval?
Every time an item was added to the custom list, the event was firing twice.For instance in this demo we are assuming a hypothetical business requirement demanding “”.In order to showcase this validation scenario we can consider the same Item as mentioned above.As with any problem, I always try to resolve it through the process of elimination by first isolating the core issue into a test project and therefore out of the primary project I’m experiencing it in because sometimes you can’t see the forest because of the trees. After creating the simple project, the problem was still there. The event wasn’t firing twice for the same list, it was firing for ALL Lists. I took another look at my event receiver I had added via Visual Studio to the project. Yes, I had left the file for the Event Receiver there, and therefore when the feature was activated for the project, the receiver got associated to ALL lists on the site.Even a simple app to enumerate the event receivers associated to the list only showed the one instance. Well, I had moved on to other things again, when all of a sudden, I noticed that new tasks were being created in the task list for some documents that I was uploading to a different document library. That’s pretty much the symptom for a receiver associated to a list template, but this was NOT a list template! It wasn’t going to show up in the Event Receivers collection for that list instance, because it was associated to the list type.
When I added it to the list instance, it just caused the event to fire twice on THAT list.