StephanieJoly4GitHubcubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>github-actionsAbdul RahmanFélix MalfaitReorganizing by Feature sections
Capabilities folders to give an overview of each feature
How-Tos folders to give guidance for advanced customizations
Reorganized the Developers section as well, moving the API sub section
there
added some new visuals and videos to illustrate the How-Tos articles
checked the typos, the links and added a section at the end of the
doc.json file to redirect existing links to the new ones (SEO purpose +
continuity of the user experience)
What I have not updated is the "l" folder that, per my understanding,
contains the translation of the User Guide - that I only edited in
English
<!-- CURSOR_SUMMARY -->
---
> [!NOTE]
> <sup>[Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) is
generating a summary for commit
5301502a32. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
---------
Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>
Co-authored-by: github-actions <[email protected]>
Co-authored-by: Abdul Rahman <[email protected]>
Co-authored-by: Félix Malfait <[email protected]>
60 lines
1.8 KiB
Plaintext
60 lines
1.8 KiB
Plaintext
---
|
|
title: Create Relation Fields
|
|
description: Step-by-step guide to connecting objects with relation fields.
|
|
---
|
|
|
|
Relation fields connect records from different objects—for example, linking People to Companies.
|
|
|
|
<Note>
|
|
**Relation names cannot be changed after creation** (they affect the API). Plan your names carefully.
|
|
</Note>
|
|
|
|
## Before You Start
|
|
|
|
Decide:
|
|
- Which objects are you connecting? (e.g., People → Companies)
|
|
- Which is the "one" side? (e.g., Company)
|
|
- Which is the "many" side? (e.g., People — many people work at one company)
|
|
- What should the field be named on each side?
|
|
|
|
See [Relation Fields](/user-guide/data-model/capabilities/relation-fields) for relation types explained.
|
|
|
|
## Steps
|
|
|
|
1. Go to **Settings → Data Model**
|
|
2. Select the object where you want the relation (typically the "many" side)
|
|
3. Click **+ Add Field**
|
|
4. Select **Relation** as the field type
|
|
5. Choose the **target object**
|
|
6. Select **One-to-Many** or **Many-to-One**
|
|
7. Enter field names for **both sides** of the relation
|
|
8. Click **Save**
|
|
|
|
## Example: People → Companies
|
|
|
|
- Go to **Settings → Data Model → People**
|
|
- Add a Relation field
|
|
- Target: **Companies**
|
|
- Type: **Many-to-One**
|
|
- Field on People: **Company**
|
|
- Field on Companies: **Employees**
|
|
|
|
Now each Person can be linked to a Company, and each Company shows its People.
|
|
|
|
## Deleting a Relation
|
|
|
|
1. Go to **Settings → Data Model**
|
|
2. Find the relation field
|
|
3. Click **⋮ → Deactivate**
|
|
|
|
Links are preserved but hidden. Reactivate to restore.
|
|
|
|
<Note>
|
|
**Deleting a relation doesn't delete records.** Only the link between them is removed.
|
|
</Note>
|
|
|
|
## Related
|
|
|
|
- [Relation Fields](/user-guide/data-model/capabilities/relation-fields) — types and limitations
|
|
- [How to Import Relations](/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv) — bulk import linked records
|