What is the usage scenario's for using a dedicated Form library instead of using a custom list as where you modify the data entry form with InfoPath?

Is it if you want the added functionality you get when using the installed client instead of the web version (in SP Ent. Ed)?

In my head I would probably create a list for most cases as they are easier to work with, and I don't have to deal with adding the InfoPath logic of generating unique filenames for the form submissions.

I hope someone can enlighten me a nit here :)

1 Answer 1


A form library generates XML documents for each entry. Whereas a custom list is simply list data with you custom entry form. Having the documents are useful of you want to interact with the forms outside of Sharepoint or if you want I do anything that isnt available in a custom list (ie. signatures).

  • I know it generates an xml file. And using the forms outside of SharePoint is something I would try to avoid. Web UI's are easier for most people and covers most cases. Could you elaborate on the signatures part? Oct 7, 2011 at 6:29
  • When you customize the entry form for a SP list, you can only store values that have a corresponding SharePoint field type. With signatures, for example, they cannot be stored in a SP column and would be retained only in the XML InfoPath file on a forms library. Same goes for attachments inside the form or any other non-text content. Oct 7, 2011 at 15:37

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.