Published at: 2026-09-17
Use record types
A Record Type classifies data and processes in a Custom Object to support different Business Scenario values.
Overview
This article explains when and how to use Record Types. It covers role scope, Default Record Type fallback behavior, and master-detail type matching.
The Usage Object determines where the Record Type and its Business Process apply.
What is a Record Type?
A Record Type classifies data in one Custom Object by Business Scenario. When you enable multiple Record Types, you can configure:
- Different field sets: Show only the fields needed for each scenario.
- Independent required-field rules: Set requirements for each type.
- Dedicated page layouts: Assign different Form Page, details, and list layouts.
- Role-based type scope: Control which types each role can create and use.
Why use Record Types?
Different scenarios within one object can have very different requirements. For example:
| Business Scenario | Field differences | Process differences |
|---|---|---|
| Account Complaint | Complaint category, severity, and expected resolution time | Escalated Approval Process |
| Account inquiry | Inquiry topic, product line, and feedback channel | Rapid-response process |
Without Record Types, unrelated fields share one page. This creates clutter, complicates required-field rules, and lowers data quality. Multiple Record Types give each Business Category a focused layout.
How it works
Role scope
Create Record Types and assign them to roles. For example:
- After-sales Service Personnel: Account Complaint
- Pre-sales support personnel: Account inquiry
Users can select only the Record Types assigned to their roles.
Default Record Type rules
- Each role has at least one Record Type: If none is assigned, the system assigns the Default Record Type.
- Fallback after disabling custom types: If all custom types are disabled, the system assigns the Default Record Type to every role.
[!IMPORTANT] You cannot delete the Default Record Type. You can rename and configure it, but it remains the system fallback.
Master-detail type matching
For Related Object data in a Master-Detail relationship, go to Record Type > Match Primary Object Record Types on the detail object.
If primary type A matches detail types B, C, and D, only those three options appear when users create or edit the primary and detail records together.
Example:
- Primary object: Order with type Standard Order
- Detail object: Order Detail with types Product Details and Service Details
- When creating a Standard Order, users can select only Product Details or Service Details.
Recommended use
| Scenario | Recommendation | Description |
|---|---|---|
| One object needs different field sets | Recommended | Configure a field set for each type |
| Roles can create different data types | Recommended | Use role scope |
| Master-detail types must cascade | Recommended | Use master-detail type matching |
| Only field values differ, such as status | Not recommended | Use a picklist and scenario filters |