InfoPath Dev

I created a form a few years ago in Infopath 2003. It is a constantly evolving form as our business needs change often so I am always adding and deleting fields. About 6 months ago our company upgraded to Office 2007, including Infopath 2007. The forms can still be filled out with no issues, however when one of our analysts tries to open the form after it has been submitted they get this error. InfoPath cannot open the following file: C:\Documents and Settings\....etc The form contains schema validation errors. When I Show Details is says... Element '{http://schemas.microsoft.com/office/infopath/2003/myXSD/2009-08-17T20:55:02}Strat_CustFeedback' is unexpected according to content model of parent element '{http://schemas.microsoft.com/office/infopath/2003/myXSD/2009-08-17T20:55:02}Contract_Strategy'. Expecting: {http://schemas.microsoft.com/office/infopath/2003/myXSD/2009-08-17T20:55:02}Strat_MOV, {http://schemas.microsoft.com/office.... I thought that perhaps it was because I recently made some changes to the form and did them in 2007 (that seems to be when all the problems started). I got a second computer with 2003 loaded on it and tried to go back to a previous version of the form and make the changes in 2003, but that did not fix the issue. It seems to be a progressive problem (which is the confusing part for me) because it started with just a few analysts and now has progressively gotten worse to the point that no one in our department can open any of the forms anymore. This has become a production critical issue now and no one in our company can seem to figure out why. Any insight would be greatly appreciated. Thanks, Josh

Hi - generally this error is because the main data source was changed in the form template. It sounds like you have added and deleted fields.

There are versioning settings - you can set the template to upgrade existing XML. If you've deleted, moved or renamed nodes in the main data source of the template, you will have data loss if you upgrade your existing XML.

You can test your current template with existing XML to see in a non-destructive fashion what you need to do to resolve this - here's a blog post of mine on previewing your template with existing XML.

However, if the user opens the current template, and creates and saves a file, if the template hasn't changed, they should be able to reopen that XML without an issue - is that the case? Can you create, save and close a form, and then immediately re-open it and not have an error?

 I just upgraded from SharePoint 2007 to 2013 and I am getting this error when trying to open any forms created before the upgrade.  It seems to work fine for any forms created in the form library today.

 

Please help, this is causing a major issue.

 This issue has been resolved, please disregard this message.

 Hi Hilary,

 

Is there a way to restore existing forms? I made a change in the default form and now I'm not able to open any of the existing forms.

 

This is the error message that I'm seeing

Element '{http://schemas.microsoft.com/office/infopath/2003/myXSD/2014-07-28T22:55:36}field939' is unexpected according to content model of parent element '{http://schemas.microsoft.com/office/infopath/2003/myXSD/2014-07-28T22:55:36}myFields'.

 

I removed field 939 and still getting this error.

Thanks,
Mara 

 

When you publish the form, under the form options, you can choose what should happen to existing XML. Look in the versioning category of the form options. You can set the XML to be updated to the latest schema. Here's a blog post on previewing with an existing XML to see if your changes will cause you any issues: http://www.infopathdev.com/blogs/hilary/archive/2009/03/13/first-do-no-harm.aspx

 I will try that. Thanks

 Hi Hilary,

 I have the same type of error message.  Does what you suggest actually fix the issue or is it just a preventative measure to prevent future issues?   I applied the change you suggested and re-published my form but still receive the issue.

Thanks,

 Paul

It is a preventative. If you set your versioning to update existing XML, you shouldn't get schema validation errors in the filler, but browser forms are pickier. What kind of schema changes did you make?

Thanks for the quick response.  I made the changes to update the existing XML so the issue won't occur again.  I made numerous changes to the form and only checked the preview.  I will not make that mistake again.  I ended up deleting my form and re-publishing, to fix the issue and add in my changes again.