in

SharePoint Blogs

The Best Place for SharePoint-related Blogs

in·for·ma·tion /ˌɪnfərˈmeɪʃən/ [in-fer-mey-shuhn]

"Knowledge is of two kinds. We know a subject ourselves, or we know where we can find information on it." -- Dr. Samuel Johnson [1709 - 1784]

"Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?" -- T. S. Eliot [1888 - 1965]

Connecting MOSS Version number in Word Documents

This one has been resurrected from the collection of post-crash blogs:

How is it possible to connect metadata/column information to Word documents stored in a WSS 3.0 library so that it is synchronised both ways??

Also referenced in the MS Office Word Team blog adding links between Word & MOSS metadata/columns is simple enough to do, but one thing appears to be missing....
Easily implemented for custom metadata and a few defaults, however 'Version' (as in the version number created by doc libs, both minor & major) doesn't seem to be available? Only Revision number which isn't the same. Or am I missing something?

Surely this is one of the more important columns that users may wish to include in a document header. How can this be added??

Finally, after trawling through endless forums & posts I find a blog by Joerg Sinemus describing exactly what I want to achieve. Though by no means a simple solution: http://blogs.msdn.com/joerg_sinemus/archive/2007/01/26/wss-version-number-in-the-word-2003-document.aspx

A great post, but surely there is an easier way to do this in MOSS / Word??

The bigger questions is perhaps: why on earth wasn't this feature included in the WSS 3.0/Word integration options by default??!!! After all, once a document is in library you can connect any custom metadata using the Quick Parts as well as some defaults. So why not Version?? it's possibly one of the most often used items in word headers.

So was this a serious lack of foresight on the part of the MOSS development team? or just too complicated to get into this release?

Comments

 

John Powell, PMP, MCPD, MCSD said:

July 23, 2007 10:18 AM
 

Links (7/23/2007) « Steve Pietrek’s SharePoint Stuff said:

Pingback from  Links (7/23/2007) « Steve Pietrek’s SharePoint Stuff

July 23, 2007 7:30 PM
 

Anna said:

Hi,

Above is a solution for Office 2003 client applications but what about Office 2007? Does anyone know of a way to solve this issue in Word 2007 templates?

Regards,

August 27, 2007 9:25 AM
 

Mark Attew said:

I am in the same boat here. I have templates into which I have inserted the Version Document Property and I want it to link up the version numbers SharePoint generates during check in and check out. Instead the version box is open and can be typed into while SharePoint keeps its version numbers seperate. Has any figured out how to link these in Word 2007/MOSS 2007?

September 18, 2008 5:51 PM
 

A Goodwin said:

Hi Mark,

We build a MOSS/WSS feature around custom content types. It replicated the SharePoint version number into the word documents stored in the library using Office 2007's mapped fields called 'Quick Parts'.

You can read more about features in these posts:

Creating a Custom Document Library Feature in WSS V3 / MOSS 2007  (www.sharepointblogs.com/.../creating-a-custom-document-library-feature-in-wss-v3-moss-2007.aspx)

Adding a Document Library Feature to a Site Definition in WSS V3 / MOSS 2007

(www.sharepointblogs.com/.../adding-a-document-library-feature-to-a-site-definition-in-wss-v3-moss-2007.aspx)

September 19, 2008 3:14 AM

Leave a Comment

(required )  
(optional )
(required )  
Add

Need SharePoint Training? Attend a SharePoint Bootcamp!

Posts (c) their respective authors. Everything else (c) 2007 SharePoint Experts