WSS version number in the Word 2003 document

re: WSS version number in the Word 2003 document

samwise_gamgee — Tue, 30 Jan 2007 04:20:13 GMT

Hi there,

Thank you for the helpful post. However -- I am wondering if you (or anyone else out there) could help me

with an issue I've been having lately with WSS 3.0. Here's a summary of my environment:

DEV ENVIRONMENT SUMMARY:

===================================================

"bare" WSS 3.0 RTM (RTW) running on W2k3 SP1

MOSS (ie. SPS) 2007 is NOT installed.

MAIN GOAL: Leverage WSS 3.0's versioning functionality for network communications management application.

Installation of Event handlers is via Object model, NOT by features.

PROBLEM SUMMARY:

===================================================

I have written classes to override the "ItemUpdated", and "ItemAdded" methods as shown in this article, as

well as trying to tap into other methods such as "ItemCheckedIn" "ItemDeleted" etc. I have successfully been

able to get the events to fire for simple tests.

Now, as I prepare to deploy my event handlers in a more commercial environment, I have been running

more rigorous tests, and have been getting very inconsistent behaviour with respect to the events

firing on document libraries:

The following WORKS:

-- a) If I trigger events via the SP Web UI

-- b) If I "SLOWLY" trigger events via the SP Object Model (ie. using SPFolder.Add(..) and SPFolder.Delete(..) methods)

By "SLOWLY" I mean that I artifically "sleep" for a few seconds between consecutive calls.

The following DOES NOT WORK (or works at best very inconsistently)

-- c) If I "QUICKLY" trigger events via the SP Object Model (ie. using SPFolder.Add(..) and SPFolder.Delete(..))

By "QUICKY" I mean that I remove all of my artificial sleeps and let the code in b) run normally.

The events sometime fire, sometimes not. On a document library of ten items, I may have ZERO events fire, or

I may get the events to fire only on the 1st, 3rd, and 8th item for example. It is, as far as I can tell,

rather random.

Has anyone else noticed such strange behaviour? I have searched and every example

I've come across usually focuses on very simple docLib events (triggered via the SP UI), and often do not

consider what would happen if MANY MANY events happen at once.

Though I feel the doclib events ins WSS 3.0 /SPS 2007 are a great enhancement from WSS 2.0

-- I am apprehensive to fully commit if the event model doesn't stand up well under high event loads?

Thanks in advance for any help you can provide.

re: WSS version number in the Word 2003 document

Joerg_Sinemus — Tue, 30 Jan 2007 22:56:38 GMT

The best way to get and give community support could be one of our newsgroup. Start here http://www.microsoft.com/technet/community/newsgroups/server/sharepoint.mspx

re: WSS version number in the Word 2003 document

agoodwin — Wed, 07 Feb 2007 17:46:21 GMT

Great post and this is exactly what I have been trying to achieve!

My big questions is: why the hell wasn't this feature included in the WSS/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 one of those items often used in word headers.

Serious lack of forsight on the part of the MOSS development team? or just too complicated to get into this release?(doubtful)

Connecting MOSS Version number in Word Documents

Wed, 07 Feb 2007 18:09:36 GMT

Finally my first blog post - I've been struggling to find something worthwhile to submit and I suppose...

re: WSS version number in the Word 2003 document

Joerg_Sinemus — Fri, 09 Feb 2007 22:32:19 GMT

The SharePoint product group knows this customer need now.

re: WSS version number in the Word 2003 document

frommi — Fri, 23 Feb 2007 12:47:06 GMT

I'm curious as to how steps 4 and 5 need to be performed.

[On a remote machine] I did create a .cs file with the code above and "compiled" it to a DLL using csc.exe. I copied the DLL to the Sharepoint server but gacutil wouldn't add it to the GAC, stating an "unknown error".

Are there any further steps need to be taken or did I miss something essential? Is there a little more step-by-step guiding howto on these to steps (compiling and adding to the gac) for this?

re: WSS version number in the Word 2003 document

Joerg_Sinemus — Tue, 27 Feb 2007 21:10:01 GMT

I created the DLL directly on the SharePoint Server due to some relationships (Use solutions in VS2005, *.SLN). The DLL should be in the GAC and not somewhere else.

For those questions like “how to” please refer to the MSDN and community support.

How to: Create a Simple Feature

http://msdn2.microsoft.com/en-us/library/ms475286.aspx

How to: Create an Event Handler Feature

http://msdn2.microsoft.com/en-us/library/ms453149.aspx

Last but not least refer also to the Visual Studio 2005 help/support/community.

Community support:

http://www.microsoft.com/technet/community/newsgroups/server/sharepoint.mspx

re: WSS version number in the Word 2003 document

mlh — Tue, 13 Mar 2007 18:22:47 GMT

Thanks very much for that post.

Is that feature required because of office 2003 usage or it is required too with office 2007 ?

Many thanks for the answer

re: WSS version number in the Word 2003 document

bome — Thu, 22 Mar 2007 15:58:47 GMT

The easiest way is to create a new column called WSSVersion in the document library. Set it up as a calculated column and add [Version] as formula. No coding needed.

re: WSS version number in the Word 2003 document

Joerg_Sinemus — Fri, 06 Apr 2007 15:06:54 GMT

The feature should work DOC's and is not fully tested to work with fully featured DOCX's.

The reason for the feature is because the calculated column works one time.

re: WSS version number in the Word 2003 document

jloving — Sun, 15 Apr 2007 04:56:35 GMT

