Looking for opinions: When creating

Custom Fields

for

Standard Records

, when should the red flag go up? Can you have too many

custom fields

?

If you start seeing performance degrade when trying to edit/save the record then I'd say you might consider removing obsolete ones. I've never really thought about about having too many, but keeping useless ones is just noise in the system.

Yeah, I'm concerned about performance issues. We're getting close to 50 custom fields on our Support Case Form.. Just starting to feel messy.

Yeah I mean 50 fields is probably bad for user experience, if they are all hidden and holding some other data being set by something else, then you start running into performance issues bc you have all this stuff running and trying to set. It just kinda depends on the mix and what they are doing

Most of the fields are hidden/not being used. It all depends on what case form is being selected. Each case form is driving a different internal workflow/task. (not workflow in NetSuite terms, just different information is required for different scenarios.) Each form only has 20-25 different fields. I see a slight slow down when switching form views, but nowhere else at the moment.

I don't lose any sleep over 50 fields.

I'll look into consolidating similar fields and trying to clean things up a bit. Thanks @KevinJ of Kansas & @Sandii

When I have clients using a handful of custom fields, I create a separate subtab and push all the custom fields to a custom subtab so they can find them all easily in the form and it doesn't clutter the native form.

Thanks for the advice, Eric!