Long-reads on NetSuite craft from the team building MokuBot. Saved search formulas, SuiteScript governance, and the parts of NetSuite that are not in the documentation.
The AP Aging report and the accounts payable balance on the balance sheet disagree, and the difference is not a missing bill. Three specific traps in how NetSuite stores payables, and the SuiteQL…
Read the article →NetSuite 2026.2 is putting legacy SuiteScript versions on notice. Here is what the update changes, what it does not change, and how to inventory scripts before migration.
Read the article →The thing you built in sandbox is never one file. It is a file, a script record, a deployment, two custom fields and a saved search, and internal IDs do not survive the trip. A manifest-driven way to…
Read the article →Two developers edit the same SuiteScript file in the NetSuite File Cabinet. The second save silently destroys the first, with no warning, no history and no way to recover. Here is why it happens and…
Read the article →The native File Cabinet editor is a textarea. MokuStudio is the VS Code engine running in the browser against the live File Cabinet of the account you are signed in to, with real IntelliSense over…
Read the article →Three architectures for putting an AI agent into NetSuite, what each one can read, which role it acts under, and the audit trail problem that none of the product pages mention. A checklist for…
Read the article →Field Explorer tells you what a field is called. MokuBot uses the field. An honest comparison of the two, including where Field Explorer is still the better tool.
Read the article →Governance units are a per-execution budget, not a rate limit. The arithmetic that decides whether your SuiteScript survives, and the four substitutions that buy back the most headroom.
Read the article →Field IDs, NULL propagation, main line, and the difference between Criteria, Results and Summary. The parts of NetSuite saved search formulas that fail quietly, and how to read the failure.
Read the article →