General

Re: What constitutes an InfoPath version change?

Qazi Anis — Tue, 10 Nov 2009 07:30:18 GMT

Infopath changes the version whenever the form is published and it increases the version number automatically, if a form has a version number 2.0.0.1 and we publish it, the version number is changed to 2.0.0.2

Re: What constitutes an InfoPath version change?

warrtalon — Mon, 09 Nov 2009 15:06:02 GMT

More like 1.0.0.1, but I don't pay attention as it is not important to me. I let SharePoint do my versioning by creating a document library (not a form library) where I store all my forms as documents with version control turned on (I limit to 10 versions). I then map a network drive directly to that library by opening the library in Windows Explorer, copying the path, then pasting it into a Map Network Drive window (right-click on My Computer or My Network Places). Once I have it mapped to a drive, it makes it very easy and quick to save my forms back to that location. I also create a shortcut button on my taskbar so I can quickly get to my templates.

What constitutes an InfoPath version change?

davidevan — Mon, 09 Nov 2009 13:59:36 GMT

I'm just curious what constitutes an InfoPath version change. For example, a new InfoPath form would be version 1.0.0.0. If I were to put a couple new controls on the InfoPath form should the version increase to 2.0.0.0 or would it just be 1.0.0.1. What is everyone doing for their InfoPath form versioning? Is there best practice for versioning or is it totally up to the author?