Updating published templates to a shared directory - InfoPath Dev
in

InfoPath Dev

Updating published templates to a shared directory

Last post 04-26-2007 06:12 AM by larivat. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 04-20-2007 04:03 AM

    Updating published templates to a shared directory

    I am having trouble with the my first Infopath 2003 template that I published to a shared directory at work. When ever I update the original template in design mode all of the other users who have used my form are losing data in their existing forms that they have saved, when they open theirs forms my alterations have changed the old version as well,  I am really becoming unpopular every time I alter the template, please help.  
  • 04-20-2007 06:50 AM In reply to

    • ahardin
    • Top 200 Contributor
    • Joined on 02-13-2006
    • United Kingdom
    • Posts 55

    Re: Updating published templates to a shared directory

    Larivat

     The only thing you can guarantee will not affect previous data is conditional formatting, all other operations will change at least the user operation at most will change the data.

     Validation will prevent previous forms from submitting unless done carefully.  You cannot change the name of fields, data connections etc.

    To help you you have to publish the amended form under a different name in the shared directory OR go into 'tools', 'Form Options' select 'Advanced' and change the 'On version upgrade' drop-down box to "Do nothing, exisiting forms may not work properly".

     Hope this helps

    Adam

    I'm from WALES
    [email protected]
  • 04-23-2007 11:49 AM In reply to

    • Shiva
    • Top 25 Contributor
    • Joined on 04-15-2005
    • India
    • Posts 694

    Re: Updating published templates to a shared directory

    Hi,

    If you have FormTemplate v1.0 and create Form A from it, and then you upgrade FormTemplate to v1.5, there is a default upgrade.xsl that will make sure that Form A is compatible with the schema changes when you open it in v1.5.

    If upgrade.xsl doesn't exist or doesn't do the job you need, there is a way to write you own upgrade.xsl or do the upgrade via code. Above Adam given the suggestion also works for you. Whatever we are modifications are done, those changes are automatically stores at upgrade.xsl file.

  • 04-26-2007 06:12 AM In reply to

    Re: Updating published templates to a shared directory

    Thankyou for the reply, you have all helped a great deal
Page 1 of 1 (4 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.