Published at: 2026-09-17

Manage standard objects

Manage system-standard fields, custom fields, and field dependency relationships for business objects in ShareCRM CRM.

Overview

Every business object includes system-standard fields and supports administrators adding custom fields and configuring field dependency relationships based on business requirements. This topic describes how to configure standard fields, custom fields, and dependency relationships.

System-standard fields

Every business object has system-standard fields. These fields cannot be deleted, but some can be modified and hidden. For example, the Account object includes standard fields such as account status and account pool.

Standard fields support the following configuration:

Field name: Cannot be modified.
Required: Whether the field is required when creating a new business record.
Hidden: If hidden, the field is not visible when creating a new business record.
Option settings: For select-type fields, users can modify option values. For example, in the Opportunity object, you can configure “Lost Reason” options such as “Lost to competitor” or “Did not meet customer requirements”.

Custom fields

When system-standard fields cannot fully meet business requirements, users can add custom fields to each business object.

Supported field types

The system currently supports 32 field types and 3 business components. Details are as follows:

Standard base fields: Owner, Owner Department, Owner Primary Department, Created By, Create Time, Last Modified By, Last Modified Time, Life Status, Delete Flag

Standard interconnection fields: External Personnel, External Related Team, External Enterprise Account

Supported field type list:

Single-line text: Supports barcode scanning and manual entry
Multi-line text
Rich text: Supports mixed text and image formatting
Single select: Supports field dependency relationships
Multi-select
Number: Supports default values
Amount: Supports default values and masking
Date
Time
Date/Time
Mobile phone: Supports default values and SMS verification codes (Account object only)
Image: Up to 20 image fields per object, supports watermarks
Attachment: Up to 50 attachment fields per object
Large attachment: Up to 1 large attachment field per object
Email: Supports default values and masking
URL: Supports default values
Boolean: Yes/No with editable option names, usable in formula calculations
Percent: Supports default values
Location: Configurable selection scope
Personnel: Configurable selection scope
Personnel (multi-select): Configurable selection scope
External personnel
Department: Configurable selection scope
Department (multi-select): Configurable selection scope
Reference field: Up to 20 per object. Can reference fields from lookup-related objects and parent objects. Filtering is not supported when referencing global variables (current date, current time) or fields from the personnel object.
Lookup relationship: Up to 10 per object (expandable via resource packages). Supports default data values. Selection scope: manual settings or custom functions for complex rules.
Lookup relationship (multi-select)
Master-detail field: Used for scenarios where child detail data is created together with the parent. The child object’s functional permissions and data permissions follow the parent object. Child objects do not have independent void, restore, lock, or unlock capabilities. Only objects without historical data can have master-detail fields added. One object can have only one master-detail field. One parent object can have up to 5 child objects.
Auto number: Auto-generated when data is saved. Not displayed on the create page. Prefix and suffix support year, month, and day variable insertion, as well as single-select fields from the current object and personnel object. Recount rules can be set by year, year-month, or year-month-day. Supports custom encoding rules via custom functions (710).
Formula: Up to 20 per object. Filtering is not supported when referencing global variables (current date, current time) or fields from the personnel object. Automatically recalculates all historical data when referenced field values change.
Roll-up summary field: Up to 20 per object. Supports configurable roll-up scope.
Signature field: Captures personnel signature information.
Payment collection component: Completes business payment collection to a specified account through this field definition. Up to 1 per object.
Check-in component: Users can check in/check out. The back end can configure whether check-out is enabled. Up to 1 per object.
Area location: Creates location information that can be displayed on a map. Up to 1 per object. Can trigger UI events.

[!WARNING] - When a standard object field is deleted, all associated data is also deleted and cannot be recovered. - Changes to standard object fields are synced to reports on the next calendar day.

Dependency relationships

Add a dependency relationship

A dependency relationship defines a parent-child dependency between fields within the same business object. The available values of the child field depend on the value selected in the parent field, similar to a cascading “Country-Province-City” relationship. The key difference is that in a dependency relationship, a single child option can be linked to multiple parent options, which is commonly used for multi-level classification.

Example: The parent field “Customer Category” has options “Enterprise Customer” and “Individual Customer”. The child field “Customer Level” has options “VIP Customer”, “Key Customer”, and “Regular Customer”. When setting up the dependency, you can assign “VIP Customer”, “Key Customer”, and “Regular Customer” to “Enterprise Customer”, and “VIP Customer” and “Regular Customer” to “Individual Customer”. At runtime, users must select “Customer Category” before selecting “Customer Level”.

Users can also create multiple dependency relationships to form multi-level dependencies. When creating the second dependency, select the child field from the first dependency as the parent field, and so on. Up to 10 levels of dependency are supported.

[!NOTE] - The parent field must be a single-select field. The child field can be a single-select or multi-select field. - Up to 10 levels of dependency are supported.

Remove a dependency relationship

After removing a dependency relationship, the two single-select fields are no longer interdependent and can be selected independently.