There's a limit (70) to the number of form fields you can have on a custom list form. Does anyone know what this count includes? I am wondering whether I can stay under the limit by replacing some editable fields with xsl:value-of or by setting the FormField's ControlMode to "Display". There are some items that need to be shown on the edit form but not actually edited.

2 Answers 2


70 fields on one form does not sound like a great user experience. You may want to re-think your data architecture.

Other discussions show that exceeding the limit will result in a stack overflow error. Even a field that is just displayed would need to be on the stack, so the display mode will probably not help much.

In any case, why don't your try it out yourself? Create some data in an Excel file and import that as a list, edit the form with SP Designer and see what works and what doesn't.

InfoPath does not have this limitation, so customizing the form with IP is an alternative. You can then also use a tabbed interface to improve the UX.

You really don't want to throw a page with 70 fields at a user.

Edit: With the information provided in the comments it seems that you have a parent/child (or master/detail) relationship and try to pack it all into one list instead of building a normalized database structure. Parent/child relationships can be set up in SharePoint, too. You don't need to create dozens of fields to store the detail data for a master record.

You need a master list with a unique ID and a detail list where the Master ID is assigned to the new list items to define the relationship. In the Master List you can customize the display form to contain a list view of the related items in the Detail list and a link to add new items to that detail list. A little bit of JavaScript will ensure that a new item in the Detail list gets the Master item's ID assigned automatically.

Clear as mud? The SharePoint Hillbilly has a video tutorial for 2007 and 2010.

If you go through the material (the 2007 stuff is good to understand the approach), you'll find that there are two techniques, one using SharePoint Designer, the other one without SPD.

It is entirely doable to create relationships to several different detail lists, if required.

  • This application requires ~150 list fields. Previously, they were using InfoPath with collapsible sections, so the form was much nicer. However, corporate has decided to eliminate all enterprise features, so no more IP. I'm working with the users to see how we can break up the data entry on multiple forms.
    – wbco
    Commented Jun 19, 2014 at 19:51
  • To clarify, most of these fields are in repeating groups, with the vast majority of list items having < 4 groups filled in, so users will very seldom have to scroll down the form.
    – wbco
    Commented Jun 19, 2014 at 20:02
  • See my edits for master/detail techniques.
    – teylyn
    Commented Jun 19, 2014 at 21:42
  • I have done master-detail before and am still considering it for this app. We do have some complex workflows on this one, which coul be extra fun if dealing with multiple items and lists. However, since there's apparently no simple answer to my query, guess I'll just have to undergo some pain. Thanks for the information.
    – wbco
    Commented Jun 19, 2014 at 22:07

There is a limit of 70 fields (67 fields plus one attachment field, one created by field and one modified by field) on custom forms. The limit can be overcome by instead customizing a list form with an InfoPath 2010 form.


I think use the InfoPath form But I think time to redesign the form in different tool Access / SQL as InfoPath is also retiring.

  • InfoPath support will exist for nearly 10 years and Microsoft is still saying to use InfoPath, it is still a viable option. Commented Jun 19, 2014 at 4:43
  • You are right it here for another 10 years, But we are on last version of it...i dont know but MSFT Folks told us to move other alternates... it is mix feeling stuff.
    – Waqas Sarwar MVP
    Commented Jun 19, 2014 at 4:46
  • Yes, well aware of the limitation, which I actually stated in my original question...but we can't use InfoPath any more.
    – wbco
    Commented Jun 19, 2014 at 19:54

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.