Version and ID in printed document

As you probably already know it’s possible to add Quick Parts in Word to add metadata from custom columns in your header/footer.
But getting Version or ID in the header/footer is a whole other bargain.

It’s really important to get this information inside the document, so that it’s possible to see on a printed copy, what version it is compared to the latest version in SharePoint.

So how should we accomplish this?

• Make sure you have a document with a header section.
• Create a Content type and add this document as the template.
• Navigate to a document library and activate Versioning and the possibility to handle Content types.
• Add your Content type to the library.
• Navigate to the settings for the library and then the settings for the Content type. Click on “Information management policy settings”.
• Check “Enable Labels” and add: {Version}nDok.ID: {ID} in “Label format”. Make changes regarding the style as it fits you.
• In advanced settings for the Content type, choose to edit the template.
• Put the cursor where you want to have the Version and ID added.
• Click on Insert, Quick Parts, Document property and Label.
• Save, click Ok and try it out.

The first time you open up the document it looks a little bit strange because there is no version yet, but don’t worry, save and open the document again and behold the version.

/Niax


Custom Meeting workspace site template

In a project I recently worked in I found out the hard way that it wasn’t possible to save a Meeting workspace (MW) as a custom template to recreate sites from. I also found out through Bing that I wasn’t alone in my discovery 🙂

The other day I was discussing this with a colleague and by reproducing it I wanted to show him that the left navigation on the site between the different meetings would crack.

So I saved a MW as a new template and from that template I created a new MW from a calendar event. Then I created another calendar event and linked to the same MW. Navigating to the MW I could now see the two dates in the left nav. And do you know what? It worked!

I could actually navigate between the two dates! This has never worked before!

So why does it suddenly work? SP1 for SharePoint 2010 🙂

My colleague who did not have SP1 installed, doing the same thing in his dev environment, got the old behavior, left navigation cracked. After installing SP1 he didn’t have the problem any longer.

Isn’t that great? When SP1 was released I actually went through the Excel file with all the fixes and couldn’t find anything about this. I wish it could have been mentioned, it would have saved me and the client a lot of time.

Another thing to be aware of when you have meeting workspaces in a site collection and you for that site collection, wants to push out a custom master page on all sub sites. If you do that, the MWs will also be getting your custom master page. As you already might know, MWs have their own master page.

The result you will get by doing this is that (again) the left navigation will crack. You will get a JavaScript error telling you that a property bag is missing.

To fix this you will have to add this into your custom master page.

At the top add this Tagprefix:

<%@ Register Tagprefix=”Meetings” Namespace=”Microsoft.SharePoint.Meetings” Assembly=”Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” %>
Below the FORM-tag below the BODY-tag add:

<Meetings:PropertyBag runat=”server”/>

There is one more thing to add to this. In a MW there are two more options in the Site Actions menu.

“Add Pages” and “Manage Pages”. These two options will also be lost when you apply another master page than the default for a MW. I don’t have a solution for how to handle that as for now. But some how I think it’s needed to make the Site Actions menu dynamic and show these options only if the site is created from a MW template.

/Niax