Relationships
Records can point to other records (a task belongs to a wedding).
Difficulty 2/5
Plain English
Relationships connect records: a task belongs to a wedding, a message belongs to a conversation. Usually you store the other record's id, not a copy of its whole data. This is how lists stay fast and data stays consistent.
Analogy
A hold slip that only stores the book's call number, not the entire book text.
Jessica's wedding portal
task.weddingId → one wedding record.
Agentify CRM
message.conversationId → one inbox thread.
Go deeper
Links between records via ids.
Common mistakes
- Copying parent fields onto children and forgetting to sync.
- Deleting parents while children still point at them.
AI-agent trap
Agents embed huge nested objects. Ask for id references + separate queries.
Summary
Prefer ids over duplicating names/emails. When the contact name changes, every linked view updates from one place.
Confidence: