Form vs List Library SharePoint 2013

2
ASPX forms InfoPath List Forms Basics Form cannot be printed Form cannot be printed Form can be printed Data cannot be saved as draft Data cannot be saved as draft Document can be saved as draft Coding Support Client and server side code support No client or server side code support Form Design CSS can be applied No CSS support No CSS support Data Data can be changed or imported into the list in bulk Multiple data sources can be used Multiple data sources can be used Managed Meta data can be mapped to fields Can NOT use Managed Meta data Can NOT use Managed Meta data Form Functionality Multiple views of data cannot be created Validation Rule engine does it all Rule engine does it all Workflow InfoPath Documents Separate forms for display, edit and new items. Forms simply work on whatever data is in the list. Single form works for all operations. Like aspx forms, this form works on whatever data is in the list. Each list/data item is a document itself. Documents can be configured to promote fields to library columns Only server side code support, it uses XMLHttp in order to avoid full page postbacks during data entry. Data can be changed or imported into the list in bulk Only existing data in promoted fields can be modified. Records cannot be added or deleted in bulk. Multiple data sources are not supported unless they are in the form of lookup columns or used in client or server side code Can use external data through client or server side code Can consume simple SOAP and REST based services and can have connections to databases and XML files Can consume simple SOAP and REST based services and can have connections to databases and XML files No built in support for cascading drop downs, this functionality is achieved using JavaScript Cascading drop downs can be created without code Cascading drop downs can be created without code Multiple view of data CAN BE created and switched based on rules Multiple view of data CAN BE created and switched based on rules Multiple web part can be added to the form, inline editing of records possible Data can be shown from multiple data sources, but can’t be changed Data can be shown from multiple data sources, but can’t be changed JavaScript for all the rules and client side validation

description

Difference between SharePoint 2013 Forms and List Library

Transcript of Form vs List Library SharePoint 2013

Page 1: Form vs List Library SharePoint 2013

ASPX forms InfoPath List FormsBasics

Form cannot be printed Form cannot be printed Form can be printedData cannot be saved as draft Data cannot be saved as draft Document can be saved as draft

Coding Support

Client and server side code support No client or server side code support

Form DesignCSS can be applied No CSS support No CSS support

Data

Data can be changed or imported into the list in bulk

Multiple data sources can be used Multiple data sources can be used

Managed Meta data can be mapped to fields Can NOT use Managed Meta data Can NOT use Managed Meta data

Can use external data through client or server side code

Form Functionality

Cascading drop downs can be created without code Cascading drop downs can be created without code

Multiple views of data cannot be created

InfoPath Documents

Separate forms for display, edit and new items. Forms simply work on whatever data is in the list.

Single form works for all operations. Like aspx forms, this form works on whatever data is in the list.

Each list/data item is a document itself. Documents can be configured to promote fields to library columns

Only server side code support, it uses XMLHttp in order to avoid full page postbacks during data entry.

Data can be changed or imported into the list in bulk

Only existing data in promoted fields can be modified. Records cannot be added or deleted in bulk.

Multiple data sources are not supported unless they are in the form of lookup columns or used in client or server side code

Can consume simple SOAP and REST based services and can have connections to databases and XML files

Can consume simple SOAP and REST based services and can have connections to databases and XML files

No built in support for cascading drop downs, this functionality is achieved using JavaScript

Multiple view of data CAN BE created and switched based on rules

Multiple view of data CAN BE created and switched based on rules

Page 2: Form vs List Library SharePoint 2013

ValidationJavaScript for all the rules and client side validation Rule engine does it all Rule engine does it all

Workflow

Key Benefits

Maximum control on the form Easy to develop and relatively less testing is required

JavaScript/JQuery and Server side code support Can be developed with minimum time and effort Server side code support

CSS Support

Data in the list can be edited, imported and exported in bulk Repeating and nesting data support

Drawbacks

Increased development and testing time No Coding support

Can run in Sandbox

Multiple web part can be added to the form, inline editing of records possible

Data can be shown from multiple data sources, but can’t be changed

Data can be shown from multiple data sources, but can’t be changed

SPD based list and reusable workflows and VS based custom workflows can be created and attached

SPD based list and reusable workflows and VS based custom workflows can be created and attached

SPD based list and reusable workflows and VS based custom workflows can be created and attached. Only promoted fields can be used in SPD based workflows.

Very easy to develop and very little testing is required

InfoPath Views, Rules and facial features are supported

All InfoPath features like Views, Rules, facial features and printing are supported

Data in the list can be edited, imported and exported in bulk

Multiple web parts can be used on a form to view or modify items from different lists on a single form

No client side coding support, limited server side code ability