InfoPath Dev

Hi,

We’re experiencing quite an odd issue with opening forms within a SharePoint form library. These are the symptoms;

We recently published a newer version of an InfoPath form, and have since received some feedback that the form no longer opens in the “View Properties” view of SharePoint.

Rather interesting though, within the standard view all form instances can be opened with no problem.

The reason this has to work within the “View Properties” view of SharePoint is because we have a workflow that is sent, with a link to this particular page.

This is the error message that is displayed;

Standard;

There has been an error while loading the form.

Error Details;

The following file is not a valid InfoPath form template:

More Information;

The InfoPath Form is configured to show in the client;

The InfoPath Form was re-published in InfoPath 2010

The InfoPath form has to be accessible using Office 2007

The Error message is displayed in the browser powered by InfoPath Forms Services

The form opens absolutely fine in the standard SharePoint view;

Can you please assist me with this issue

Many thanks

I'm a bit confused about the scenario. You say: "The InfoPath Form is configured to show in the client" and "The Error message is displayed in the browser powered by InfoPath Forms Services". If the form is configured to show in the client, why is it opening in IPFS?

I'm not sure to be honest, I guess this would form part of the question. Because the form is not a web enabled form, it's been built to only display within the InfoPath client.

 When I try opening a form from a standard SharePoint view, it opens fine. However, if I try opening the form, via "View Properties" and then clicking the file name, I get the error within IPFS.

Please advise, many thanks

Sorry, I'm a bit confused by the scenario. If the form was designed to open in InfoPath, then the fact that it's opening in the browser means something is wrong. Did you change the Form Library settings to display the forms in the browser?

I guess you could try to redeploy using InfoPath 2007 (instead of 2010) to see if the form returns to its previous behavior.

Make sure that when you publish your form using InfoPath 2010 that you choose compatibility settings for 2007. Otherwise, you'll see this error.