Sharepoint itemupdating event Family fun sexe webcam

posted by | Leave a comment

wrapping up a Share Point 2007 to 2010 migration with custom development including programmatically copying files and folders, custom Event Receivers, Web Parts, etc.Since the new setup uses a new AD domain, user accounts were mapped to new accounts and migrated using stsadm –o migrateuser.

While this approach works for deploying standalone site columns there are a few problems you might encounter: The first issue is to do with the fact that managed metadata columns rely on a second note field to function correctly.

A look at the Item Xml confirmed this: I didn’t want to script an update to all files (because that would trigger Event Receivers) so I avoided querying those properties directly and instead created an extension method to get those values through the SPList Item: There were a lot of Event Receivers in the custom solution so I didn’t take this path, mainly because I noticed in Share Point 2010 the SPList Item.

System Update() method will also trigger Event Receivers.

The library was configured with multiple Content Types, but the issue occurred only on some of them.

It appeared that for those Content Types, the Managed Metadata field was Optional, not Required.

Leave a Reply

wood harris dating