<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Missing Content Type fields in the Document Information Panel</title>
	<atom:link href="http://www.novolocus.com/2008/03/26/missing-content-type-fields-in-the-document-information-panel/feed" rel="self" type="application/rss+xml" />
	<link>http://www.novolocus.com/2008/03/26/missing-content-type-fields-in-the-document-information-panel/</link>
	<description>Whatever Andy Burns is working on...</description>
	<pubDate>Mon,  1 Dec 2008 21:18:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Adrian DeFazio</title>
		<link>http://www.novolocus.com/2008/03/26/missing-content-type-fields-in-the-document-information-panel/#comment-3632</link>
		<dc:creator>Adrian DeFazio</dc:creator>
		<pubDate>Thu, 30 Oct 2008 17:42:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/2008/03/26/missing-content-type-fields-in-the-document-information-panel/#comment-3632</guid>
		<description>Andy,

I don't know if you ever found a solution.  You can check this url: http://weblogs.asp.net/mnissen/archive/2008/10/18/sensible-document-template-file-management-with-sharepoint.aspx.  It's what I used in our case.</description>
		<content:encoded><![CDATA[<p>Andy,</p>
<p>I don&#8217;t know if you ever found a solution.  You can check this url: <a href="http://weblogs.asp.net/mnissen/archive/2008/10/18/sensible-document-template-file-management-with-sharepoint.aspx" rel="nofollow">http://weblogs.asp.net/mnissen/archive/2008/10/18/sensible-document-template-file-management-with-sharepoint.aspx</a>.  It&#8217;s what I used in our case.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.novolocus.com/2008/03/26/missing-content-type-fields-in-the-document-information-panel/#comment-1921</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Thu, 12 Jun 2008 23:38:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/2008/03/26/missing-content-type-fields-in-the-document-information-panel/#comment-1921</guid>
		<description>I'm having the exact same issue as you've described Adrian, with funny behaviour when my templates are associated by URL...

The templates are word documents, and they open up properly, but as soon as the user tries to save back to the document library it seems that SharePoint forgets which content type it is saving... instead it saves the document as the list's 'default' content type (which in this case is 'word document'). 

This issue goes away when my templates are uploaded directly to the content type, but the ability to maintain the templates in a document library and attach the URL instead is of high importance in this case.

Has anybody made progress on this issue? Thanks in advance.</description>
		<content:encoded><![CDATA[<p>I&#8217;m having the exact same issue as you&#8217;ve described Adrian, with funny behaviour when my templates are associated by URL&#8230;</p>
<p>The templates are word documents, and they open up properly, but as soon as the user tries to save back to the document library it seems that SharePoint forgets which content type it is saving&#8230; instead it saves the document as the list&#8217;s &#8216;default&#8217; content type (which in this case is &#8216;word document&#8217;). </p>
<p>This issue goes away when my templates are uploaded directly to the content type, but the ability to maintain the templates in a document library and attach the URL instead is of high importance in this case.</p>
<p>Has anybody made progress on this issue? Thanks in advance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: novolocus.com &#187; Document Conversion Service doesn&#8217;t map column data - Part I</title>
		<link>http://www.novolocus.com/2008/03/26/missing-content-type-fields-in-the-document-information-panel/#comment-1428</link>
		<dc:creator>novolocus.com &#187; Document Conversion Service doesn&#8217;t map column data - Part I</dc:creator>
		<pubDate>Tue, 08 Apr 2008 09:04:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/2008/03/26/missing-content-type-fields-in-the-document-information-panel/#comment-1428</guid>
		<description>[...] then just saved the template without making any changes - I&#8217;ve found that you need to do this to get the Document information panel to work [...]</description>
		<content:encoded><![CDATA[<p>[...] then just saved the template without making any changes - I&#8217;ve found that you need to do this to get the Document information panel to work [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian</title>
		<link>http://www.novolocus.com/2008/03/26/missing-content-type-fields-in-the-document-information-panel/#comment-1389</link>
		<dc:creator>Adrian</dc:creator>
		<pubDate>Fri, 28 Mar 2008 15:35:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/2008/03/26/missing-content-type-fields-in-the-document-information-panel/#comment-1389</guid>
		<description>One interesting note.  I added a column to my Document Center Document library where my templates reside.  I then went back to my Document Library that references that template within my Content TYpe.  I  created a new document of that content type and the DIP showed the new column I had added to the document library of my templates.  It seems to be using the metadata of the templates library?  Is this some kind of inheritance issue?</description>
		<content:encoded><![CDATA[<p>One interesting note.  I added a column to my Document Center Document library where my templates reside.  I then went back to my Document Library that references that template within my Content TYpe.  I  created a new document of that content type and the DIP showed the new column I had added to the document library of my templates.  It seems to be using the metadata of the templates library?  Is this some kind of inheritance issue?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://www.novolocus.com/2008/03/26/missing-content-type-fields-in-the-document-information-panel/#comment-1388</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Thu, 27 Mar 2008 17:03:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/2008/03/26/missing-content-type-fields-in-the-document-information-panel/#comment-1388</guid>
		<description>I think internally it must be a full URL, it's just not showing all of it. I tried that and got the same thing with the URL or filename being displayed, although I also wasn't actually able to replicate the original problem of making  fields not appear!

Still, I think it makes sense - for some reason my child content type must still have had the URL to the parent content type's template file.

Bit miffed that I couldn't replicate the problem though. Might try again tomorrow...</description>
		<content:encoded><![CDATA[<p>I think internally it must be a full URL, it&#8217;s just not showing all of it. I tried that and got the same thing with the URL or filename being displayed, although I also wasn&#8217;t actually able to replicate the original problem of making  fields not appear!</p>
<p>Still, I think it makes sense - for some reason my child content type must still have had the URL to the parent content type&#8217;s template file.</p>
<p>Bit miffed that I couldn&#8217;t replicate the problem though. Might try again tomorrow&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: novolocus.com &#187; What happens to content types when you add a column to a list in SharePoint?</title>
		<link>http://www.novolocus.com/2008/03/26/missing-content-type-fields-in-the-document-information-panel/#comment-1387</link>
		<dc:creator>novolocus.com &#187; What happens to content types when you add a column to a list in SharePoint?</dc:creator>
		<pubDate>Thu, 27 Mar 2008 14:14:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/2008/03/26/missing-content-type-fields-in-the-document-information-panel/#comment-1387</guid>
		<description>[...] This is sort of relevant to an earlier post on the Document Information Panel, and showing fields in it. [...]</description>
		<content:encoded><![CDATA[<p>[...] This is sort of relevant to an earlier post on the Document Information Panel, and showing fields in it. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian</title>
		<link>http://www.novolocus.com/2008/03/26/missing-content-type-fields-in-the-document-information-panel/#comment-1386</link>
		<dc:creator>Adrian</dc:creator>
		<pubDate>Thu, 27 Mar 2008 13:58:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/2008/03/26/missing-content-type-fields-in-the-document-information-panel/#comment-1386</guid>
		<description>That is an interesting question.  If you enter the URL of an existing document template, it becomes something like http://intranet/Docs/Templates/NotesTemplate.dotx.  However, when you use the Upload a new document template,  the URL of the newly uploaded template is just the file name (i.e. - NotesTemplate.dotx).  I'm not sure whether or not this is a bug or normal functionality.</description>
		<content:encoded><![CDATA[<p>That is an interesting question.  If you enter the URL of an existing document template, it becomes something like <a href="http://intranet/Docs/Templates/NotesTemplate.dotx" rel="nofollow">http://intranet/Docs/Templates/NotesTemplate.dotx</a>.  However, when you use the Upload a new document template,  the URL of the newly uploaded template is just the file name (i.e. - NotesTemplate.dotx).  I&#8217;m not sure whether or not this is a bug or normal functionality.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://www.novolocus.com/2008/03/26/missing-content-type-fields-in-the-document-information-panel/#comment-1385</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Thu, 27 Mar 2008 13:11:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/2008/03/26/missing-content-type-fields-in-the-document-information-panel/#comment-1385</guid>
		<description>Nope, I've gotta admit I've not tried using the URL of an existing template. It sounds like that URL field value might be the thing that was inherited by the child content type, and that the 'Upload a new document template' option overrides that. I might take a look to see. I don't suppose you happen to know what the URL to the existing template was and what the URL to the newly uploaded template became? That might tell us something.

I'll maybe take a look, and report back if I find anything...</description>
		<content:encoded><![CDATA[<p>Nope, I&#8217;ve gotta admit I&#8217;ve not tried using the URL of an existing template. It sounds like that URL field value might be the thing that was inherited by the child content type, and that the &#8216;Upload a new document template&#8217; option overrides that. I might take a look to see. I don&#8217;t suppose you happen to know what the URL to the existing template was and what the URL to the newly uploaded template became? That might tell us something.</p>
<p>I&#8217;ll maybe take a look, and report back if I find anything&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian</title>
		<link>http://www.novolocus.com/2008/03/26/missing-content-type-fields-in-the-document-information-panel/#comment-1384</link>
		<dc:creator>Adrian</dc:creator>
		<pubDate>Wed, 26 Mar 2008 14:42:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/2008/03/26/missing-content-type-fields-in-the-document-information-panel/#comment-1384</guid>
		<description>I've created my own content type.  I've specified my own template document in the advanced settings of the content type with the url of a template from a document library within my Document center site (I used the option: Enter the URL of an existing document template).  If I create a new document library with the content type it will open the appropriate template but the DIP reflects that of the Document content type, with the one metadata - title field.  If I use the other option in the advanced settings of the content type (Upload a new document template:), I get the appropriate metdata in my DIP.  Do you know why this is?  I would think referencing a template from a url would only provide the template for that content type and the document library would still use the metadata for that particular content type.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve created my own content type.  I&#8217;ve specified my own template document in the advanced settings of the content type with the url of a template from a document library within my Document center site (I used the option: Enter the URL of an existing document template).  If I create a new document library with the content type it will open the appropriate template but the DIP reflects that of the Document content type, with the one metadata - title field.  If I use the other option in the advanced settings of the content type (Upload a new document template:), I get the appropriate metdata in my DIP.  Do you know why this is?  I would think referencing a template from a url would only provide the template for that content type and the document library would still use the metadata for that particular content type.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
