1. Primary-Sub Field Usage Scenarios

A primary-sub relationship means a Primary Object can have multiple Sub-objects, while a Sub-object can only belong to one Primary Object. For example, when Company A generates a Sales Order and its line items, a primary-sub relationship exists between them—the Sales Order is the Primary Object, and the line items are Sub-objects. This relationship allows you to query and manage the line items associated with the Sales Order, improving data visibility, accuracy, and management efficiency, giving you a comprehensive view of the order.

picture coming soon:

2. User Guide

2.1 Primary-Sub Field Configuration

In a one-to-many relationship between a primary business object and its detail records, you can add this field to the detail object.

2.1.1 Primary Business Object

After selecting the Primary Business Object, the current object becomes its Sub-object. For example, if you set the Sales Order as the Primary Business Object for line items, the Sales Order becomes the Primary Object, and the line items become Sub-objects.

2.1.2 Related List Title on Detail Page

If you enter “Sales Details” as the Related List Title on Detail Page in the primary-sub field settings of the line items, this title will appear in the related list section of the Primary Business Object’s detail page.

2.1.3 Cascading Operations and Data Permissions

• Status Synchronization: The status of Primary and Sub-objects is fully synchronized. Voiding, restoring, or deleting the Primary Object will apply the same action to its Sub-objects.
• Modification Records: Changes to Sub-objects will be reflected in the modification history of the Primary Object.
• Data Permissions: Sub-objects inherit the same data permissions as the Primary Business Object.

picture coming soon:
picture coming soon:

2.1.4 Mandatory Sub-object Entry When Creating Primary Object

• If set to Yes, you must fill in Sub-object details when creating a Primary Object.
• Example: If line items are marked as mandatory for Sales Orders, submitting a Sales Order without line items will trigger a validation error: “Sales Order cannot be empty.”

2.1.5 Display Separate Create/Edit Entry for Sub-object

• This is a fixed configuration and cannot be edited.
• Sub-objects that allow separate editing are not standard primary-sub relationships, as they break status and permission synchronization. For such cases, use a Lookup Relationship field instead.

picture coming soon:

2.2 Key Considerations for Primary-Sub Fields

• Approval Workflows: Sub-objects (created with Primary Objects) cannot have separate approval flows. Any changes to Sub-objects trigger the Primary Object’s approval process, displaying both Primary and Sub-object changes.
• Mapping Rules: Sub-objects cannot have independent mapping rules; they must be mapped together with the Primary Object.
• Custom Sorting: Sub-objects can be sorted during creation/editing, and the sorted order applies to list views.
• No Self-Referencing Fields: Sub-objects cannot add lookup fields to their Primary Object. A single object cannot have both primary-sub and lookup fields referencing the same object.
• No Separate Creation: Sub-objects cannot be created independently. The “Display Separate Create/Edit Entry” setting is read-only and cannot be modified.
• No Multi-Level Hierarchy: For example, if line items are Sub-objects of a Sales Order, the Sales Order itself cannot be a Sub-object of another object.
• Limits: A Primary Object can have up to 5 Sub-objects. Each object supports only one primary-sub field.
• Legacy Support: Some preset objects historically allow separate Sub-object creation/editing, but new objects do not.

Note:
1. Sorting is not supported for the following objects (which have their own sort fields): Products, Specifications, Specification Values, Price List Details, and Units.
2. Mobile sorting is not supported; results follow the Web sorting order.
3. Template prints also display sorted results.
4. The default limit is 200 Sub-objects. To increase this, purchase a resource pack (100 additional Sub-objects per pack, max 3 packs).