Upgrading browser-enabled InfoPath forms in a SharePoint solution
Hi, I have a live SharePoint 2007 solution that involves a couple of InfoPath forms. I have added functionality to the forms, and need to deploy the new versions alongside the old ones so that instances of the old forms can still be opened. I seem to have a conflict between the versions in that I currently have to deactivate the old form solution in the site collection before I can activate the new form.
What element values in the manifest.xsf and other files within the xsn need to be modified in order for the two versions to happily coexist and work independently of each other?
Any "best practice" resources on this would be helpful.
Many thanks!
What element values in the manifest.xsf and other files within the xsn need to be modified in order for the two versions to happily coexist and work independently of each other?
Any "best practice" resources on this would be helpful.
Many thanks!
Last Comment
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
I have found in these situations, where SharePoint does not update correctly.
To start from scratch and publish them with new names and delete out the old ones, since the replacement process often does not work completely.
To start from scratch and publish them with new names and delete out the old ones, since the replacement process often does not work completely.
ASKER
Not quite a complete answer, but helpful.
Microsoft SharePoint
Microsoft Sharepoint is a software platform and family of software products used for collaboration and web publishing combined. These capabilities include developing web sites, portals, intranets, content management systems, search engines, wikis, blogs, and other tools for business intelligence and collaboration. SharePoint has a Microsoft Office-like interface, and it is closely integrated with the Office suite.
40K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
ASKER
The new version of the form contains additional fields, but none of the original fields have been deleted. If I keep to one content type then as far as I am aware I am tied to one associated InfoPath form, which would not give the users the ability to choose one of the two forms in the drop down. Correct? In which case I need two content types. The content type is generated when I publish my form - so I need two separate forms?
These are browser based forms with codebehind requiring full trust, so I am not sure that having two separate form libraries would work? When I upload a form via Central Admin I don't get a choice as to which form library it goes into - there's only one per site collection?
Please let me know if there's a shortfall in my understanding or logic here.
Many thanks for your help.