Itemupdating firing 2 times
Policy documents, Functional Specs, Technical Specs, Time Sheets, Work-Orders etc.Custom Content types help us with defining the data-structure while layouts help us define the presentation.
After adding "List Added Event Handler" to our Share Point 2010 feature to update the list properties after listed created, we run into major issue during any list or document library creation by choosing below templates. SPException: Save Conflict Your changes conflict with those made concurrently by another user.Okay fine, workflows are still out of box, what are we doing new in that? Imagine what would happen after a document (like our Functional Spec) is approved? Until the document is approved again it would no longer be in ‘Published’ state.To view the previous state would be slightly messy.In SP 2010, workflows have been made pretty obvious.In fact our custom Pages will not be visible to everyone if we don’t actually publish them and the only way to do that is to start the approval workflow. Ten days into development new requirements would come in and the spec would have to be re-visited and re-routed for approval.
Search for itemupdating firing 2 times:
If we look at our example of creating a custom Content Type for “Functional Specifications”, we could extrapolate it to many different types of documents typically used in an enterprise, e.g.