<?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: Repeating Table Secondary Data Source change from dynamic to static</title><link>https://www.infopathdev.com:443/forums/thread/118598.aspx</link><pubDate>Thu, 22 Mar 2018 21:39:03 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:118598</guid><dc:creator>Hilary Stoupa</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/118598.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=46&amp;PostID=118598</wfw:commentRss><description>So - the tricky part here is that you can&amp;#39;t copy repeating data out of the box in InfoPath. You have to use code and if this is a list form, you can&amp;#39;t do that. Creating a PDF is a great option - but that will likely involve third party tools like Muhimbi.</description></item><item><title>Repeating Table Secondary Data Source change from dynamic to static</title><link>https://www.infopathdev.com:443/forums/thread/118576.aspx</link><pubDate>Tue, 20 Mar 2018 23:17:38 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:118576</guid><dc:creator>Callie</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/118576.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=46&amp;PostID=118576</wfw:commentRss><description>&lt;p&gt;Some background &amp;gt; The overall purpose of this InfoPath web form that is used in our SharePoint Online site is to facilitate a &amp;quot;roster approval&amp;quot; process. We are an organization that has many contracting companies and those companies have employee rosters. Only the personnel on those rosters are approved to work on the organization&amp;#39;s projects. Previously, this was a manual process where the roster was a table on a Word document and passed around for signatures, but now each company&amp;#39;s roster is a custom&amp;nbsp;list on a SharePoint Online site. The roster/list can be updated at any time with new personnel, rate changes, etc., but those changes must be approved by a designated authority. The InfoPath form is the approval form and it currently has a repeating table with a binding to a secondary data source, which is the custom SharePoint list / roster. This is so the approver can open the form, review the changes to the roster within the form, and approve/deny without having to navigate anywhere. &lt;/p&gt;&lt;p&gt;Here&amp;#39;s the problem - once the form is approved,&amp;nbsp;the roster list in SharePoint&amp;nbsp;will continue&amp;nbsp;to be updated as personnel come and go, which is also updating the repeating table in the approved InfoPath form. I need the data in the repeating table to become static once the approver finalizes it. Basically, make the dynamic data from the SharePoint list no longer dynamic.&lt;/p&gt;&lt;p&gt;I&amp;#39;ve looked at everything from converting InfoPath into PDF using Microsoft Flow to rules that copy all the rows into another table (thus disengaging the binding for the final view) to rules that remove the binding but keep the previous data&amp;nbsp;and nothing has quite worked. I did get close with the copy method, but it only brought over the first row. &lt;/p&gt;&lt;p&gt;We&amp;#39;re using InfoPath&amp;nbsp;Designer 2013, SharePoint Online, and SharePoint Designer for the review / approval routing.&lt;/p&gt;&lt;p&gt;&amp;nbsp;I&amp;#39;m open to other&amp;nbsp;ideas, I&amp;#39;m just so close&amp;nbsp;to this that I&amp;#39;m&amp;nbsp;most likely not seeing all the possibilities. &amp;nbsp;&lt;/p&gt;</description></item></channel></rss>