<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Acuff Group &#187; sharepoint designer</title>
	<atom:link href="http://www.acuffgroup.com/tag/sharepoint-designer/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.acuffgroup.com</link>
	<description>Vision - Strategy - Execution</description>
	<lastBuildDate>Tue, 20 Oct 2009 16:46:38 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Tip for publishing an InfoPath form to a SharePoint library</title>
		<link>http://www.acuffgroup.com/2009/01/21/tip-for-publishing-infopath-form-to-sharepoint-library/</link>
		<comments>http://www.acuffgroup.com/2009/01/21/tip-for-publishing-infopath-form-to-sharepoint-library/#comments</comments>
		<pubDate>Wed, 21 Jan 2009 18:22:20 +0000</pubDate>
		<dc:creator>Noble</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[infopath]]></category>
		<category><![CDATA[sharepoint]]></category>
		<category><![CDATA[sharepoint designer]]></category>

		<guid isPermaLink="false">http://acuffgroup.com/?p=21</guid>
		<description><![CDATA[One of our clients is doing a lot of development work with SharePoint, InfoPath, and SharePoint Designer workflows. We were running into an issue where publishing the form to SharePoint often failed, resulting in an error: &#8220;Updating content type failed&#8221;. After extensive google&#8217;ing it appears that a lot of other developers have run into this, [...]]]></description>
			<content:encoded><![CDATA[<p>One of our clients is doing a lot of development work with SharePoint, InfoPath, and SharePoint Designer workflows. We were running into an issue where publishing the form to SharePoint often failed, resulting in an error: &#8220;Updating content type failed&#8221;. After extensive google&#8217;ing it appears that a lot of other developers have run into this, but we couldn&#8217;t find a fix for it. A good friend came through last night with a great idea that seems to have solved the problem.</p>
<p>Symptoms:</p>
<ul>
<li>InfoPath form with ~150 data elements</li>
<li>About 60 of the elements need to be attached to the SharePoint library</li>
<li>We were promoting the columns to the library, and on publishing ran into failures about 90% of the time</li>
</ul>
<p>Our best hypothesis is that the web service on the SharePoint server was timing out before the publish operation could complete. However, once we changed the way we&#8217;re publishing the problem seems to have gone away completely. The fix is to ensure all of the &#8220;linked&#8221; columns already exist in the form library, then tell InfoPath to attach to those columns, not create new ones. You can do this during the publish wizard process:</p>
<ol>
<li>Click the File -&gt; Publish&#8230; menu option</li>
<li>Select the first option &#8220;To a SharePoint server&#8230;&#8221;</li>
<li>On the next screen include the proper URL to the library</li>
<li>On the third screen select &#8220;Document Library&#8221;</li>
<li>On the fourth screen select &#8220;Update the form template in an existing library&#8221; and choose the library from the list</li>
<li>On the fifth screen you&#8217;ll have the option to add your columns. When you click the &#8220;Add&#8221; button, instead of opting to have InfoPath create the column for you (i.e. the &#8220;None: Creat the new column&#8230;&#8221; option), select the &#8220;This document library&#8221; option from the first drop-down, then select the appropriate column name from the second drop-down box</li>
</ol>
<p>This seems to have completely corrected the &#8220;Updating content type failed&#8221; error we were having and appears to have cleared up several other issues. When our publish failed, we were losing all of the views, etc. which makes sense, as InfoPath was re-creating the columns. We were also seeing fields become un-linked in the SP Designer workflow. Presumably this will fix all of the issues and save us an incredible amount of time moving forward. Hopefully this tip helps you, and please leave comments for others if you can add any insight.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.acuffgroup.com/2009/01/21/tip-for-publishing-infopath-form-to-sharepoint-library/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
