Published at: 2026-09-17
Field overview
Learn about field definitions, types, basic attributes, and common configuration rules.
Overview
Fields are the fundamental units for storing data in objects and are the core elements for building business models. The system supports 32 field types and 3 business components, covering text, selection, numeric, date/time, relationship, and calculation categories. This topic describes field definitions, field type details, basic attribute configuration, and common configuration rules.
Field definition
Fields carry all specific information for each object. Enterprises can add fields as needed for data maintenance. Each object supports up to 500 fields.
To add a field, go to Setup > Object Management > Standard Object Management / Custom Object Management, select the object to configure, and click Add Field.
System-standard fields
System-standard fields (also called pre-built fields) are the fields automatically included in every object upon creation. There are 15 in total:
| Field name | Field type | Purpose | Editable |
|---|---|---|---|
| Primary attribute | Single-line text | Uniquely identifies each record | Partially editable |
| Owner | Personnel | The owner of this record | Partially editable |
| External owner | Personnel | The external owner of this record (user interconnection scenario) | Not editable |
| Organization | Department | The organization this record belongs to | Not editable |
| Owner department | Department | The department this record belongs to. Does not change when the Owner field changes | Partially editable |
| Owner primary department | Single-line text | The primary department of the record owner. Changes when the Owner field changes | Not editable |
| Lock status | Single select | Indicates whether the data is locked | Not editable |
| Record type | Record type | Every record must have a record type | Not editable |
| Life status | Single select | Indicates the current life status, typically used with approval workflows | Not editable |
| Last modified time | Date/Time | The last time this record was modified | Not editable |
| Create time | Date/Time | The time this record was created | Not editable |
| Last modified by | Personnel | The user who last modified this record | Not editable |
| Created by | Personnel | The user who created this record | Not editable |
| Exchange rate | Number | For transaction scenarios, pre-built when multi-currency is enabled | Not editable |
| Currency | Single select | For transaction scenarios, pre-built when multi-currency is enabled | Not editable |
Because these standard fields represent common data storage needs, they cannot be deleted. Some fields support editing.
[!NOTE] - The Owner, Owner Primary Department, and Owner Department fields involve data permissions. You can only set their values on the create page. They cannot be modified during editing and can only be changed through buttons and functions. To change these fields after record creation, configure a business button with a field change event. - When standard field data is redundant, hide the field from the role’s permissions or hide it directly in the scenario.
Differences between standard and custom fields
Similarities:
- Every field, whether pre-built or custom, includes the following attributes: field name, API name, description, create time, field type, status, and actions.
- No field has a “last modified time” attribute.
Differences:
- Pre-built fields: The field name, API name, description, and field type are generally fixed and cannot be modified.
- Custom fields: After saving, most attributes can be modified except for the API name and field type.
Among standard fields, Lock Status, Record Type, Life Status, External Owner, Owner Primary Department, Last Modified Time, Create Time, Last Modified By, and Created By do not support editing, disabling, or deletion. The Primary Attribute, Owner, and Owner Department fields are partially editable.
Field type summary
The system supports 32 field types and 3 business components. The following tables describe each type’s use cases and restrictions.
Text fields
| Field type | Description | Example | Notes |
|---|---|---|---|
| Single-line text | For short text such as names | Text | Up to 100 characters |
| Multi-line text | For longer text such as remarks or suggestions | Text typically longer than 10 characters | Up to 2,000 characters |
| Rich text | For mixed text and image content such as product descriptions | Text + images | Up to 131,072 characters |
| Collaborative rich text | For mixed text and image content with more collaboration features than rich text | Text + images | Up to 131,072 characters |
Selection fields
| Field type | Description | Example | Notes |
|---|---|---|---|
| Single select | For selecting one option from a list, such as grade or gender | Grade A | Up to 3,000 options |
| Multi-select | For selecting multiple options from a list, such as interests | A, B | Up to 3,000 options |
| Boolean | For selecting “Yes” or “No” | Yes | — |
Numeric fields
| Field type | Description | Example | Notes |
|---|---|---|---|
| Number | For numeric values such as age or order quantity | 10.01 | — |
| Amount | For monetary values with thousands separators, such as order amount | 66.66 | — |
| Percent | For entering and displaying percentages | 90% | — |
Date/time fields
| Field type | Description | Example | Notes |
|---|---|---|---|
| Date | Select a specific date | 2099-12-31 | Supports “Year-Month-Day”, “Year-Month”, “Year-Quarter”, “Year” format variations |
| Time | Select a specific time | 16:31 | — |
| Date/Time | Select a specific date and time | 2099-12-31 16:31 | — |
| Date range | Set a specific time period | 07/03/2023, 00:00 - 05/04/2023, 10:00 | Supports precision down to seconds |
Contact and media fields
| Field type | Description | Example | Notes |
|---|---|---|---|
| Mobile phone | For phone numbers | 18888889999 | — |
| For email addresses | user@example.com | — | |
| URL | For web addresses | www.example.com | — |
| Image | For uploading images. Supports watermark photos and OCR text recognition | — | Up to 20 per object (expandable via resource packages) |
| Attachment | For uploading files with configurable quantity limits | — | Up to 50 per object (expandable via resource packages) |
| Large attachment | For uploading files larger than 100 MB | — | Up to 1 per object (resource packages not supported) |
Relationship and calculation fields
| Field type | Description | Example | Notes |
|---|---|---|---|
| Lookup relationship | Links the current object to another object (or itself) | [Order] linked to [Account] | Up to 10 per object (expandable via resource packages) |
| Master-detail relationship | Defines a master-detail relationship where the child object’s data permissions follow the parent | Order - Order Products | Up to 1 per object |
| Reference field | Supports cross-object data retrieval | — | Up to 20 per object (expandable via resource packages) |
| Auto number | System-generated code following configured rules. Cannot be modified manually | 20191219-00001 | Up to 10 per object (expandable via resource packages) |
| Formula | Calculates field values using formulas. Result types include numbers, percentages, dates, and booleans | 66.66 | Up to 20 per object (expandable via resource packages) |
| Roll-up summary field | Supports cross-object data aggregation | — | Up to 20 per object (expandable via resource packages) |
Personnel and location fields
| Field type | Description | Example | Notes |
|---|---|---|---|
| Department | Select a specific department in the company | Sales Department 1 | — |
| Personnel | Select a specific person in the company | John Smith | — |
| Location | Create location information displayable on a map | No. 63 Zhichun Road, Haidian District, Beijing | — |
| Signature | Capture personnel signature information | — | — |
Business components
| Component type | Description | Notes |
|---|---|---|
| Area location component | Records specific geographic location information for business data | — |
| Check-in component | Records the time, location, and duration of business activities | Up to 1 per object |
| Payment collection component | Completes business payment collection to a specified account through this field definition | Up to 1 per object |
Field basic attributes
Field name and API name
- Field name: Must be unique within the object. Administrators can customize it based on business needs.
- API name: Auto-generated by the system. Primarily used by developers and formula references. Do not modify it unless necessary.
Help text
Help text provides field entry guidance for front-end users and supports two display modes:
| Display mode | Display location | Applicable scenario |
|---|---|---|
| Hover question mark | Create page, edit page, details page | Long descriptions or on-demand viewing |
| Inline display | Create page and edit page only | When you need to directly prompt the entry format or criteria |
Default values
- Default value: Pre-fills a value when front-end users create a new record. The default value can be a fixed value or a dynamic value calculated by a formula. After pre-filling, users can manually modify the value.
Different field types support different default value configuration methods:
| Field type | Default value method |
|---|---|
| Single-line text, multi-line text, percent | Text input or formula calculation |
| Rich text, email, URL | Text input only |
| Number, amount | Number selection or formula input (integers up to 12 digits, decimals up to 2 digits) |
| Boolean | Set “Yes/No” as the default value (option names are editable) |
| Mobile phone | Only supports mobile/phone fields from other objects via lookup relationships |
| Single select, multi-select | Set a specific option as the default value |
| Date, date/time, time | Formula input |
Differences between default values and formula fields
When designing field default value formulas, it is easy to confuse them with formula fields. The following table compares the key differences:
| Dimension | Field default value (using formula) | Formula field |
|---|---|---|
| Design purpose | Provides entry assistance. Generates an initial recommended value that front-end users can adjust based on actual business needs | Ensures strictly correct results. Auto-calculates and is read-only |
| Typical scenario | Default product price (cost + margin). Sales reps can adjust the price based on customer discounts | Base currency amount (original currency × exchange rate). Must be strictly calculated and read-only for financial records |
| Historical data recalculation | After creating or modifying a default value formula, the system does not recalculate existing historical data | After modifying a formula, the system automatically recalculates all historical data (with some delay) |
| Trigger scenario | Only triggers on the create page, edit page, or list page edit when a dependent field physically changes. The default value formula does not re-trigger when data is modified through back-end APIs, imports, custom functions, or button operations | Triggers in all scenarios (including front-end manual entry, API imports, automation buttons, UI functions, and custom workflows) whenever a dependent field changes |
Other basic attributes
| Attribute | Description |
|---|---|
| Placeholder text for empty value | Displays placeholder text when the field is empty on the create/edit page. Currently supported by single-line text, multi-line text, number, amount, mobile phone, and URL fields |
| Allow duplicates | When set to “Do not allow duplicates”, the system validates data uniqueness. Records with identical values cannot be created, edited, saved, or imported |
| Required | When set to “Yes”, the field is required during creation, editing, and import. Records cannot be saved without a value |
| Cloneable | When set to “Yes”, the field value is carried over when cloning a record from the details page |
| AI content generation | When enabled, you can select or create a prompt template. Front-end users can click the AI button to generate content when creating records |
Three ways to configure required fields
- Field-level required: On the field configuration page, set “Required” to “Yes”. This applies across all scenarios, including front-end entry and back-end data import. Missing values prevent saving.
- Layout-level required: If a field is required only in specific business scenarios, set it as not required in the field properties. Then, in the specific page layout editor, select the field and check “Required”.
- Conditional required: If the required condition depends on the value of another field (for example, “Churn Description” is required only when “Churn Reason” is not empty), configure validation rules. See How to configure validation rules.
AI content generation configuration
When AI content generation is enabled, you need to configure prompt templates:
| Property | Description |
|---|---|
| Scenario category | Categorize the prompt template |
| Primary object | The object this field belongs to. Cannot be modified |
| API name | Auto-generated by the system. Modifiable, but do not change unless necessary |
| Template name | Serves as the unique identifier for selecting the prompt template. Required. Avoid duplicating existing template names |
| Description | Required. Not displayed when selecting the prompt template |
| Prompt content | Enter text and variables (supports current object fields, other object fields, scenario-related variables, and custom functions) |
The selected model generates content based on the “prompt content” according to “generation language”, “language style”, and “content length”. Click “Generate Preview” to view the template result. After configuration, front-end users can click the AI button on the field when creating records. The AI model generates key business information summaries including historical data based on the template.
Batch import fields
When you need to add multiple fields to an object at once, use batch field import. Batch import is suitable for the initial object setup phase, such as migrating a field list from a legacy system or quickly creating fields based on a business design table.
For detailed steps and the supported field type list, see Batch import fields.
Set field display names
When the same object has multiple record types, administrators can set different front-end display names for the same field. This is suitable for scenarios where different business lines share the same field but use different business terminology.
[!NOTE] Field display name settings only affect the front-end display name. The physical field name in the back-end field configuration remains unchanged.
For detailed configuration steps and results, see Field display name settings.
Field dependency relationships
Field dependency relationships control how the available values of single-select/multi-select child fields dynamically change based on the parent single-select field value within the same business object.
Business scenario example
In the “Account” object, there is a
Customer Level single-select field (options: Level 1, Level 2, Level 3) and a Customer Assets single-select field (options: Less than 100K, 100K-1M, More than 1M). If the business rule states that when a user selects Level 1, the “Less than 100K” asset option should be hidden, you need to configure a field dependency relationship.Configuration steps
- Prerequisites: In the target object, create both the parent and child fields with all their option values.
- Go to Setup > Object Management > Standard/Custom Object Management and open the target object.
- Navigate to the Field Dependencies configuration page and click to create a new dependency.
- Select the parent field and child field, and in the dependency matrix, check the child field options that correspond to each parent field option.
- Save the configuration.
Key limitations and logic rules
- Parent-child field type restriction: The parent field must be a single-select field. The child field can be a single-select or multi-select field.
- Cascade level limit: The system supports multi-level cascading (the child field of the second level serves as the parent field of the third level, and so on). Up to 10 levels of dependency are supported.
- Auto-fill logic: On the front-end entry page, when the child field is set as “Required” and after selecting a parent value, if the child field has only one remaining selectable option, the system auto-fills that unique value.
Cross-object filtering
Cross-object filtering allows users to set cascading filter conditions across different objects through master-detail fields, lookup relationship fields, or reference fields. For example, in the “Account” list, filter accounts that have “contact records in the last 30 days”.
Enable cross-object filtering in Setup
- Go to Setup > Object Management > Standard/Custom Object Management and open the target object.
- In the Basic Information > Optional Features section, check and enable the Cross-Object Filtering feature.
Front-end steps
After the feature is enabled in Setup, users can perform advanced multi-dimensional filtering on the front-end list page:
- Open the target object list page and click the Filter button in the upper-right corner to expand the side filter panel.
-
In the filter panel, click the Advanced Filter button.
-
Click Select Object and specify the related object whose data serves as the filter condition (for example, select the “Contact Record” object).
-
In the dialog box, configure: related object name, field name, operator (such as “greater than” or “equals”), and the corresponding filter value.
-
After configuration, click the Filter button. The system filters records that match the cross-object conditions.
FAQ
How to rename a standard field
You cannot directly rename a standard field on the field list page. Instead, use the Object Name Settings menu to modify the locale value corresponding to the field name.
For example, to change “Owner” to “Data Owner”, modify the Chinese locale value from “Owner” to “Data Owner”. The display name then shows “Data Owner” in the Chinese locale.
Owner, owner primary department, and owner department cannot be edited
These fields involve data permissions and can only be modified on the create page. During editing, the Owner, Owner Primary Department, and Owner Department fields cannot be modified and can only be changed through buttons and functions.
To change these fields after record creation, configure a business button with a field change event.
Single-select field displays “Option deleted” on the page
Possible cause 1: The option name retrieved is not the latest
- Clear the browser cache and try again.
- Confirm whether the option name has changed, then refresh and check again.
Possible cause 2: A non-existent option value was backfilled
- Check whether the field has a default value set and whether the backfilled option still exists.
- Check whether the option is assigned by a function and whether the backfilled option still exists.