Home » sharepoint » SharePoint 2013 » Some Best Practices for Building Forms for SharePoint Server 2013 with InfoPath

Some Best Practices for Building Forms for SharePoint Server 2013 with InfoPath

The demonstration of how to build a form with InfoPath 2013, which is included in a video tutorial on SharePoint-Videos.com titled InfoPath Form Tools for SharePoint 2013 is directed towards forms developers, administrators, designers with little experience building forms with InfoPath. So its short length (10 mins) makes it an excellent asset to included in a curriculum on forms development.

This video is available for unlimited viewing by anyone with a subscription to our website. The video is also included in our tutorial set on building electronic forms with SharePoint Server 2013, SharePoint 2013: Enterprise Forms. The tutorial set is available for purchase and local use by individuals or groups.

Darvish Shadravan, a Technical Specialist and a published author on forms publishing (his books are published by the Microsoft Press) demonstrates how to use InfoPath 2013, in Design Mode, to build a form to manage requests from a Line of Business (LoB) unit to add content to a records management site. The form will be submitted to an hypothetical central IT department for disposition.

This video tutorial presents some important best practices for building forms with InfoPath 2013, including:

  1. Be sure to provide unique names for fields. The InfoPath 2013 out of the box naming convention for fields merely appends a number following the string “field”, which makes it difficult, as this video points out, to quickly find information in forms with quite a number of fields
  2. Use the “Views” feature to minimize the complexity of a form. Providing discrete views of the same electronic form for different application settings is preferred over building a complex form to satisfy any/all viewing.
  3. Keep in mind the advantage of the no-code development option presented by InfoPath 2013. Business Analysts from LoBs can be taught to use the tool to build specific forms for business processes, which can, in turn, lower the burden on a central IT organization
  4. Use the conditional formatting capability of InfoPath 2013 to reduce the complexity of a form. Conditional formating facilitates precise determination of when and when not to serve additional information to a user consuming a form depending on an answer to a question included in the form
  5. Ira Michael Blonder

    © Rehmani Consulting, Inc. & Ira Michael Blonder, 2013 All Rights Reserved