SharePoint Integration

Re: open old xml-form with old xsn

c_breemersch@yahoo.com — Fri, 21 Aug 2009 09:33:59 GMT

Hi Jo-Anne,

thank you for your suggestions. However, the versioning does'nt help. When opening the new form I receive the following message:
"Form Conflict: The form you are opening has the same form ID as a form already on your computer."

I thought the version number was stored in the xml, so I would suppose that the program knows what version of the xsd to use, but apparently it doesn't work like that. All I want is that my old forms can still be opened and the new forms also. I have added two templates in the sharepoint library, but that doesn't work either.

I haven't tried the 'creating views' option yet.

Christophe

Re: open old xml-form with old xsn

Jo-Anne Alfafara — Thu, 20 Aug 2009 15:34:31 GMT

Hi christophe,

I'm not sure if this is the right solution for you, but could you try the following steps:

1. In your form, click Tools > Form Options

2. Click Versioning. Inside "Versioning" category, there is an option to manage version upgrades. The option "Automatically upgrade existing forms" is selected by default. Can you try selecting the option "Do nothing"? Then re-save your form.

3. Re-publish your form to your library and see if that works.

More information here: http://office.microsoft.com/en-us/infopath/HA100522701033.aspx

Or you could try Patrick Halstead's idea of creating separate views for each version and add an Open rule to switch to the correct view based on the version in the form. You can read the post here.

open old xml-form with old xsn

c_breemersch@yahoo.com — Thu, 20 Aug 2009 14:09:25 GMT

Hi,

I have a library with InfoPath-xml-files based on a specific xsn-file. I want to change the scheme drastically so the new xml-files will be different.
However, the old forms should still open with the old xsn-file. The problem is that whenever I open the old forms, the open with the new Schema.

How can I make sure that the old forms open with the old xsn and the new files with the new xsn? All this has to happen in the same current webpart, because code is linked to this webpart.

Thank you,

christophe