Short posts on script visibility, custom record sprawl, ERP handoffs, and making NetSuite knowledge easier to trust.
A NetSuite cleanup spreadsheet can look very convincing. Old custom fields. Inactive-looking scripts. Saved searches nobody remembers. Workflows with names from three consultants ago. It is tempting to…
Read note →Some NetSuite scripts only look risky during close. A scheduled billing cleanup job can run fine on the 3rd, 11th, and 18th. Then close starts, volume jumps, queues…
Read note →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…
Read note →A SuiteScript governance error is usually the first visible symptom, not the whole problem. The units matter. You still have to know which API calls are expensive, which…
Read note →The morning after a NetSuite deploy is usually when the questions start. Someone changed workflow criteria. A script was pushed. A custom field was updated. A saved search…
Read note →APM, NetSuite’s Application Performance Management tool, can tell you which script is slowing down a transaction. That is useful. It is not enough. APM helps you spot execution…
Read note →A lot of NetSuite change review meetings start with everyone opening their own tabs. System Notes. Deployment notes. Jira tickets. Saved searches. Old Slack threads. Maybe a spreadsheet…
Read note →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…
Read note →The NetSuite script I worry about is not always the one throwing errors. It's the one that still runs every day, looks mostly fine, but nobody remembers why…
Read note →Why NetSuite docs decay, and why keeping them close to the live account matters.
Read note →