<?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: Promote Form Fields to Column names for Multiple forms to one library</title><link>https://www.infopathdev.com:443/forums/thread/90217.aspx</link><pubDate>Wed, 29 May 2013 12:40:42 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:90217</guid><dc:creator>ErnestoM</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/90217.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=46&amp;PostID=90217</wfw:commentRss><description>&lt;p&gt;Hi-&lt;/p&gt;&lt;p&gt;I think this is a problem you&amp;#39;ll encounter whenever there are multiple content types in a single form library. Since each form is different, each XSN will have its own set of promoter properties and I can see where if you have 10 forms in one form library managing the columns / promoted properties can become unwieldy. Sadly, there&amp;#39;s&amp;nbsp;no command in qRules to help with this scenario. &lt;/p&gt;&lt;p&gt;May I suggest giving this a shot in a simpler scenario? That is, create a test form library, admin deploy a few forms (the forms&amp;nbsp;can be simple, no qRules), and start adding them (one by one) as content types. Maybe going thru that easy scenario first will&amp;nbsp;provide insight into the more complex scenario with 10 forms.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;</description></item><item><title>Promote Form Fields to Column names for Multiple forms to one library</title><link>https://www.infopathdev.com:443/forums/thread/90208.aspx</link><pubDate>Wed, 29 May 2013 07:58:14 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:90208</guid><dc:creator>MrWilde</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/90208.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=46&amp;PostID=90208</wfw:commentRss><description>&lt;p&gt;Sorry I know that must sound complicated or just strange but here is what I am doing. I have 10 forms to build for client and there will be more so I have them submitting to one form library. These are only forms that require approval and there are a few.&lt;br /&gt;
This way I can create one workflow to monitor and send tasks for approval and there is only 1 library.&lt;br /&gt;
The library is configured with 2 filters, one for submitted=[me] and second is supervisor=[me] so only the supervisor or the submitter will see there related forms, all in the one place.&lt;/p&gt;
&lt;p&gt;So i have most of these forms injected as some update multiple lists and some have special Qrules functions like number of days.  Due to this they are amin approved forms witch is working well, I am SharePoint Admin so not to difficult.&lt;/p&gt;
&lt;p&gt;Having issue with promoting fields to columns though.  Got the first working then when completed the second it updated the columns but deleted all the data submitted by the first form.&lt;/p&gt;
&lt;p&gt;Is just enherent of the SharePoint form libraries work? any ideas on how to correct this?&lt;/p&gt;
&lt;p&gt;I have taken to creating a very interesting form name that has 5 or 6 values in and using calculated fields to extract the values I need into columns that can be accessed by the workflows. Works OK but would like solution to first problem if there is one.&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;</description></item></channel></rss>