customersubsidiaryrelationship
controlSubsidiary-scopedThe OneWorld customer bridge: one row per customer per subsidiary the customer is shared with, carrying that subsidiary's receivable, deposit and unbilled-order balances.
Browser page name is CustomerSubsidiaryRelationship (PascalCase); the analytics id is lowercase. isprimarysub marks the customer's home subsidiary — the row most reports mean when they say "the customer's subsidiary".
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
10 fields · 3 key
10 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | id | Internal ID | NUMBER | Primary-key field |
| 2 | entity | Customer (internal id) | NUMBER | Primary-key field |
| 3 | subsidiary | Subsidiary (internal id) | NUMBER | Primary-key field |
| 4 | isprimarysub | The customer's primary subsidiary | VARCHAR | |
| 5 | primarycurrency | Currency for this relationship (internal id) | NUMBER | |
| 6 | balance | Receivable balance for this subsidiary | NUMBER | |
| 7 | depositbalance | Customer deposits held by this subsidiary | NUMBER | |
| 8 | unbilledorders | Unbilled orders for this subsidiary | NUMBER | |
| 9 | name | Relationship name (unlabeled on the browser page) | VARCHAR | |
| 10 | externalid | External ID | VARCHAR |
Field provenance: hand-curated. 3 key fields.
Boilerplate SQL
Starting point for reading the Connect-landed copy of customersubsidiaryrelationship 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.
5 parameters not filled: <catalog>, <schema>, <subsidiary_id>, <id>, <entity>
-- ============================================================
-- Table : customersubsidiaryrelationship — The OneWorld customer bridge: one row per customer per subsidiary the customer is shared with, carrying that subsidiary's receivable, deposit and unbilled-order balances.
-- Purpose: Column-selected read of customersubsidiaryrelationship — auto-generated from field metadata
-- Grain : One row per id + entity + subsidiary
-- 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.entity AS "Customer (internal id)",
t.subsidiary AS "Subsidiary (internal id)",
t.isprimarysub AS "The customer's primary subsidiary", -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
t.primarycurrency AS "Currency for this relationship (internal id)",
t.balance AS "Receivable balance for this subsidiary",
t.depositbalance AS "Customer deposits held by this subsidiary",
t.unbilledorders AS "Unbilled orders for this subsidiary",
t.name AS "Relationship name (unlabeled on the browser page)",
t.externalid AS "External ID"
FROM <catalog>.<schema>.customersubsidiaryrelationship t
WHERE
t.subsidiary = <subsidiary_id> -- OneWorld partition — see quirks guide #oneworld
-- AND t.id = <id>
-- AND t.entity = <entity>
-- no lastmodifieddate on this record — there is no watermark column, so incremental extraction must full-refresh it (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 customer.id = customersubsidiaryrelationship.entityON customersubsidiaryrelationship.subsidiary = subsidiary.idON customersubsidiaryrelationship.primarycurrency = currency.id
More Entities tables
- entityThe 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.
- 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.