entity
masterThe entity supertype: one row for every customer, vendor, employee, partner, contact, project and group, with pointer columns to the concrete record and a type discriminator.
A real queryable record, not a UI abstraction — it is the cheapest way to resolve transaction.entity to a name without knowing which subtype you are looking at. It carries no subsidiary or currency: those live on the concrete customer/vendor records and their subsidiary-relationship bridges.
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
17 fields · 1 key
17 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | id | Internal ID | NUMBER | Primary-key field |
| 2 | entityid | Entity ID | VARCHAR | |
| 3 | entitytitle | Name/ID as displayed | VARCHAR | |
| 4 | altname | Name | VARCHAR | |
| 5 | entitynumber | Entity number | NUMBER | |
| 6 | type | Entity type discriminator (multiselect) | VARCHAR | |
| 7 | isperson | Individual rather than a company | VARCHAR | |
| 8 | isinactive | Inactive | VARCHAR | |
| 9 | datecreated | Date created — note the column is datecreated here, not createddate | TIMESTAMP | |
| 10 | lastmodifieddate | Last modified — the incremental watermark | TIMESTAMP | |
| 11 | parent | Parent entity (internal id) | NUMBER | |
| 12 | toplevelparent | Top-level parent entity (internal id) | NUMBER | |
| 13 | customer | Customer record this entity resolves to (internal id) | NUMBER | |
| 14 | vendor | Vendor record this entity resolves to (internal id) | NUMBER | |
| 15 | employee | Employee record this entity resolves to (internal id) | NUMBER | |
| 16 | group | Group record this entity resolves to (internal id) | NUMBER | |
| 17 | externalid | External ID | VARCHAR |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the Connect-landed copy of entity on Databricks — dates are real DATE/TIMESTAMP columns and need no conversion, and the partition anchors are already in place. The lastmodifieddate watermark is in place too. Set your Unity Catalog location, schema, and filter values below; they’re substituted into the SQL and the copy button.
4 parameters not filled: <catalog>, <schema>, <id>, <watermark>
-- ============================================================
-- Table : entity — The entity supertype: one row for every customer, vendor, employee, partner, contact, project and group, with pointer columns to the concrete record and a type discriminator.
-- Purpose: Column-selected read of entity — auto-generated from field metadata
-- Grain : One row per id
-- 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.id AS "Internal ID",
t.entityid AS "Entity ID",
t.entitytitle AS "Name/ID as displayed",
t.altname AS "Name",
t.entitynumber AS "Entity number",
t.type AS "Entity type discriminator (multiselect)",
t.isperson AS "Individual rather than a company", -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
t.isinactive AS "Inactive", -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
t.datecreated AS "Date created — note the column is datecreated here, not createddate",
t.lastmodifieddate AS "Last modified — the incremental watermark",
t.parent AS "Parent entity (internal id)",
t.toplevelparent AS "Top-level parent entity (internal id)",
t.customer AS "Customer record this entity resolves to (internal id)",
t.vendor AS "Vendor record this entity resolves to (internal id)",
t.employee AS "Employee record this entity resolves to (internal id)",
t.`group` AS "Group record this entity resolves to (internal id)",
t.externalid AS "External ID"
FROM <catalog>.<schema>.entity t
WHERE
1 = 1 -- no partition column on this record; the filters below are optional
-- AND t.id = <id>
-- AND t.lastmodifieddate >= TIMESTAMP '<watermark>' -- inserts and updates only — deletes never appear here; diff deletedrecord, which is itself blind to line-level deletes (see quirks #deletes)
ORDER BY t.id;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 transaction.entity = entity.idON entity.customer = customer.idON entity.vendor = vendor.idON pricing.customer = entity.idON fulfillmentrequest.entity = entity.idON fulfillmentrequest.createdby = entity.idON fulfillmentrequest.lastmodifiedby = entity.idON systemnote.name = entity.idON budgets.customer = entity.id
More Entities tables
- vendorThe vendor master: identity, terms, incoterm, credit limit and payables balances in both the vendor's primary currency and the base currency.
- vendorsubsidiaryrelationshipThe OneWorld vendor bridge: one row per vendor per subsidiary, with payables, in-transit and unbilled balances in both the relationship currency and the base currency, plus the per-subsidiary credit limit.
- customerThe customer master: identity, status, terms, credit control and the entity-level balance rollups, plus the sales-history date stamps.
- customersubsidiaryrelationshipThe OneWorld customer bridge: one row per customer per subsidiary the customer is shared with, carrying that subsidiary's receivable, deposit and unbilled-order balances.