InfoPath Dev

Hello, I've ran in to an issue where when we update one of our forms it also updates previously filled forms which have signatures (Via integrisign) on them, when the form changes the signature gets invalidated, I noticed that the filled forms are saved as XML which reference the original form (the one that gets updated and then invalidates signatures), and was wondering if there is any way to have the submit button save a full copy instead of an XML that references the original, or if there is a way to avoid form updates invalidating signatures. If you need further information please let me know. Thank you.

Hi - this is a great scenario for using content types. You can set the form library to use content types. Publish the form as a content type, set the library to default to that. You can relink the forms as needed from the relink view, if you have an existing library that you need to change over.

Then, when you make a template change, publish the change as a new content type. Set the library to use that as the default content type. New docs will use the new content type - old docs will keep using the old one.

Hilary Stoupa:

Hi - this is a great scenario for using content types. You can set the form library to use content types. Publish the form as a content type, set the library to default to that. You can relink the forms as needed from the relink view, if you have an existing library that you need to change over.

Then, when you make a template change, publish the change as a new content type. Set the library to use that as the default content type. New docs will use the new content type - old docs will keep using the old one.

Looking at this, I've enabled content types in both libraries (New and Completed), when I go to publish the form and specify new content type it publishes to the root of the site as a new content type and not the library.

Content types do not publish directly to the form library - the published XSNs are stored in their own library.