Publish faster to even more places with InfoPath 2007
When designing a form template, publish is an important step to make the form available for end users of the form. In InfoPath 2007, we have made some modifications and improvements to the publish process. This article is intended to highlight some of the key changes you will encounter in the publishing wizard.
Let us start off with a snapshot of the page in the wizard which helps you decide where to publish.
Here is the second page in the wizard when you invoke File/Publish in InfoPath 2003.
Here is the first page in the wizard when you invoke File/Publish in InfoPath 2007.
Here are some key differences that you can notice:
- Windows SharePoint Services server is now the default option and it can be used to publish to SharePoint server with or without InfoPath Forms Services. This option itself has several new features worth a blog post of its own.
- Shared folder and web server options have been collapsed into one, namely, network location. This option includes the functionality of both shared folder and web server.
- Email has been added to allow sharing templates via email. This functionality used to be available previously under File menu as "Send form as attachment". This option can be used to generate InfoPath email forms integrated with Outlook 2007.
- Installable form template option has been added. This makes it really easy to create installable solutions which you may need to do if you are form's security setting is fully trusted.
- A new branch to publish a Document Information Panel template on a SharePoint site has been added. However this option will show up only when it is relevant (i.e. you are customizing a content type in SharePoint).
Work on it here, publish it there
Another important difference is the concept of "working/developer copy" vs. "published copy". In InfoPath 2003, when you complete the publish wizard, your working solution will be the same as the published copy. In other words, any changes you are making from then on is on the published copy which may not be something you want to do. In InfoPath 2007, when you complete the publish wizard, your working solution is still the original copy that you were working with and subsequent changes to the solution will not affect the published copy unless you chose to publish those additional changes.
Publish once, publish again
We have also made it really easy to make updates to your published copy. Once you have successfully published once, the next time you go through the wizard, it will remember your previous information and automatically populate them for you. This makes it really easy to go through the wizard for subsequent publishing without having to re-enter various information.
Hope you have a great experience publishing form templates using InfoPath 2007.
Anand
Senior Development Lead
Comments
Anonymous
October 15, 2006
The comment has been removedAnonymous
October 17, 2006
With forms authentication, your users will need to first login to the site and click "remember me." This will allow the users credential to be persisted and InfoPath to publish against the server.Anonymous
December 21, 2006
I don't have that option anymore. I only have the ability to publish to an .MSI file. It's like the page of the wizard that asks me what kind of template I'd like to create is being skipped and it always selects .MSI. Even the help screens in Infopath talk about using .JS but it's unavailable to me. Any suggestions?Anonymous
December 21, 2006
ZoomPooky, You are right in that the .js option has gone away. We only support creating MSI files from the Publishing Wizard in Infopath 2007. If you still want to create .js installers, you can download the InfoPath2003 SDK (http://www.microsoft.com/downloads/details.aspx?FamilyID=351F0616-93AA-4FE8-9238-D702F1BFBAB4&displaylang=en) and run the RegForm tool there to create a script installer. Hope that helps!!!Anonymous
July 15, 2008
Hi, I am new in Infopath and facing a problem during publishing. I am publishing my Form to a MOSS Server e.g. Server A; I am trying to take the form and then deploying in Server B. I am facing a strange problem while submitting the Form. It hangs. Is there anything wrong I am doing? After doing a little research I figured out that it is holding Server A name in some internal files which I can not change. I am shipping my .XSN file to be deployed to Server B. Any help in this regard would be of great help. Thanks DibsAnonymous
October 29, 2010
Hi Ramesh, www.sharepoint-tips.com/.../publishing-infopath-to-sharepoint.html