Office creates customxml for SharePoint 2007/2010 Content Type on save to doc library problem

Question

Hey All,

We have a product (an Office add-in) that adds custom document properties to office. There is a problem when saving these properties into SharePoint 2007/2010, in that Office creates the customxml to store the content type properties for SharePoint but does not map the custom properties into the customxml. We are looking for a way to catch the creation of the customxml for the Content Type properties and do the property mapping in our code. Any help would be appreciated.

Cheers,

Craig.

Answer 1

Hi Craig,
Thank you for posting. 
I will help you involve others to help you. There might be some delay about the response. Appreciate your patience.
Best Regards,

---

Bruce Song [MSFT]
MSDN Community Support | Feedback to us

Answer 2

Thanks Bruce. I looki forward to hearing your response.

Cheers,

Craig.

Answer 3

Maybe event receiver on content type can catch the creation of the customxml for the Content Type properties.

Answer 4

Hi Manish,

Good thought. We had been thinking of an event receiver on a document library, but didn't want to impact all libraries. We hadn't thought of Content Type event receivers. Is this possible in 2007 as well?

Cheers,

Craig.

Answer 5

Hi Manish,

I see that it works for 2007 as well. I'm having a little trouble finding out which event receivers are acceptable for Content Types. It looks like all of the list events can be caught with Content Type event receivers. Is there a good reference defining the set of event receivers that will fire when attached to Content Types and what the behaviour will be in each case?

Thanks,

Craig.

Answer 6

http://msdn.microsoft.com/en-us/library/gg749858.aspx

Event though above link is for SharePoint 2010 it will give you details. What events are available for content types.

Answer 7

Hi,

I have 2 subsequent questions about this:

1. Is it possible to fix this from within Office?
2. Is it possible to configure Office and/or SharePoint to not have this issue?

Cheers,

Craig.