Skip to content
NetSuite Reference

entity

master

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.

Module: EntitiesNo partition column
Notes

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.

Structural facts — how the record is partitioned, not a trap by itself

Subsidiary-scoped
The record carries a subsidiary column 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 location column — an org segment in NetSuite before it is a warehouse — and the generated SQL anchors it the same way.

Join & extract hazards — verify before you rely on this

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.
In field listings, the Key chip marks a primary-key field, and the T/F chip marks a check-box column Connect returns as a 'T'/'F' string.

Fields

17 fields · 1 key

17 fields.

Table fields: position, field name, description, data type, and flags. 17 fields.
#FieldDescriptionTypeFlags
1idInternal IDNUMBER
Primary-key field
2entityidEntity IDVARCHAR
3entitytitleName/ID as displayedVARCHAR
4altnameNameVARCHAR
5entitynumberEntity numberNUMBER
6typeEntity type discriminator (multiselect)VARCHAR
7ispersonIndividual rather than a companyVARCHAR
8isinactiveInactiveVARCHAR
9datecreatedDate created — note the column is datecreated here, not createddateTIMESTAMP
10lastmodifieddateLast modified — the incremental watermarkTIMESTAMP
11parentParent entity (internal id)NUMBER
12toplevelparentTop-level parent entity (internal id)NUMBER
13customerCustomer record this entity resolves to (internal id)NUMBER
14vendorVendor record this entity resolves to (internal id)NUMBER
15employeeEmployee record this entity resolves to (internal id)NUMBER
16groupGroup record this entity resolves to (internal id)NUMBER
17externalidExternal IDVARCHAR

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.

Query parameters

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

  • transactionentityforeign key · N:1
    ON transaction.entity = entity.id
  • entitycustomerforeign key · 1:1
    ON entity.customer = customer.id
  • entityvendorforeign key · 1:1
    ON entity.vendor = vendor.id
  • pricingentityforeign key · N:1
    ON pricing.customer = entity.id
  • fulfillmentrequestentityforeign key · N:1
    ON fulfillmentrequest.entity = entity.id
  • fulfillmentrequestentityforeign key · N:1
    ON fulfillmentrequest.createdby = entity.id
  • fulfillmentrequestentityforeign key · N:1
    ON fulfillmentrequest.lastmodifiedby = entity.id
  • systemnoteentityforeign key · N:1
    ON systemnote.name = entity.id
  • budgetsentityforeign key · N:1
    ON budgets.customer = entity.id

Browse more Entities tables

More Entities tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle or NetSuite. NetSuite is a registered trademark of Oracle and/or its affiliates.