What is the maximum recommended number of Custom Fields?

Whats the maximum recommended number of Custom Item fields? Is there a different max recommend amount for other Custom Fields such as Transactions? Is there a recommended overall total number?

Thanks in advance!

Beginner Asked on November 16, 2019 in Best Practices.
Add Comment
3 Answer(s)

I haven’t ever seen a maximum in any documentation. I have seen accounts with hundreds of custom item fields though and they worked fine without issue. As for transaction fields, I’ve also seen accounts with probably at least 100 custom fields on them, once again with no issue.

There was a thread a few weeks back in NS Pros Slack channel about someone wondering if adding additional fields would add to total memory. It might, but I believe the difference would be negligible. The overall count of records being more cumbersome than the number of fields themselves.

The biggest thing is with hundreds of fields, I would definitely consider having someone manage your forms, as user experience can degrade pretty quickly with busy forms of custom fields scattered all over the place.

Beginner Answered on November 18, 2019.
Add Comment

technically there are no restriction or limit for custom fields, but logically you shouldn’t have 100s of custom field with out any reason or defined business process. Managing them would be a nightmare – think twice before doing so, my 2 cents worth.

Advanced Answered on November 19, 2019.
Add Comment
Best answer

We were worried about this too, as we heavily rely on a Custom Record that has about 800+ fields, and more to be added in future.  Oracle SQL documentation suggests a 1000 column limit, but we tested on sandbox adding more fields to push it beyond 1000 and it didn’t break ….

Beginner Answered on November 20, 2019.
Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.
  • This site made possible by our sponsors:   Tipalti   Celigo   Limebox   Become a Sponsor   Become a Sponsor