Chris’s SharePoint Reflections

Just another weblog

  • Chris Zhong

    IT consultant Australia

  • Advertisements

Make your InfoPath investment worthwhile – Part 1 Why use InfoPath

Posted by chrissyz on October 6, 2008

In Microsoft office suite, the trend is:

·         Document-> word

·         Spreadsheet-> Excel

·         Forms-> InfoPath

InfoPath is designed for efficient forms management and becoming more mature. It is now a great idea for organizations to use InfoPath 2007 for their form development.

The strong points of InfoPath:

1.       Build on Xml, easy for organization to reuse data and connect to LOB

The data stored in InfoPath can be easily separated from the form and reformatted or reused in a variety of ways. This enables form designer to integrate form data into existing business process. For example, look at the use the form in SharePoint. InfoPath’s views and formatting elements are self-contained in the XSN file, which makes the InfoPath form very portable. On the other hand, if you use SP Designer to design a form in SharePoint library and submit it to a list item, the forms used here are very much tied to the lists they depend on, thus, are not very portable.


2.       Rapidly develop forms

InfoPath’s OOTB drag and drop support for form controls, table layouts etc allow the power user create a flexible form that is designed to accommodate the users. However, InfoPath does not support the following advanced scenarios like: tabs, custom AJAX/DHTML, multiple/nested forms. Meanwhile, InfoPath has a lot of features like rules, formulas, data validation, data connections, conditional formatting etc, which makes most form development does not need code. It out-weighted other form designing tools on this point.

As for developer experience, InfoPath2007 has strong capabilities allowing developers to efficiently develop and deploy form solutions. It has new object model which is based on .NET 2.0 and incorporate with System.xml. The code is written in common develop platforms (VSTO, VSTA). The coding experience is much more familiar and handy.


3.       Form services  VS Smart Client

The core concept in 2007 release is “design once”. It means you only need to design one form and it will work on both the smart client and form services.  You only need to compile once, deploy once, and send customer one URL, and InfoPath will work for them whether or not they have InfoPath.

An InfoPath form can be opened in:

1) Any browser (e.g. IE, Firefox, Safar etc.)

2) Desktop App


Most of the features are still available in both smart client and form services like most controls, business logic (rules, data validation, conditional formatting), new object model etc.  However, you can optimize for Desktop, but you cannot optimize for a specific browser or an environment. This is a limitation with any form tools which support variety of tools. The choice of controls is limited as well. The following table is a comparison between form services & smart client


InfoPath Form Services

InfoPath 2007 Smart Client


It support cross platform like (Unix/Linux.)

It doesn’t support 


Don’t require InfoPath Installed in all User Machine

Required to have InfoPath Installed in all User Machine


Form accessible through web browser.

Form accessible through Office InfoPath 2007


Browser form relies on the server for a variety of form processing operations, require more communication to exchange data between the browser and the form server

InfoPath client doesn’t need to communicate with the form server as frequently. This is because the InfoPath client processes most forms locally on the user’s computer.


Does not support all features of InfoPath2007

Like Design & Compatibility checker

It support full features


Does not support all the controls of InfoPath2007

it support full controls


As far as which method is best, it depends on your situation.  Is the InfoPath client readily deployed to all users?   If the client has Forms Server already, and they are unsure about the availability of the InfoPath client for all users, I would recommend browser forms. The biggest selling point to clients for using Forms Services is that it doesn’t require a client app to be installed on users’ machines. From a client’s perspective, despite the fact that you do lose some functionality using Form Services, allowing the end-user to view forms through a browser far out-weighs any Form Services limitations. I have found the limitations in Forms Services to be minimal. You still get the majority of the OOTB conditional formatting, field validation and submit functionality.


4.       Automate data-driven business process

InfoPath 2007 has a very deep integration with the rest of MS office suite, especially SharePoint and Outlook. For example, you can integrate forms in outlook and promote fields and properties in Outlook folder. As for SharePoint, InfoPath can be used in workflow, form library, publishing content type, archiving, document information panel etc. I will talk more about it in the second part.


One Response to “Make your InfoPath investment worthwhile – Part 1 Why use InfoPath”

  1. […] Make your InfoPath investment worthwhile – Part 1 Why use InfoPath […]

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: