Geeks With Blogs

News I am a SharePoint Designer for a Sales based media organization. I have been a SharePoint professional since Jan 2007, working with MOSS 2007 and now 2010. I have the MCTS SharePoint 2007 Configuration and hope to someday have the time to upgrade for 2010. My previous work for a fortune 100 bank integrating their business processes into InfoPath forms and in SharePoint administration started my SharePoint journey. I am now a full time SharePoint admin, developer, and designer. My day to day is spent integrating the media sales business into a SharePoint collaboration portal.
SharePoint Tales Anecdotes of SharePoint Life

In January I had the pleasure to speak at SharePoint Saturday Virginia Beach.  I presented a session on InfoPath 2010 forms design which included some of the basics of Forms Design, description of some of the new options with InfoPath 2010 and SharePoint 2010, and other integration possibilities.  Included below is the information presented:

First thing you need to understand is what the difference is between an InfoPath List form and a Form Library Form? 

SharePoint List Forms:  Store data directly in a SharePoint list.  Each control (e.g. text box) in the form is bound to a column in the list. SharePoint list forms are directly connected to the list, which means that you don’t have to worry about setting up the publish and submit locations. You also do not have the option for back-end code.

Form Library Forms:  Store data in XML files in a SharePoint form library.  This means they are more flexible and you can do more with them.  For example, they can be configured to save drafts and submit to different locations. However, they are more complex to work with and require more decisions to be made during configuration.  You do have the option of back-end code with these type of forms.

Next steps:

You need to create your File Architecture Plan. 

  • Plan the location for the saved template – both Test and Production (This is pretty much a given, but just in case - Always make sure to have a test environment)
  • Plan for the location of the published template

Then you need to document your Form Template Design Plan.  Some questions to ask to gather your requirements:

  • What will the form be designed to do?
  • Will it gather user information?
  • Will it display data from a data source?
  • Do we need to show different views to different
    users? What do we base this on?
  • How will it be implemented for the users?
  • Browser or Client based form
  • Site collection content type – Published through
    Central Admin
  • Form Library – Published directly to form library

So what are the requirements for this template? 
Business Card Request Form Template Design Plan

  • Gather user information and requirements for card
  • Pull in as much user information as possible.
  • Use data from the user profile web services as a data source
  • Show and hide fields as necessary for requirements
  • Create multiple views – one for those submitting the form and
    another view for the executive assistants placing the orders.
  • Browser based form integrated into SharePoint team site
  • Published directly to form library

The form was published through Central Administration and incorporated into the site as a content type.


Utilizing the new InfoPath Web part, the form is integrated into the page and the users can complete the form directly from within that page.


For now, if you are interested in the final form XSN, contact me using the Contact link above.   I will post soon with the details on how the form was created and how it integrated the requirements detailed above.

Posted on Thursday, June 21, 2012 8:57 PM InfoPath 2010 | Back to top

Related Posts on Geeks With Blogs Matching Categories

Comments on this post: InfoPath 2010 Form Design and Web Part Deployment

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © JKenderdine | Powered by: