InfoPath Dev

The following problem arises when publishing a revised form to a SharePoint document library. I'm using K2.net but perhaps someone here has experienced a similar problem... calling vt_asparagus! :)

I've found that if I make a change to an InfoPath form and publish it to SharePoint, then any existing documents can't use the new version of the form.

Upon opening the document from SharePoint, the following error message is displayed:
InfoPath cannot open the following file: <filename>
The form contains schema validation errors.

Content for element 'http://schemas.microsoft.com/office/infopath/2003/myXSD/2005-09-08T03:18:17}NewStart' is incomplete according to the DTD/Schema.
Expecting: http://schemas.microsoft.com/office/infopath/2003/myXSD/2005-09-08T03:18:17}_K2.

This occurs even if the InfoPath document's data source doesn't change prior to integration with K2.net. The K2.net integration does alter the data source, it adds a _K2 section to the XML, however the section being added is the same each time.

Has anyone seen a similar problem with incompatible versions of a form? Surely I can't be alone in this..

Any help greatly appreciated.
Thanks
David.

Okay, I may be having a 'moment' here but I've found that if I hack the XML files produced by the form, and update the older version to have the same version number it will open successfully.

Presumably this won't work if the data source is actually different?

Apologies for hoggin' my own thread. :)

On the Form Options dialog, using the Advanced tab, if I change the "On version upgrade" option to "Do nothing (existing forms may not work properly)" then older versions of the XML files work fine, just as long as the data source hasn't changed.

Hey, crazy day and still no end.

Do you get the schema errors when you simply preview the form before publishing to SharePoint?
Usually when I make a change to an InfoPath form, I publish to SharePoint and then I refresh the InfoPath form with K2 by right clicking the process >> refresh the infopath form.

Also what types of changes were you make to the InfoPath form? Where they schema changes? If the old XML that is saved on SharePoint and it does not match the modified .xsn that has been published you will get schema validation errors. I beleive there is an InfoPath event called that is used for modifing data - read the following:

InfoPath automatically stamps a date, time and version number for your form template upon save. For sandboxed solutions, InfoPath uses this stamp for ensuring that the user filling out your form is using your latest template. Each time a user opens an InfoPath form based on a sandboxed solution, InfoPath verifies whether there is a newer version of the form template available. If a newer version is available, InfoPath updates the template silently in the background. If the new template has fields or groups that were added in design mode, then, by default, InfoPath will automatically add them to the older form when it is opened with the new form template. However, if you made any other structural changes (e.g. removing or renaming a field or group), you will be prompted with a warning upon save from design mode that existing forms may lose data in the affected fields or groups. At this point, you can choose to publish your updated template to a new location (to ensure that existing forms can use the original template) or save over the existing one. If you#%92ve made a change to your template that will lose data in existing forms but need to override the existing template, you should use the OnVersionUpgrade() event which occurs when a user opens an existing form that has a newer version of the associated template available. With this event, you can write script to run a procedure to modify the structure of the existing form to be compatible with the new template. Note that your script will also need to handle the additive changes, as InfoPath cannot do that automatically if you use the script option. If you only made non-structural (e.g. formatting or layout changes) or additive changes, new and existing forms will automatically work with this upgraded template without any data loss.

Thanks again, vt_asparagus. To try to answer your questions:

I can preview my own form without encountering this problem (although prior to integration with K2.net I obviously can't submit the form as the functionality hasn't been added yet!). I wasn't making any changes to the InfoPath form's 'data source' - the last change was purely a cosmetic request from the client.

An example of the problem: I publish the form to SharePoint, integrate with K2.net (using the method you've indicated above) and then fill out a form. This instance of the form sits in SharePoint awaiting approval (using an InfoPath activity in K2.net). If I republish the same form and re-integrate with K2.net - without changing a thing on the form or in K2 - then I can no longer open the previously completed form. The error message in my original post is displayed.

If I download the XML of the completed from SharePoint and edit the version number to match the newly republished form then it will open correctly.

The error message would appear to point to the inclusion of the K2 data fields as being the problem when InfoPath tries to automatically update the older version of the form. I don't know why InfoPath can't update the K2.net section of the template... In switching off the automatic update, I've at least gotten around this problem.

However changes to the original InfoPath form's data source (that which exists prior to integration with K2.net) will cause the older forms to fail.

Ummm...let me think on this... I do not think it is possible to tie more than one InfoPath form to a K2 process...

I saw you made the post on the K2 forum as well :-)

Did you see this:
-http://forum.k2workflow.com/viewtopic.php?t=896
-http://forum.k2workflow.com/viewtopic.php?t=712

Similar errors that you ran into. I am still researching. Specifically, look at the second one, it seems the "any" attribute may be missing from your schema and that may be causing you some issues.

I'm only using the one form with my K2.net workflow.

The latter half of the thread linked below describes why I have to republish the form:
http://forum.k2workflow.com/viewtopic.php?t=232

I don't think it's the republishing that's at fault. I just wanted to demonstrate the even with no schema changes the form is incompatible with a previous version.

I'm not basing the form on an existing XSD as listed in the second link, although the error messages 8are* quite similar.

I assumed you were not using a custom XSD but error was the same. The first link had to do with one of the K2 labs and it seemed similar.

David,

I just ran into the exact issue when I was investigating something else in regards to K2. http://forum.k2workflow.com/viewtopic.php?t=972

I have not had a chance to test thier solution, will later tonight but it seems the issue was that the K2 nodes need to have proper defauly values.

I have tried the solution offered here:
http://forum.k2workflow.com/viewtopic.php?t=946

It sounds nuts but it seems to work.

Yeah - that seems nuts.

Hi,

I'm having the same issue but my form doesn't have anything to do with K2, its got managed code.  When I remove dthe managed code, the form works perfectly in the browser but when I add managed code, the form complains that 'One or more fields are not installed properly.  Go to ther list settings page to delete these fields."

I'm ready to pull my hair out with InfoPath - its such an unfriednly tool.

 Thanx

Yusuf