Specific problems. Specific fixes.
Written from work we have actually done, which is why there are numbers in them. One article a fortnight, no roundups of other people's links.
Why your Map/Reduce keeps hitting SSS_USAGE_LIMIT_EXCEEDED
Latest · SuiteScript · 9 min readEach one is something we had to work out.
Pick a topic. Every panel shows the problem the article solves.
Cutting NetSuite file cabinet costs without deleting anything
File storage is one of the few NetSuite costs that grows on its own. Archival tiering keeps every document reachable and takes the bill down with it.
7 min readSELECT item, SUM(quantity) FROM transactionline GROUP BY item
SuiteQL or saved search: how to decide, with the governance maths
Both read the same data. They cost very different amounts, and the break-even is not where most people assume.
11 min readWork-order scrap: capturing it where it actually happens
If scrap is entered at month end from a paper sheet, your standard costs are fiction. Capturing it at the operation changes what the GL can tell you.
8 min readThe multi-subsidiary decisions you cannot undo later
Chart of accounts, subsidiary hierarchy and accounting book setup are effectively permanent. Four choices worth arguing about before go-live.
12 min read<#list record.item as line> ${line.item} · ${line.quantity} · ${line.amount} </#list>
Advanced PDF templates: the FreeMarker patterns worth knowing
Six patterns that cover most of what clients ask for in transaction templates, including the page-break behaviour nobody documents.
6 min readOne article a fortnight. No newsletter padding. Just the next thing we worked out, when we work it out.
Considering NetSuite, or already living with it?
Tell us what is not working. If it is a half-hour fix we will tell you that, and you can decide whether to pay anyone at all.