K
Ken Ng
Currently, we have several form templates in use by users. We are planning to
consolidate all those into one form templates for easy maintainance. As part
of the work, we need to modify the schema and the name of the for template.
As the exist form templates are already in use and users have saved form data
XML into sharepoint library, here are my two questions:
1) The form data XML files are referencing the old xsns which are now all
combine into one new xsn with a different name. How can I make sure when the
users double click on the XML files, the new xsn will be opened to show the
form?
2) Once I can handle the name change, is upgrade.xsl the answer to handle
the change in the form schema?
consolidate all those into one form templates for easy maintainance. As part
of the work, we need to modify the schema and the name of the for template.
As the exist form templates are already in use and users have saved form data
XML into sharepoint library, here are my two questions:
1) The form data XML files are referencing the old xsns which are now all
combine into one new xsn with a different name. How can I make sure when the
users double click on the XML files, the new xsn will be opened to show the
form?
2) Once I can handle the name change, is upgrade.xsl the answer to handle
the change in the form schema?