systemnote
transactionThe field-level change log: one row per record, field and change, with who changed it, in what context, and the old and new values as text.
Browser page name is SystemNote. The grain is one row per logged CHANGE, not one per record: recordid repeats as often as a record is edited, so it is authored as a pointer rather than a key and any per-record read has to aggregate or pick a change. Old and new values are display TEXT, not typed values, so numeric comparison means casting. The newer store, systemnote2, keeps the same history with TYPED old/new value columns — check which one your account populates before building an audit report on either.
What the badges mean
- master
- Data class: what the record holds — master data, transaction documents, control/configuration, or a documented convenience record. NetSuite has no product-family or schema axis, so this is the whole classification.
- Subsidiary-scoped
- The record carries a
subsidiarycolumn that partitions its rows, so the generated SQL anchors it. On a few records the column is a multiselect rather than a scalar foreign key — the table notes say which (see the quirks guide). - Location-scoped
- The record carries a
locationcolumn — an org segment in NetSuite before it is a warehouse — and the generated SQL anchors it the same way. - View
- A documented convenience record rather than a stored one. Land the records it stands in for instead of assuming it extracts as-is — the table notes say where the rows actually live.
Structural facts — how the record is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
'T'/'F' string.Fields
11 fields
11 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | recordid | Internal id of the record that changed — repeats once per logged change | NUMBER | |
| 2 | recordtypeid | Record type that changed (internal id) | NUMBER | |
| 3 | record | Record as displayed | VARCHAR | |
| 4 | field | Field that changed (internal id) | NUMBER | |
| 5 | oldvalue | Old value, as display text | VARCHAR | |
| 6 | newvalue | New value, as display text | VARCHAR | |
| 7 | date | When the change was made | TIMESTAMP | |
| 8 | name | Entity who made the change (internal id) | NUMBER | |
| 9 | role | Role used (internal id) | NUMBER | |
| 10 | context | Context the change came from (internal id) — UI, CSV, script | NUMBER | |
| 11 | type | Note type (internal id) | NUMBER |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading the Connect-landed copy of systemnote on Databricks — dates are real DATE/TIMESTAMP columns and need no conversion, and the partition anchors are already in place. This record carries no modification stamp, and the snippet says so where the watermark would otherwise go. Set your Unity Catalog location, schema, and filter values below; they’re substituted into the SQL and the copy button.
2 parameters not filled: <catalog>, <schema>
-- ============================================================
-- Table : systemnote — The field-level change log: one row per record, field and change, with who changed it, in what context, and the old and new values as text.
-- Purpose: Column-selected read of systemnote — auto-generated from field metadata
-- Grain : One row per record — see the Fields section for the full key
-- Notes : Auto-generated skeleton for NetSuite data landed in your lakehouse from a SuiteAnalytics Connect (or SuiteQL) extract — it never addresses live NetSuite. Identifiers are lowercase as NetSuite2.com renders them. Select-type columns hold numeric internal ids: BUILTIN.DF() display resolution exists only at extraction time, so decode ids by joining the landed list records; see quirks #display-values. Check-box columns arrive as 'T'/'F' strings; see quirks #tf-booleans.
-- ============================================================
SELECT
t.recordid AS "Internal id of the record that changed — repeats once per logged change",
t.recordtypeid AS "Record type that changed (internal id)",
t.record AS "Record as displayed",
t.field AS "Field that changed (internal id)",
t.oldvalue AS "Old value, as display text",
t.newvalue AS "New value, as display text",
t.date AS "When the change was made",
t.name AS "Entity who made the change (internal id)",
t.role AS "Role used (internal id)",
t.context AS "Context the change came from (internal id) — UI, CSV, script",
t.type AS "Note type (internal id)"
FROM <catalog>.<schema>.systemnote t
WHERE
1 = 1 -- no partition column on this record; the filters below are optional
-- no lastmodifieddate on this record — there is no watermark column, so incremental extraction must full-refresh it (see quirks #deletes)
;Verified August 2026 · Analytics Browser 2021.1 · corroborated 2025.2
Select columns hold internal ids, not display text — see decoding display values.
Relationships
Diagram of 1-hop neighbors — join details below. Document-link edges are highlighted; they chain one document to the next and are the joins newcomers most often get wrong.
Join details
ON systemnote.name = entity.id
More Platform tables
- systemnote2The second-generation change log: the same field-level history as systemnote, but with the old and new values split into typed columns — string, numeric, date, boolean and reference — beside a UTC change timestamp.
- deletedrecordThe deletion ledger: one row per deleted record with its type, name, script id, who deleted it and when. The only public evidence that something disappeared.