Create/Edit Page Layout

1. Create/Edit Page Layout — Desktop

The Create/Edit page layout has a default state. Its structure matches the Detail page and is divided into left, center, and right sections.

1.1 Default State of Create/Edit Page Layout

The Create/Edit page layout is disabled by default and uses the Detail page layout. Once you enable the Create/Edit page layout, the change is irreversible.

1.2 Navigation Area

The left side of the layout configuration screen contains two main sections: Components and Field information.

• Supported component types:
  • Generic components: platform-provided, common components that exist for every custom object
    • Title & Buttons: configure whether labels and buttons are shown on the Detail page and the number of buttons exposed
    • Form Component: move certain fields into a form component to highlight and emphasize fields to fill or edit
    • Table Component: create a table with a specified number of rows and columns and place fields or text boxes inside for side-by-side comparison
    • Related List: bulk-create other associated objects
    • Related List: same as on the Detail page
    • Container: same as on the Detail page

1.3 Content Preview Area

The center area of the screen is the page preview.

1. Drag components directly onto the page to configure them.
2. Set fields to Hidden or Visible.

1.4 Settings Area

Note: The right side of the layout configuration screen includes Global Settings and Component Settings.

1.4.1 Global Settings

Configure basic page-level information and layout, including:

• Toggle display of Quick Navigation
• Choose JS plugins for Desktop and Mobile
• Field alignment: Left, Center, Right

1.4.2 Component Settings

1. Title & Buttons
   • Configure the displayed title; can set to the object name or Record Type
   • Enable toggle button that allows changing column count on the Create/Edit page on the frontend
   • Show or hide generic Detail-page buttons
2. Form Component
   • Configure default column count: 1, 2, 3, or 4 columns

1. Table Component - Drag the Table component to set row and column counts. - Configure whether to show header, borders, and field background. - Merge and unmerge table cells. - Set cell background colors.

1. Related List Component - Support creation and configuration of related records when the lookup/association field points to this object. - Configure whether related object fields are required. - Configure generic buttons for related objects.

1. Text Box Component - Set the component label. - Toggle display of the component label. - Configure the text content.

2. Create/Edit Page Layout — Mobile

The Mobile Create/Edit page layout generally inherits Desktop settings; most component settings are shared. Some settings support independent Mobile configuration.

For Global Settings, you can independently configure:

• Field alignment (field text alignment)

For Component Settings you can configure:

• Quick Positioning (Quick Navigation) component: reorder other components
• Form Component: hide or show specific fields
• Record Component (business-related component): display style, title field, whether to show Images, whether fields are exposed, show/hide generic buttons
• Generic Button Settings: show/hide generic buttons on Create/Edit pages

3. Frequently Asked Questions

1. Why does the List view not update after I edit and submit a record on the Edit page?

You may have an approval process configured. Submitting on the Edit page can trigger the approval flow; the record will only update after approval completes.

2. Why does hiding a Sub-object field via a UI action not work on the Edit page — the field shows as read-only and the value is hidden (and not displayed)?

Hiding a Sub-object field via a UI action only hides the field value in the row, not the entire column header. Tables have multiple rows, and the system cannot dynamically render table headers per-row. If different rows hide different fields, the header cannot be hidden consistently.

3. Why does a lookup-associated object show on the Create page but not on the Edit page?

Creating the Primary Object and related object together is a feature in controlled release (feature flag): [Primary Object and related objects created together]. Currently, this feature only supports Create, not Edit; therefore the related object does not appear on the Edit page.

4. Mobile — Where do I configure which Sub-object fields expose outside the subtable on Create/Edit?

Unsupported field types: Rich Text, Collaborative Rich Text, Attachment, Large Attachment

The priority for which Sub-object fields appear outside the subtable is: 1) Primary Object Create/Edit page layout — Sub-object exposed fields configuration (up to 15 fields) 2) Sub-object Mobile Summary layout (takes the first 8 fields) 3) If Create/Edit layout is not enabled and no exposed fields configured, the system takes the first 6 fields from the Sub-object form as exposed fields for the Primary Object

Specific locations are shown below.

New/Edit Layout — Sub-object exposed fields configuration:

Sub-object Mobile Summary layout:

5. Why are Owner and Dept. hidden during Edit, and can they be exposed?

The system intentionally hides these during Edit to prevent accidental changes and to better control permission to change an Owner. Currently, you can change the Owner only via the Change Owner button. Dept. is calculated automatically from the Owner.

6. Why does saving the layout show “xxx option does not exist”?

Current observations: - If you import only the parent (controlling) field, saving the layout shows “Child option xxx field does not exist”. - If you import only the child (dependent) field, saving the layout shows “Option xxx does not exist”.

Cause: - The dependency for a picklist is recorded on the child field’s metadata, while the option dependency mapping lives on the parent field’s picklist options. - If you sync only the child field, the child’s recorded dependency might be overwritten or missing, causing the dependency to not appear. - If you sync only the parent field, the system validates dependencies and fails to save because the child field is missing.

Solution: - Re-deploy both parent and child fields together.

7. In Primary-Sub create/edit, pasting Sub-object data does not trigger UI actions

Scenario: Copy multiple rows/columns from Excel and paste them into the Sub-object table fields. The pasted fields have UI actions configured but they do not trigger.

Reason: This paste operation is not supported for triggering UI actions.

8. Why is there no Quick Navigation on the left for an object’s Create/Edit page?

1. Is the Create/Edit page layout enabled for the object? => Yes: verify the backend layout configuration. => No: if the page has only one section/group, Quick Navigation does not display.

2. If there are multiple groups but no navigation: a. The groups are configured as not visible in the backend. b. Fields in a group are not editable, so the group does not show on the Create/Edit page.