One record per real customer, assembled from the ERPs, the CRM and the portals, with every source key kept.
Delta tables are read in place through Unity Catalog with filters and aggregates pushed down; nothing is copied out.
| Object | Read from | Fields the domain uses | Freshness |
|---|---|---|---|
| Customer | silver.customer | customer_key · source_system · source_id · name · country · vat_id · postcode | as fresh as the landing pipeline; live for governed tables |
| Sales order | silver.sales_order · silver.sales_order_line | order_id · customer_key · order_date · net_value · status | as fresh as the landing pipeline; live for governed tables |
| Invoice | silver.ar_invoice | invoice_id · customer_key · due_date · open_amount | as fresh as the landing pipeline; live for governed tables |
The first object above carries the strong keys; the standardised attributes come from the same rows. Two records match when a strong key agrees, or when name and address agree closely and no strong key disagrees.
Golden records and their history are written with MERGE INTO into a governed catalog, registered in Unity Catalog with lineage.
| Interface | Used for | Result |
|---|---|---|
MERGE INTO gold.customer on the golden key; history in gold.customer_history; registered in Unity Catalog | golden values approved for write-back: identity; addresses; contacts and roles | the id or error Databricks returns, stored beside the change |
Write-back is off per object until a test write succeeds, and approval rules can require a person per object. Reconciliation compares the source row with the golden value on a schedule.
Unity Catalog grants and row filters are honoured; Lima adds its own layers on top.
Customer on
Other domains on Databricks
The golden record reads the objects above in place. History the pivot needs at scale is landed in your lake by the Backbone, under the same keys, security and audit.
Grant the read access and the write interfaces listed above and agree the refresh method. Nothing is installed in Databricks.
Yes. Write-back stays off per object until a test write succeeds; the golden view, the API and the pivots work from day one on reads.
Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.
