InfoPath Form Library doesn’t allow to save any changes

Sometime InfoPath form library doesn’t allow to save the changes made to list item.

It throws following error:-

ExceptionType: ‘SPException’ ExceptionMessage: ‘Changes could not be saved into the
document.
The property to change is read-only for the document’s content type, or the
document is missing XML elements
or attributes where the changes would be saved.
Try editing the document  in a Windows SharePoint Services-compatible XML editor
such as Microsoft Office InfoPath.

This problem happens when the Form Library contains several property promoted fields
and the form for which changes were made and supposed to save , doesn’t contains those
fields and blows up when trying to save.

To fix this issue, double check content type definition and linked field associated with that.

Some time problematic field got created, doesn’t remove just by deactivating/Uninstall of
feature because instance got created.
This is important to find the instance and remove it then use feature to install/activate to work properly.

Action Item to resolve this issue:-

To fix the problematic filed which blows up,
1. Create a unit test to identify the fields used in Infopath Form
2. Now Remove the filed column mapping from the content type associated in a list
3. Similarly remove the field mapping from content type in Site Collection
4. Remove the content type from the Site Collection
5. Redeploy the content Type so that the Push Down mechanism will update the child
content type

And this solved the problem.

Advertisements

3 thoughts on “InfoPath Form Library doesn’t allow to save any changes

  1. Hi Mukesh,
    Sounds like I have the same issue with an InfoPath form that I have recently developed for a client. Im having a little trouble with understanding exactly what the solution is that you are proposing.

    “Some time problematic field got created, doesn’t remove just by deactivating/Uninstall of feature because instance got created. This is important to find the instance and remove it then use feature to install/activate to work properly.”

    Are you saying here that the problematic column does not get removed by merely removing the column from the promoted fields in InfoPath and republishing to the form library?

    “To check the problematic filed check List columns, Content Types associated with that list, then check site collection content type definition and remove the linking and finally delete the column from site collection.”

    Could you be a little clearer and expand on what you mean here? It sounds like you are proposing the course of action / solution but I am having trouble understanding exactly what needs to be done.

    Cheers.

  2. I have updated my post, see the action items to fix the problem.
    Hope this should resolve your problem, Let me know if it works.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s