Changes in InfoPath 2010 (for IT pros)
Applies to: Office 2010
Topic Last Modified: 2012-04-05
IT Pros can learn about the new, changed, and deprecated features of Microsoft InfoPath 2010 and how these changes can impact migration plans.
|Are you looking for help using new features in InfoPath 2010? Visit Office.com to learn how to use new features (http://go.microsoft.com/fwlink/p/?LinkId=247996).|
In this article:
This section provides information about removed features in InfoPath 2010.
In the InfoPath 2010 Editor, the entry point for Import form data is removed. The Import form data option enabled users to select a third-party data importer to import form data into their forms.
The functionality to track data set changes when a user designs a form in InfoPath Form Designer against a Web service that returns the System.DataSet type is removed in InfoPath 2010. However, existing forms that use change tracking with the System.DataSet type will continue to work in InfoPath 2010.
The settings that let you disable aspects of InfoPath Form Designer are removed from the Office 2010 Group Policy templates. This change provides more consistent functionality across installations of InfoPath 2010.
The form template exporter extensibility option is removed from the InfoPath 2010 Form Designer. In Office InfoPath 2007, this option enabled third-party vendors to provide tools to export InfoPath form templates to other formats.
The sample form templates that were included with Office 2003 and the 2007 Office system are removed in InfoPath 2010. If an organization uses these templates, you must republish these form templates to a location other than the default location to continue using the forms. The new page and section layouts that are now in the InfoPath Form Designer replace the form templates.
All integration points with BizTalk Human Workflow Services are removed from InfoPath 2010. This functionality is replaced by Workflows in Microsoft Office SharePoint Server 2007 and Microsoft SharePoint Server 2010.
The capability to publish a form template that can be installed on the local client computer as an application is removed. Instead, users can publish forms to a specific location and run the form from that location. Existing installable forms will continue to run in the InfoPath 2010 Editor.
The Receive and submit data Web service connection option is removed for new forms. To simplify the feature and promote best practices, it is replaced with separate options to create a Receive data connection and then create a secondary Submit data connection. Existing forms that use the Receive and submit data Web service connection type will still work in InfoPath 2010.
The capability to display sample data in the controls is removed. In InfoPath 2010 users must preview the form and manually enter sample data to evaluate how it looks in the form.
The ability to develop script code in InfoPath 2010 is removed. When existing forms with script code are opened, all of the entry points to add code to a form will be disabled and hidden. Runtime support continues, but customers will have to upgrade script code to managed code to continue developing by using an integrated development environment in InfoPath.
Office 2010 does not support Microsoft XML Parser version 5 (MSXML5). Existing solutions will not create an instance of MSXML5 objects when loaded by Office 2010. Migrate code to managed code by using the Microsoft .NET Framework or to MSXML6. Note that MSXML6 does not support digital signature code.