Home » sharepoint » SharePoint 2013 » How Electronic Forms Built with InfoPath 2013 Interact with SharePoint Server 2013

How Electronic Forms Built with InfoPath 2013 Interact with SharePoint Server 2013

SharePoint Administrators, developers and even stakeholders need to maintain an understanding of how forms built with InfoPath 2013 work with SharePoint Server 2013 and SharePoint Online.

In a video tutorial titled InfoPath 2013 Integration with SharePoint 2013, authored by Darvish Shadravan, we provide these users with in understanding of the interaction between personnel connecting with browsers to forms built with InfoPath 2013 and SharePoint Server 2013.

This video tutorial is included in our set on Building and Processing Forms with SharePoint Server 2013. This set is available to any/all subscribers to SharePoint-Videos.com. The set can also be purchased for local viewing by individuals or groups of users.

The important takeaways from this class include understanding InfoPath 2013 as another in the set of tools offered by Microsoft built on the XML scripting language. As such, there is a “weight” to any InfoPath form, which administrators, in particular, need to manage to ensure top performance of the server in a forms processing environment. As we make clear in this video, poorly architected InfoPath forms can negatively impact on the overall performance of a SharePoint Server 2013 farm.

The intent of the architecture is to enable forms designers and developers to avail of the same Javascript and jQuery tools to limit as much of the interactivity required for forms processing to the client browser as possible. These users need to make best efforts to limit server interaction as much as possible, or risk degradation of farm performance, as we mentioned above.

Some of the important terms administrators should be familiar with include “InfoPath Forms Services” which is the process running on SharePoint Server 2013 to support forms built with this tool. The operation of this service is entirely consistent with earlier versions of it for SharePoint 2010. The instances of true interactivity between any client processing the form and the service running on SharePoint Server 2013 are called “postbacks”. These events need to be kept to a minimum to ensure proper performance of the server.

Ira Michael Blonder

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