A custom field cleanup sounds harmless until the field turns out to be part of how finance actually runs the business.
Maybe it is an approval threshold. Maybe a SuiteScript checks it before routing invoices. Maybe a saved search pulls it into a controller’s month-end review. Maybe it became audit evidence three years ago and nobody remembers who made that decision.
A script reference or saved search result helps you see where the field is touched. That matters. But it still does not always explain what breaks politically, operationally, or financially when the field changes.
Before hiding, renaming, or deleting an important NetSuite field, I’d want to know:
- What scripts, workflows, searches, reports, and integrations reference it?
- Is it tied to approvals, controls, or audit support?
- Who depends on it without realizing they do?
That is the kind of context CSDocs keeps current. The map and its change impact show which scripts and workflows set a field and when, so a field is not just a label and an internal ID — you can see where it matters.