This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.
COURSE of the MONTH
13 days, 2 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Upgrading browser-enabled InfoPath forms in a SharePoint solution
Posted on 2010-09-10
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!
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2-
2
4 Comments
Best Practice when updating forms is not to delete fields from your schema in the form so you do not break comaptibility with the existing forms. Otherwise best practice would be to create a new seperate form library and seperate the two. Typically you can give the users two URL's or something so that they can move between the new form and the old versions.
You should be able to publish it as a site content type that would allow you to have both appear on the same library in the drop down.
You should be able to publish it as a site content type that would allow you to have both appear on the same library in the drop down.
Thanks, Clayfox.
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.
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.
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.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
There is one common problem that all we SharePoint developers share: custom solution deployment.
This topic can't be covered fully in this short article, so all I want to do in this one is to review it from a development-to-operations perspectiv…
Pimping Sharepoint 2007 without Server-Side Code
Part 1
One of my biggest frustrations with Sharepoint 2007 in the corporate world is that while good-intentioned managers lock down the more interesting capabilities of Sharepoint programming in…
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…
In this video you will find out how to export Office 365 mailboxes using the built in eDiscovery tool. Bear in mind that although this method might be useful in some cases, using PST files as Office 365 backup is troublesome in a long run (more on t…
Suggested Courses
Course of the Month13 days, 2 hours left to enroll
777 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.