Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
DiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWord
DirectoryUser Groups
Related Topics
Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ...

MS Office Forum / General MS InfoPath Questions / April 2008

Tip: Looking for answers? Try searching our database.

Question on InfoPath form upgrade

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Ken Ng - 16 Apr 2008 17:36 GMT
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?
Gavin McKay - 17 Apr 2008 12:19 GMT
Hi Ken,

This can all be done - I won't call it all that simple though :)  In answer
to your questions:

1. You need to update the template location in all the Xml files you want to
change.  I wrote a short article explaining the manual steps:

http://www.infopathkb.com/Knowledge%20Base/How%20to%20manually%20change%20an%20I
nfoPath%20Forms%20Services%60%20template%20location%20in%20an%20existing%20InfoP
ath%20form.aspx


which explains the section you need to modify.  I had to do this same task
for a client and ended up writing a simple utility to bulk-change the Xml
files all at once.  The utility opened the Xml file as text, and then did a
search-and-replace of the old template name to the new one.  I didn't use an
Xml object to do it because I couldn't remember how to change pre-processor
Xml directives :D but a text replace works just as well.

2. I don't think you'll be able to use upgrade.xsl because you said you are
changing a number of different forms.  upgrade.xsl only works when you are
modifying one version of the same form to another version.  You will probably
need to write your own custom Xsl file that will convert the old Xml files
into your new compatible format.  Again, writing a simple utility is the way
to go I think.  You will also have complete control over the Xml migration
process.

You can also use the XSD from your new template to verify that the Xsl
process has worked correctly - that's if you want the "bonus mark" :)

Hope all of that makes sense!

HTH

Gavin.
Signature

InfoPath Knowledge Base
http://www.infopathkb.com/
2B | !2B

> 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
[quoted text clipped - 9 lines]
> 2) Once I can handle the name change, is upgrade.xsl the answer to handle
> the change in the form schema?
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.