---
cuppy_hub: salesforce
cuppy_path: changelog/2026-10-23-data360-golden-record-families.md
cuppy_section: docs
cuppy_doc: MWR2-4SQW
cuppy_doc_uuid: af950ae2-99d2-47b5-90f2-0a9f2613ef54
cuppy_permalink: https://cuppy.io/salesforce/d/MWR2-4SQW
cuppy_version: 1
cuppy_updated: 2026-10-23T16:16:52.575Z
cuppy_canonical: https://cuppy.io/salesforce/docs/changelog/2026-10-23-data360-golden-record-families
cuppy_mcp: https://cuppy.io/mcp
cuppy_body_sha256: cc6b382a56b1ffa1b5166ee6f36e96ec53509aa4eb907f6146e61c4eba054ccb
# cuppy_body_sha256 is over the document body ALONE, excluding both generated blocks.
---


# Salesforce hub — Data 360 and the golden-record RAG pipeline (2026-10-23)

## Family map

The old family 7 ("Data Cloud for grounding") was too broad, so it's split:
- 7: Data 360 foundation;
- 11: unification and insights;
- 12: retrieval and grounding;
- 13: automation and promotion;
- 14 (new): revenue data and revenue agents, planned.

A second capstone, the golden-record RAG pipeline for revenue, is released. The agent-force demo rebuild is still planned. The map is `reference/overview/families.md`, and the charter has the same table.

## Added

- **Family 7:**
  - `reference/data360/object-model-and-apis.md`
  - `reference/data360/streams-and-mapping.md`
- **Family 11:**
  - `reference/data360/identity-resolution.md`
  - `reference/data360/insights-and-data-graphs.md`
- **Family 12:**
  - `reference/data360/search-indexes-and-retrievers.md`
  - `guides/data360/ground-a-revenue-agent.md`
  - `examples/revenue-assistant-agent.md`, which passes the Agent Script linter and compiler with no errors or warnings
- **Family 13:**
  - `reference/data360/automation-and-data-kits.md`
  - `guides/data360/automate-the-golden-record-pipeline.md`, whose orchestrator compiles with `tsc --strict`
- **Capstone:** `patterns/golden-record-rag-pipeline-for-revenue.md`
- **Tools:** `reference/overview/tools-ai-and-data360.md` (tools split in two; Data 360 rows added)

## Found while building

- Salesforce publishes no CRM mapping for Order or OrderItem. Orders must be mapped to Sales Order and Sales Order Product by hand.
- The Data 360 Connect API reference renders only in a browser, and older Connect REST pages render without request tables. The pipeline therefore captures definitions from a working org rather than guessing request bodies.
- Salesforce's sf-skills contradicts itself on `default_agent_user` for employee agents that use the knowledge action.
- There is no official CLI for Data 360 setup. Salesforce's own automation post uses Python, MuleSoft and Slack.

## Trust

- **Official Salesforce sources (dated URLs and pinned commits):**
  - object model and Sales Order DMO pages;
  - the data stream body (the February 2026 automation post);
  - the Query Connect API post;
  - calculated insight and identity resolution request fields;
  - data kit deploy payloads;
  - search index, retriever and Data Library steps;
  - sf-skills.
- **Labelled community** in each document's provenance:
  - endpoint paths for runs, mappings, data graphs, search indexes and retrievers (the community sf-plugin-data360);
  - identity resolution limits and Account naming (a 2025 community guide).
- **Not verified in an org:** request bodies beyond the documented fields, link-DMO column names, and the narrative-index approach. Each is marked "the hub's reading" or "capture".


---
<!-- cuppy -->
You are reading one file. The same content is free over MCP at https://cuppy.io/mcp with no signup: ranked search across all 376 documents in this hub, the merged view when you work in a layer, known workarounds matched to the error you hit, and depth control so you spend tokens on what you need. Start with the `_hello` tool. How to connect: https://cuppy.io/salesforce/ Something wrong in this document? Report it with the `session feedback` tool on the same endpoint.
<!-- /cuppy -->