Most of these notes started as questions that kept coming back at work — why the integration returns 401, why a script stops halfway through, why the numbers in a report refuse to tie out. Written down so the answer does not have to be rediscovered each time.
29 of 29 notes
Postman is where you call an API without writing an application first. Its real value is proving whether the problem sits in the source system, in the network, or in your own code.
The three features that turn Postman from a scratchpad into integration documentation a whole team can actually reuse.
Why an integration returns 401 when the credentials look correct — and the difference between a token you paste into a header and a signature recomputed on every request.
The status code is your first clue about who has to fix it: the side that sent the request, or the side that received it. Misreading it means escalating to the wrong team.
An order of investigation that narrows the problem space systematically, so you are not guessing when data fails to arrive in the target system.
A map of Laravel's parts and the order a request travels through them, so logic ends up where it belongs rather than wherever it happens to work.
How modern Next.js splits work between server and browser, plus several version 16 rules that differ from the older tutorials still circulating.
How to arrange the two frameworks as one system, what separating them actually costs, and when not to separate them at all.
An ERP is not one large application but a set of modules sharing a single database. Understanding the split explains why one transaction moves numbers across many reports.
The chain from needing something to money leaving the company, and the matching mechanism that stops a business paying for goods it never received.
The chain from a customer order to money actually received, and how an A/R Aging report reads the health of receivables out of the same data.
The work that actually starts once an Invoice or Vendor Bill is recorded — credit control, collection, payment scheduling, and the reconciliation that keeps the sub-ledger equal to the general ledger.
The four script types you will use most, when each of them runs, and why choosing the wrong one makes your logic feel like it never executes.
NetSuite caps how much work a single script execution may do. Understanding that cap explains errors that only appear once the data has grown.
The error codes that come up most while developing on and integrating with NetSuite, what each one means, and where to look for the detail.
Two ways of retrieving NetSuite data with different characters. The right choice decides whether a report can be maintained by the business or depends on a developer forever.
The full document chain — Work Order, Assembly Build, Item Receipt, Sales Order, Item Fulfillment, Invoice, Deposit — and what each step changes in stock and in the ledger.
What actually happens in the ledger when a transaction is saved, the debit and credit rules underneath it, and a journal-impact table for the transactions used most.
The four core reports, the question each one answers, how they connect to each other, and the order to investigate in when the numbers do not tie.
Item types, the transactions that move stock, and how a costing method determines inventory value and cost of goods sold — including a decision that is hard to undo after go-live.
What the CRM module actually does, how one record moves from Lead to Customer, and the point at which sales activity starts touching financial numbers.
What Coretax DJP is, the change in tax identity it brings, and the practical consequences for master data and transactions in an ERP such as NetSuite.
Setting up the SuiteCloud CLI and the VS Code extension, pulling files and objects from the account down to your machine, then sending them back — plus the setup errors that block people most often.
How to investigate when an account does not appear in the revaluation results — starting with the question people skip: should that account be revalued at all?
A map of the databases in common use and what each is like — plus one term that is confused more than any other: SQL is a language, not the name of a database.
From the connection string to the choice between an ORM and raw queries, plus two things that cannot be skipped: credentials that do not leak, and queries that cannot be injected into.
The difference between the JOIN types, and why picking the wrong one makes a report lose rows without raising a single error.
An index makes lookups fast the same way a table of contents does — including the consequence: adding pages becomes more work.
Why changes to financial data must be grouped into a single transaction, and what the database guarantees when the process fails halfway through.
Postman & API
The tools and ideas to have straight before touching an integration.
3 notes
Error & Debugging
Reading an error message and tracing it back to the root cause.
2 notes
Web & Framework
Laravel, Next.js, and how the two are assembled into one system.
3 notes
ERP Fundamentals
The business processes the system was built to serve.
4 notes
NetSuite
SuiteScript, governance, financials, and getting data out.
12 notes
SQL & Database
Queries, indexes, and the integrity of transactional data.
5 notes