<?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>General</title><link>https://www.infopathdev.com:443/forums/41.aspx</link><description>If you're not sure where to ask your question, ask it here. If necessary, our moderators will make sure it gets classified in the correct board.</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP3 (Build: 31118.962)</generator><item><title>Re: Trying to Understand InfoPath Versioning Functionality</title><link>https://www.infopathdev.com:443/forums/thread/93778.aspx</link><pubDate>Sat, 19 Oct 2013 19:14:49 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:93778</guid><dc:creator>Patrick Halstead</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/93778.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&amp;PostID=93778</wfw:commentRss><description>&lt;p&gt;That&amp;#39;s because you are using the same name for the new versions so it is automatically updating.&lt;/p&gt;
&lt;p&gt;If you changed your form&amp;#39;s name to Name_v2 and published it would not try to upgrade the first. This is known as &amp;quot;side-by-side&amp;quot; versioning and is a good technique for doing what you want.&lt;/p&gt;
&lt;p&gt;We have a training module on this as part of our master class. Next date for the online class is November 12th-15th. We&amp;#39;d love to have you join us.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.qdabra.com/en/training/TrainingDetail.aspx"&gt;http://www.qdabra.com/en/training/TrainingDetail.aspx&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Trying to Understand InfoPath Versioning Functionality</title><link>https://www.infopathdev.com:443/forums/thread/93658.aspx</link><pubDate>Mon, 14 Oct 2013 20:30:56 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:93658</guid><dc:creator>kriskyk</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/93658.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&amp;PostID=93658</wfw:commentRss><description>&lt;p&gt;Hi All,&lt;/p&gt;&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; I&amp;#39;m new to InfoPath and trying to understand its versioning intended functionality....&amp;nbsp;&lt;/p&gt;&lt;p&gt;What i&amp;#39;m trying to grasp/understand is why form updates are retroactive for submitted&amp;nbsp;email forms?&amp;nbsp; &lt;/p&gt;&lt;p&gt;The scenario of concern is that a form that was generated/submitted in a previous period should still reference its original secondary data. For example: a drop down list of employees.&amp;nbsp; Currently it appears that&amp;nbsp;if the form templates secondary data is updated so is the employee list in already previously generated/submitted forms.&lt;/p&gt;&lt;p&gt;I&amp;#39;ve tried: Form Options &amp;gt; Versioning &amp;gt; Update Existing Forms &amp;gt; Do Nothing; with no luck.....&lt;/p&gt;&lt;p&gt;I appreciate any insight you can provide,&lt;/p&gt;&lt;p&gt;-K&lt;/p&gt;</description></item></channel></rss>