Tuesday, September 20, 2011

Utilize the Managed Metadata Service application tip #3 – Impact of message “Earlier versions of client programs might not support this type of column” on Document Library


As we discussed, the Managed Metadata Service application is one of the most important and interesting new service applications in SharePoint Server 2010.  However, there are many areas you need to be aware in order to utilize this service as we discussed before. This time, we will summarize concerns if you add metadata column to Document library list.

If you add a metadata column to a Document Library, you will see the following warning message.
Earlier versions of client programs might not support this type of column. Adding this column might block those programs from saving documents to this library.


 
You may consider what issues you might run into if we use metadata column for Document library. Well, there is limited issues and it only associated to files with Microsoft office 2007 version. Most of issues will be resolved for files with Microsoft office 2010 version. Here is the issue.

If you use “New Document” function on SharePoint Document list and you have Microsoft office 2007, you will get message as listed below and not able to check in document directly from Microsoft office if managed metadata is the REQUIRED field. 



The reason is exactly described in the message “Earlier versions of client programs might not support this type of column”. The earlier version of client is Microsoft 2007. As a result, the managed metadata column could not be populated from SharePoint side to Microsoft office client side as properties. If this managed metadata column is the required fiend, files could not be checked. Well, you could still see the file checked out from SharePoint UI and could update the managed metadata column directly from UI and checked in the file.  You could refer to other blog to see impact of the Microsoft Office 2003.

Yo will not have any issue if you are using Office 2010. However, if you have customized column such as department site column on the list, you will still have warning error message like below.



We had worked with Microsoft sine SharePoint 2007 and we Microsoft is not able to provide a final solution. So just be aware of the properties including metadata column associated with content. Please refer to other blog on managed metadata service.


Utilize the Managed Metadata Service application tip #1 - How to resolve "The required feature is not enabled for this column type" error 

Utilize the Managed Metadata Service application tip #2 - Metadata column not visible for users other than site collection administrators

Utilize the Managed Metadata Service application tip #3 – Impact of message “Earlier versions of client programs might not support this type of column” on Document Library

Utilize the Managed Metadata Service application tip #4 – How to workaround "Deletion of this user as a contributor failed" for local term store 

Utilize the Managed Metadata Service application tip #5 – Be aware of "Deletion of this user as a contributor failed" error on AD groups for local term store

Utilize the Managed Metadata Service application tip #6 – How to fix "The default termstore for this site cannot be identified " error

Utilize the Managed Metadata Service application tip #7 – How to read managed metadata column relationship 

Utilize the Managed Metadata Service application tip #8 - How to resolve error "This operation cannot be completed. The term store may be unavailable."


1 comment:

  1. it is really awesome to discover your site on the web as it really those ones who are just starting to explore the topic it outsource

    ReplyDelete