If you've created document libraries before, you probably noticed the selection of a document type that is made in the last field, the Document Template field, on the creation form e.g.
The default is "Microsoft Office Word document".
Now you have your brand new document library and you decide to update the template. But how would you accomplish such a feat? This is where the Explorer View comes into play. The template is nothing more than a Word document, or whatever other type of document was specified.
UPDATE THE TEMPLATE
Navigate to your target document library.
Notice how we don't have any visible folders in this library. The key here being "visible". In the "Select a View" menu pane on the left, click the "Explorer View" option.
You should now see a "Forms" folder in the viewing pane on the right. This folder is only visible in Explorer View. Double click the "Forms" folder to open it.
You should see 5 .aspx pages and a template file named "template.doc" in the viewer pane. The extension of the template file depends on the default document type that was selected during document library creation. In this case, the default option for Word document was used so the template file is called "template.doc". If an Excel document default was selected during library creation, the template file would be called "template.xls" as you can see below.
To update the template, simply double click the "template.doc" file to open it. Edit the document until you are happy with the template and the save it, overwriting the version in the "Forms" library and thus updating your template for the given document library.
The question now become, what if you already have your template document? How do you get its content into the library template file? You could edit the library template file and do a copy and paste, but that would not be the best method to use. You would think that clicking the "Upload Document" button would allow you to upload your template replacement document to the "Forms" folder, but you'd be mistaken. All that would accomplish is to upload the document to the document library itself while the template document remains untouched. The easiest way is to use hotkeys…
OVERWRITE THE TEMPLATE WITH A PRE-EXISTING FILE
Navigate to the document library's Explorer View as previously described.
Open Windows Explorer.
Navigate to the folder in which your replacement template document is located.
Select the replacement template document.
Copy the document.
TIP: You could use right click menus here, but in WSS you'll get a bunch of annoying warning dialogs so it's best to just use the Ctrl+C and Ctrl+V hotkeys instead.
Go back to the document library Explorer View window and click anywhere in the viewing pane to set focus to it.
Paste the replacement template document. You will be prompted to confirm that you wish to overwrite the existing template document.
Click "Yes" to overwrite the template.
That brings up another question. What if I want to completely change the template type of the library? Say I want to change the library from a Word template to an Excel template. Would I just delete the "template.doc" and replace it with "template.xls"? The answer is not that simple. WSS stores it's link to the library template so you need to update that before your change would take effect.
CHANGE TEMPLATE TYPE
Upload your new template document as described above in the overwrite directions. The notable difference would be that you won't be prompted to confirm the overwrite of the template document because your new document would have a different extension. Upon completion, you will have two template documents.
If you attempted to create a new document at this point, WSS will still generate a Word document. To remedy this, click the "Modify settings and columns" link in the left hand navigation pane.
Under the "General Settings" section, click the "Change general settings" link.
Scroll to the bottom of the page and in the "Document Template" option, note the Template URL.
Modify this value to reflect the name of your new document template e.g. "template.xls" in our case.
Click the "OK" button to commit the change. Now if you navigate back to the library and click the "New Document" button, it will create an Excel document from your template.
That brings us to one last point to note. You can have multiple document templates in the "Forms" library and can switch from time to time between these template as you wish but each library can only have one active template at a time. WSS 3.0 solves this with document type definitions but that's a story for another blog post.
One more thing to note is that WSS is intellengent enough to tie the document template file in the "Forms" folder to the "Document Template" setting for the library. That means that if you rename the document in the "Forms" library say from "template.doc" to "mytemplate.doc", WSS will automatically update the library setting to keep pointing to that document template file. That also means that if you were to delete the document template file, WSS would remove the template setting completely from the library thus having no default and NO, before you ask… it does NOT update the setting when you upload a new template file AFTER deleting the original template file. My advice is to just overwrite the template file instead…
If you have a highly customized SPS portal, especially if you've created and defined your own portal are templates, you will definitely have problems upgrading to MOSS.
Stay tuned. I will post a series on the work around I had to use to get our portal to upgrade to MOSS successfully within the next week or so…
OK, so I'm working on my computer and am heavily in process with about 12 windows and application open when what do I see?
What the heck is that all about?
Couldn't Windows Update detect that I'm busy using my system and NOT prompt me until my usage level drops?
With the timer counting down only a meager 5 minutes, if I step away from my desk, I could come back to a forcefully rebooted machine.
That's not good.
So I started wondering what the cause could be.
I checked my Automatic Updates and THAT's where I found the problem.
As you can see, I have my updates set to "Automatic".
That's OK because I did that intentionally because I wanted my machine to update at night when I'm sleeping.
The problem is that I had set it up to update around midnight… or so I thought.
You can see that I have it set for NOON instead. Doh! J Don't I feel like Homer…
Changing this setting should get me the desired result of doing the updates at night.
Born and raised in South Africa during the 70's I got my start in computers when a game on my Sinclair ZX Spectrum crashed, revealing it's BASIC source code. The ZX had a whopping 48K of memory which was considered to be a lot in the Commodore Vic20 era, but more importantly, it had BASIC built into the soft touch keyboard. Teaching myself to program, I coded my first commercial application at age 15.
After graduating high school at 17, I joined the South African Air Force, graduating the Academy and becoming a Pilot with the rank of First Lieutenant by age 20. After serving my country for six years, I made my way back into computer software.
Continuing my education, I graduated Suma Cum Laude from the Computer Training Institute before joining First National Bank where my work won the Smithsonian Award for Technological Innovation in the field of Banking and Insurance. Soon I met Will Coleman from Amdahl SA, who introduced me to a little known programming language named Huron/ObjectStar. As fate would have it, this unknown language and Y2K brought me to the USA in 1998.
I got involved with SharePoint after playing around with the Beta for SharePoint Portal Server 2003. Leaving my career at Rexnord to become a consultant in 2004, I was first awarded the Microsoft Most Valuable Professional Award for SharePoint in 2005, becoming only the 9th MVP for WSS at the time. I fulfilled a life long dream by pledging allegiance to the Flag as a US citizen in 2006. I met the love of my life and became a private consultant in 2008. I was honored to receive my ninth MVP award for SharePoint Server in 2013.