I am also trying to use the [Version] field. How can I use feature to create a customized starting value for [Version]? This seems to be the closest I have come to finding an answer. Online for days with no such luck. Thank you in advance for any help you may provide.

re: WSS version number in the Word 2003 document

Homerhirn — Tue, 12 Jun 2007 13:26:19 GMT

Hopefully someone still watches at this post.

We need this feature 'cause we want to use MOSS to control our Doc-Version. I (hopefully) successfully implemented all the steps above, created the XMLs, the DLL, signed it on the Server and put it in the GAC and activated the feature (Took me a lot of time, cause I'm doing this the first time ever). First I made some mistakes, but I think I cleared them all out, but the feature still won't work (Already uninstalled the old versions and reinstalled the error-free-version).

I put a Field-Control in my template word document, name it "WSSVersion" and assign a value of 0.1 but when the version in the WSS-library is changed, the "0.1" in the document stays and won't update to the newer version number.

My Suspection is, that it has something to do with the elements.xml Do I have to change the following line from the example above with my Template-Owner GUID and ID or can I leave it just like in the example?

If I have to change it, how can I find out my GUID and ID?

I would be very reliefed, if someone can help me. I put a lot of time into this, and I'm starting to going crazy ;)

re: WSS version number in the Word 2003 document

Homerhirn — Wed, 13 Jun 2007 09:53:13 GMT

Hi there!

Never mind, I got it! Although in my eyes there is missing something very important in the article above: to create a column named "WSSVersion" in the doclib!

Correct me if I'm wrong, but this was the magic missing step.

re: WSS version number in the Word 2003 document

frommi — Mon, 25 Jun 2007 10:50:09 GMT

This works great with my Microsoft Office Word files, thanks!

I wonder whether this is also possible with Visio *.vsd files and Excel XLS files.

With Visio I cannot add the WSSVersion property - it's simply not available for selection. Is there a workaround?

re: WSS version number in the Word 2003 document

Joerg_Sinemus — Wed, 27 Jun 2007 16:55:45 GMT

It's good to know that this works for you in WinWord.

For any other Office document, XLS, VSD,... it could be straight forward. The properties we are talking about here are also available by the Explorer, the operating system explorer. That means navigate to the folder where the file exists and right-mouse-click properties. Here you can see/edit/add for a lot of known Office files the custom properties.

Sample:

- Create Word (DOC), Excel (XLS) and Viso (VSD) file, save it into a doclib where the column WSSVersion exists.

- Double check that the WSSVersion column has a value for all three documents

- Download the three files to your Desktop

- Check each file with right-mouse-click properties

You should see in all these three documents that there is a new property called WSSVersion and the value should be also there.

The next step will be how to get this value of the file-property WSSVersion into the sheet, drawing page… For that task please check with specialists in the particular area. With a briefly look it seems that you need VBA code for Excel and Visio.

Connecting MOSS Version number in Word Documents

Mon, 23 Jul 2007 12:19:52 GMT

This one has been resurrected from the collection of post-crash blogs: How is it possible to connect

re: WSS version number in the Word 2003 document

boverton — Tue, 18 Dec 2007 01:42:51 GMT

How would I implement to multiple specific lists?

"Save Conflict" Error when uploading files

Dirk_V — Thu, 27 Mar 2008 16:48:45 GMT

The suggested solution triggers a "Save Conflict" Error when attempting to upload files. Any suggestions how to remediate this problem?

Dirk

re: WSS version number in the Word 2003 document

nmanzi — Thu, 07 Aug 2008 08:18:21 GMT

I have developed a small sharepoint feature that will do this for 5 previous versions so the details can be put into a table inside the document.

http://nathanmanzi.com/?p=12

You'll need to compile it yourself and do some prep work to make it work though. A macro can be used to automatically update document fields whenever the document is opened.

re: WSS version number in the Word 2003 document

tomo123 — Fri, 07 Nov 2008 12:20:36 GMT

Here is a simple method of posting the version number into a word 2007 document using labels...

1. Create a document library and enable versioning (Either major or minor) and content types.

2. Add any new metadata fields to the library as required.

3. Add your content types.

4. Go into document library settings and select the first of your content types.

5. Select Information management policies settings from the content type menu.

6. Select define a policy and click ok.

7. Click on the 'Enable Label' Check box

8. DO NOT Check the other two boxes in the Labels section.

9. In the Lable Format field, enter the metadata fields in the following format...

Reference : {Reference} \n Version : {Version} \n Classification : {Classification} \n Custodian : {Custodian}

10. Set the label appearence and click on preview.

11. Click ok at the bottom of the page.

The next steps relate to Word 2007....

12. Go back to the library and create a new document using the content type you have modifed. The document should open in word

13. IMPORTANT : Save the file as a Word 2007 format now.

14. Select the insert tab

15. Select Quick Parts from the Ribbon menu and hover over document property

16. Select Label from the properties list

17. This should display the metadata defined in your label as a field in your word document. The field will update automatically when you next open the document.

18. Don't forget to save!

Finished

re: WSS version number in the Word 2003 document

dedhandi — Wed, 21 Jan 2009 20:27:06 GMT

My company is fairly new to WSS and we're just learning what it can do. We're also struggling towards ISO 9001:2008 accreditation and document versioning is an important factor. The problem is we don't have the programming knowhow or the time to implement our own solution or one that is too code heavy. I really like Bome's solution and got this to work partially (in that the bit in sharepoint worked). The problem comes when trying to insert the property in a Word document, where it doesn't exist. Is there a way to add it as a field code?