SharePoint Integration

Re: InfoPath 2007 Form Content Type does not save as infopath form but as xml document.

Maarten DB — Wed, 06 Oct 2010 07:34:23 GMT

The december CU is the December Cumulative Update that is currently installed. I have tried updating to the last update but in the process lost a functioning sharepoint and i am running a backup now. The weird thing is that when I upload an xml that does not work to another newly created list, with only the infopath content type associated, it does work and it shows the correct icon and it renders in browser.

The xml content of the file is exactly the same as a previous working one except for the version number.

Re: InfoPath 2007 Form Content Type does not save as infopath form but as xml document.

Patrick Halstead — Tue, 05 Oct 2010 20:35:58 GMT

Hi Maarten DB,

This is strange and we've only ever seen this behavior of your XML loses the Processing Instruction at the top that tells your computer (and SharePoint) that it's an InfoPath document. You should take a look at the XML in notepad and see if it's correct. If not, it could be due to various factors - but in SharePoint (what is December 2009 CU?), encoding error in client, ... etc. My guess is that it's a bug in the CU.

InfoPath 2007 Form Content Type does not save as infopath form but as xml document.

Maarten DB — Tue, 05 Oct 2010 12:41:49 GMT

I have a couple of infopath forms deployed to sharepoint as content types. Normally, when a user creates a new document of an infopath content type, the form opens in browser mode and ,when the user fills in the form and saves the form, a new document is created in the document library with the correct icon and progid.

This was before... Now, whenever I save a form, the form submits correctly, i see the file in de document library, BUT it has the icon of an XML document, all the infopath functionality is gone and when I click the file, I get a save as dialog...

The form itself hasn't changed that much and even when I redeploy a version that worked before it still does not work. However, when I create a new doc lib and associate the malfunctioning form there, the behavior is normal and i can still reopen the saved form.

Little sidenote: I have 7 different forms that now do not work on my test machine. It used to be only one, but after redeploying them, all of them have the same problem. Now when I deployed these forms in a staging environment, the same thing started happening there.

UPDATE: all the forms in the staging now have the same problem

I have already tried reassociating the form to the doc lib. And everything looks normal in central administration.

Any suggestions?

MOSS version: December 2009 CU