<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.infopathdev.com:443/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>SharePoint Integration</title><link>https://www.infopathdev.com:443/forums/46.aspx</link><description> For questions concerning issues in the integration of SharePoint and Microsoft InfoPath.</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP3 (Build: 31118.962)</generator><item><title>Re: Common set of promoted properties for multiple InfoPath Forms in 1 Forms Library?</title><link>https://www.infopathdev.com:443/forums/thread/30015.aspx</link><pubDate>Wed, 02 Jul 2008 00:58:04 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:30015</guid><dc:creator>ChrisBacon</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/30015.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=46&amp;PostID=30015</wfw:commentRss><description>&lt;p&gt;With lots of help from Andrew May&amp;#39;s WebLog, I figured it out. Here are some links:&lt;/p&gt;&lt;p&gt;http://blogs.msdn.com/andrew_may/archive/2006/07/10/SharePointBeta2InfoPathFormsinContentTypes.aspx&lt;br /&gt;http://blogs.msdn.com/andrew_may/archive/2006/06/14/SharePointTermsColumnsFieldsProperties.aspx&lt;br /&gt;http://blogs.msdn.com/andrew_may/archive/2006/06/29/SharePointBeta2XMLDocumentParsers1.aspx&amp;nbsp; (#1 of 5)&lt;br /&gt;&lt;/p&gt;&lt;p&gt;My original form library was a mess, so I ended up deleting it and all the form content types so that I was starting from scratch. Then I did these steps:&lt;br /&gt;&lt;br /&gt;1. I realized I needed two form libraries, Case Forms and Admin Forms, each of which would need its own set of common promoted fields.&lt;br /&gt;&lt;br /&gt;2. Define all of the common fields as site columns.&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Site Actions | Site Settings | Galleries | Site Columns.&lt;br /&gt;&lt;br /&gt;3. Define a &amp;quot;Case Form&amp;quot; site content type with &amp;quot;Form&amp;quot; as its parent.&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Site Actions | Site Settings | Galleries | Site Content Types.&lt;br /&gt;&lt;br /&gt;4. Add the site columns you want to the &amp;quot;Case Form&amp;quot; content type.&lt;br /&gt;&lt;br /&gt;5. Define a &amp;quot;Admin Form&amp;quot; site content type with &amp;quot;Form&amp;quot; as its parent.&lt;br /&gt;&lt;br /&gt;6. Add the site columns you want to the &amp;quot;Admin Form&amp;quot; content type.&lt;br /&gt;&lt;br /&gt;7. For each InfoPath form template:&lt;br /&gt;&amp;nbsp;&amp;nbsp; a. Change the Data Connection to point to the appropriate Form Library.&lt;br /&gt;&amp;nbsp;&amp;nbsp; b. Remove all promoted fields (Tools | Form Options | Property Promotion).&lt;br /&gt;&amp;nbsp;&amp;nbsp; c. Save the form template.&lt;br /&gt;&amp;nbsp;&amp;nbsp; d. Publish the form template as a site content type.&lt;br /&gt;&amp;nbsp;&amp;nbsp; e. The first time you publish it, it will be a new content type.&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Make sure you select either &amp;quot;Case Form&amp;quot; or &amp;quot;Admin Form&amp;quot; as the&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; content type that you want to base the form template on.&lt;br /&gt;&amp;nbsp;&amp;nbsp; f. After the first time you publish, it will be an update of an existing type,&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; which is the previously published form template.&lt;br /&gt;&amp;nbsp;&amp;nbsp; g. For each form field you want to promote:&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Select the form field&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Select the appropriate site column that was created in step #2.&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Do not create a new list column! (That&amp;#39;s the mistake I made).&lt;br /&gt;&lt;br /&gt;That&amp;#39;s it. You can use the common columns to sort and filter the forms however you&amp;#39;d like.&lt;br /&gt;&lt;br /&gt;Chris&lt;br /&gt;&amp;nbsp;&lt;/p&gt;</description></item><item><title>Re: Common set of promoted properties for multiple InfoPath Forms in 1 Forms Library?</title><link>https://www.infopathdev.com:443/forums/thread/29899.aspx</link><pubDate>Sat, 28 Jun 2008 05:22:19 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:29899</guid><dc:creator>Clay Fox</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/29899.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=46&amp;PostID=29899</wfw:commentRss><description>&lt;p&gt;This is a problem when trying to share a document library.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;I think there may be a way to fix this but have not had to do it.&lt;/p&gt;
&lt;p&gt;Typically if you have a bunch of similar forms you should just have one super form then you would not have this issue.&lt;/p&gt;</description></item><item><title>Common set of promoted properties for multiple InfoPath Forms in 1 Forms Library?</title><link>https://www.infopathdev.com:443/forums/thread/29898.aspx</link><pubDate>Sat, 28 Jun 2008 00:18:35 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:29898</guid><dc:creator>ChrisBacon</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/29898.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=46&amp;PostID=29898</wfw:commentRss><description>&lt;p&gt;I have about 9 InfoPath 2007 forms (not browser-enable) that are submitted to the same SharePoint Server 2007 Forms Library. Each form has a set of promoted properties, including ones like Client Name and Client ID. The problem is that each property is added, so I end up with 9 Client Name properties and 9 Client ID ones, and of course I want only 1. Does anyone know of a way to do this?&lt;/p&gt;&lt;p&gt;I&amp;#39;ve considered setting up a Document Information Panel for each form, but I&amp;#39;m hoping there&amp;#39;s an easier approach.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Thanks,&lt;br /&gt;Chris&lt;br /&gt;&lt;br /&gt;&amp;nbsp;&lt;/p&gt;</description></item></channel></rss>