Hi everyone. Anyone ever had trouble with document properties that does not syncronize between a Word 2007 document and the SharePoint library where it is stored? I have a SharePoint library, that contains two content types. When I upload a pdf file, and set the property values everything is perfect. When I create a Word document and set the Properties using the DIP, the values are stored in the Word document (I see them in the DIP, inside the word xml files and in the fileds in the document where they are displayed (using quickparts)), but not transfered to SharePoint when I save the document to the library. If I upload a Word document to the library, I am able to choose content type and set all the property values. But when I open the document for editing, all the property values in the DIP are empty. The DIP do show the correct property fields for that content type. After creating new libraries, content types and creating, transfering and uploading files all day, I have not been able to locate what is causing this issue. My users have been using this library for several months and use the documents on a daily basis, and this problem just got raised. My users are feeling scared that they have to recreate their library or site (which will involve manually updating all the document properties ). I hope someone are able to help me out here, as my users are loosing confidence in SharePoint as a collaboration platform and a safe for their documents... Enviroment: - SharePoint 2007 Enterprise, SP1 - Windows XP, SP3 - Office 2007, SP2 No custom coding/features involved. All out of the box features. Thanks for any help.

Hi, No, I have only seen this type of behaviour when using Word 2003...Would you like to asetup a LiveMeeting so that you can show me what is happening? Please let me know when you want to set one up and I will Schedule or setup a MeetNow LiveMeeting.... -Ivan Ivan Sanders My LinkedIn Profile, My Blog, @iasanders.

This is similar to this question: http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/1ee4a29f-a7fb-4152-b6a6-bb07ae43811e I think I’ve discovered a bizarre bug when uploading a Word Doc to a SharePoint library While on site I confirmed following: Win 7, Office 2007 - Comments field does not get captured. Win 7, Office 2010 - Comments field does not get captured. Win XP, Office 2007 - Comments field does get captured. I tested with the Document properties field Keyword and it synced into a SharePoint column. On the library (test) I deleted the Comments field and recreated it with an already existing Site Column field and it worked!!!!! This worked in multiple test libraries. So it appears that the solution is that if you delete the Library multiple text Comments field in a Shared Documents library and replace it with already existing Site Column Comments field, SharePoint and Word fields sync with XP/Win 7 with Word 2007/2010. Could it really be possible that the comments field in the Doc Libraries is corrupt with Win 7? Never heard of this. Any thought?

Hi All, It may go deeper depending on the file type.. If youare using the oder DOC file type and or Office 2003 Suite.. Steve Curan has a great article on the issue http://vspug.com/smc750/2008/02/26/office-2003-files-are-second-class-citizens-in-sharepoint-2007/ also a few other things to take into account Pauls article explains how he was able to resolve the issue http://www.endusersharepoint.com/2009/09/10/missing-metadata-with-office-2003-%E2%80%93-yet-another-%E2%80%9Cduh%E2%80%9D-moment%E2%80%A6/ Personally, there have been a couple of times I would have loved to blame SharePoint CTypes, maybe it really was the servers fault.... All in All I have been able to successfully migrate hundreds of terabytes and update metadata using various thrird party and self developed tool sets where the clients used the DOC File Type and I have had others insist we change the File Type to DOCX... DOCX is the way to go if you have a choice... If you are already using the DOCX File Type, then what are your publishing, version control, and editing rules??? The Offer for a Live Meeting is still open, I would enjoy seeing the issue using a DOCX file type and helping you to resolve it, please do not hesitate. Peter I am not sure why you would create a column with the same name as one that exists and is included in Word as a default? Any time you attempt to over write a default value you may have issues. I specifically create Site Columns only when they do not already exist and ensure they have unique names... -Ivan Ivan Sanders My LinkedIn Profile, My Blog, @iasanders.

Ivan, Thanks for the reply. There's no version control set, or editing rules in the doc Library. The document saved into a Lib. process is as follows: 1. They are first saved on the network drive 2. Uploaded then uploaded into the SharePoint lib. It's at this point that the meta data from Word is synced with the SharePoint columns. This is why the SP lib. column names need to match Word properties. ------- wwww.wardpeter.com

Hi, I am also experiencing this issue and have reproduced it on Windows XP as well as Windows 7, suing Sharepoint 2007 and Office 2007. I have a document library with custom column called "TARDIS Notes" that is configured to be a multi line text box. I can edit the Sharepoint property and the Word document property independently, with no syncing either way. All other properties, none of which are multi line texts, sync fine. Happy to use live meeting to demonstrate this issue, since it is causing us real problems. Regards, Matt BBC Worldwide.