It seems that by adding a new MMS column the issues with the other columns is corrected, we believe this might be due to some version or synchronisation process but have not tracked down the root cause. The value in Word is maintained in the document’s xml fields but is not correctly udpated (at least in our tests) with the correct namespace for the term or termID.
It appears that in some cases the document Parser process fails on MMS values. Not known at this time, it appears to be related to the document parser. Note that you will need to test and re-create any faulty Site Templates. You can confirm that this fixes your issue by performing a manual update of a single list and then run a bulk correction using PowerShell. Solution:Īdd and remove a MMS column from each list. This has also been seen with Harmon.ie where it is impossible to set the MMS value, it is probable other systems may be effected. The main example is in office, at least word and Excel. We’ve seen it in at least two SharePoint 2010 SP1 environments in the last week, with farms using varying CUs.
Note: If text, choice or other non MMS fields are not being synced when you save the document then this is probably unrelated to your issue. In summary: SharePoint can write to the office document but MMS values in the document cannot be written to SharePoint by office. However as normal any changes to the values in SharePoint will be pushed down to the office document overwriting any values in the DIP. If you close and re-open the office document, even from another computer, any changes made in office to the MMS values will still remain as you set them in the DIP. Single Line of Text, Choice, Number etc.) are correctly synced. When these values are changed in an office document however these MMS column changes are not updated in the SharePoint item. When you set a Managed Metadata Service (MMS) column in SharePoint these values are pushed down to the office document and will be visible on the Document Information Panel (DIP). This issue seems to be cropping up a lot at the moment, one possible fix is below.
0 kommentar(er)
