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.
Looking for one specific answer rather than a read? Answers is a page per error message and per behaviour that surprised us.
AP Aging and the payables balance disagree, and it is not a missing bill. Three traps in how NetSuite stores payables, with the SuiteQL that finds each one.
Read the article →What you built in sandbox is a file, a script record, a deployment, two fields and a search, and internal IDs do not survive the move. Use a manifest.
Read the article →Two developers edit the same File Cabinet script. The second save destroys the first, with no warning and no history. Why it happens and how to detect it.
Read the article →The native File Cabinet editor is a textarea. MokuStudio runs the VS Code engine against your live File Cabinet, with IntelliSense over your own modules.
Read the article →Three ways to put an AI agent into NetSuite, what each one can read, which role it acts under, and the audit trail problem the product pages do not mention.
Read the article →Field Explorer reads the record, not the form, which is why the xml=T trick misses fields. What it shows, which forks are maintained, and where it stops.
Read the article →Governance units are a per-execution budget, not a rate limit. The arithmetic that decides whether your script survives, and the four cheapest substitutions.
Read the article →A formula returns one number in Results and another in Summary. Why NULL swallows a CASE, what main line changes, and how to read a quiet failure.
Read the article →