A user opens a ticket:
“NetSuite is saying this field is required, but it wasn’t yesterday.”
The tempting answer is to check the field setup page and look for the Mandatory box.
That’s worth checking. It’s sometimes it's not enough.
In a mature account, required behavior can come from the form, a workflow, a client script, a user event, a role difference, sourcing behavior, or a bundle someone installed six months ago.
So before you tell finance “try it now,” the better questions are:
- What touches this field?
- What changed recently?
- What breaks if we relax it?
System Notes can help with the timeline. They usually don’t explain intent, dependencies, or downstream side effects though.
This is one of the reasons CSDocs maps which scripts and workflows touch each field, and flags what changed this week. An admin shouldn’t have to reconstruct all of that from memory.
If your NetSuite account needs this kind of map, CSDocs is here: getcsdocs.com