Published at: 2026-09-17

Master-detail relationship

Overview

The Master-Detail Relationship describes a one-to-many strong binding between a master object and its detail objects: one master object can have multiple detail objects, but each detail object belongs to only one master object. Through this relationship, you can view and manage the related detail object list from the master object detail page, improving data visibility, accuracy, and management efficiency.

Use case

Consider sales orders and order details as an example: Company A generates sales orders and order details during its sales process. The sales order and order details have a master-detail relationship — the sales order is the master object, and the order details are the detail objects. Through this relationship, you can view and manage the order detail list associated with each sales order, providing a comprehensive view of the order.

Master-Detail field configuration

In a one-to-many master-detail business relationship, you add a Master-Detail field on the detail business object (the detail object). The configuration items are described below:

Master business object

After you select the master business object, the current object becomes a detail object of that master business object.

Example: On the “Order Detail” object, select “Sales Order” as the master business object. “Sales Order” becomes the master object, and “Order Detail” becomes the detail object.

Detail page related list title

Sets the title displayed in the “Related Lists” area of the master object detail page for the detail object.

Example: In the Master-Detail field configuration of “Order Detail,” set the Detail page related list title to “Sales Details.” On the detail page of the “Sales Order” master object, the related list title for order details displays as “Sales Details.”

Cascade operations and data permissions

The Master-Detail Relationship has strong binding characteristics:

Status synchronization: Master and detail data status are fully synchronized. When you void, restore, or delete the master object, the system also voids, restores, or deletes the detail objects.
Modification history synchronization: Modification history of detail objects appears in the master object modification history.
Data permission synchronization: Detail object data permissions match the master business object permissions.

Whether detail objects are required when creating the master object

When set to “Yes,” you must add detail object records on the master object create page. Otherwise, submission is blocked.
Example: If you configure “Order Detail is required under the Sales Order master object,” and no order detail records are added on the Sales Order create page, submission is blocked with the message “Sales Order cannot be empty.”

Whether to show standalone create/edit entry for the detail object

This is a fixed setting and cannot be edited.
Objects that allow standalone editing are not standard Master-Detail relationships. Standalone editing prevents master and detail data from maintaining consistent data status and permissions. If you need two objects to support standalone creation and editing, use a Lookup Relationship field instead of a Master-Detail Relationship.

Considerations

When using Master-Detail fields, note the following limitations and rules:

Approval workflow: Detail objects (when created simultaneously with the master) cannot have standalone approval workflows. Any change to a detail object triggers the master object approval. Approval workflows can display changes to both master and detail objects simultaneously.
Mapping rules: Detail objects cannot have standalone mapping rules. Master and detail objects can be mapped simultaneously.
Detail object sorting: During master-detail creation/editing, you can customize the detail object sort order. The list page displays records in the sorted order.
- Mobile sorting is not currently supported. The mobile app displays records in the Web sort order.
- Template print output also follows the sorted order.
- Note: This sorting feature does not support the following objects (these objects have their own sort fields): Goods, Products, Specifications, Specification Values, Price Book Details, Units.
Relationship constraint: A detail object cannot add a lookup field that references its master object. A Master-Detail field and a Lookup Relationship field on the same object cannot reference the same object.
Multi-level restriction: Master-Detail relationships cannot be nested. For example, if Order Detail is a child of Sales Order, then the Sales Order object cannot have another Master-Detail field.
Detail object count: The default detail object limit is 200 records. To increase this, purchase a detail record resource pack. Each pack adds 100 detail records, and you can purchase up to 3 packs.
Quantity limit: A master object can have up to 5 detail objects. Each object supports only 1 Master-Detail field.
Standalone create/edit entry: Detail objects no longer support standalone creation. The related configuration items are forced to read-only during Master-Detail field creation and cannot be modified.
- Some standard objects still support standalone detail object creation/editing due to legacy logic. Newly created objects do not support this.
- Because master-detail objects have strong dependencies (data permissions, approval workflows, deletion, and so on are all bound), standalone detail object editing does not align with business scenarios.
- When you need two objects to support standalone creation and editing, consider whether a Lookup Relationship can replace the Master-Detail Relationship. You can then create records through the Lookup Relationship component.
Standard object note: Some standard objects support standalone detail object creation and editing due to legacy logic. Newly created objects no longer support this capability.