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.
NetSuite 2026.2 lets REST list and run saved searches. It cannot add filters or change sorting per request, which breaks many SOAP-era search integrations.
Read the article →NetSuite 2026.2 adds Use Usage Amount Only, so a third-party platform can price usage. The usage record takes no scripts, so the dedup lives outside it.
Read the article →NetSuite 2026.2 switched the default sort for transaction SuiteQL from tranDisplayName to tranDate. Nothing errors, and paged reads break quietly.
Read the article →Oracle's SuiteScript upgrade skill maps 1.0 calls to 2.1. The conversions worth reviewing are the ones that compile, deploy, and quietly change behavior.
Read the article →What 2027.1 blocks, when SOAP endpoints actually go dark, and how to separate the authentication migration from the API migration.
Read the article →NetSuite 2026.2 controls NetSuite Next and Ask Oracle by role. What the three access modes mean, and what runtime.isNextActive() does not tell you.
Read the article →Oracle is pushing customers toward SuiteScript 2.1 with an AI migration skill. What the tool actually does, what it cannot do, and what the warning means.
Read the article →NetSuite 2026.2 adds Event Subscriber scripts for asynchronous work after a record event. How they differ from User Events, and where the design bites.
Read the article →How many NetSuite AI Units a license includes, how the pool is shared, what each feature costs to run, and why the AI Connector does not consume any of them.
Read the article →SOAP dies in 2028.2. A phased plan for teams with real integrations: inventory, auth, records, searches, and the gaps that still have no clean answer.
Read the article →