Supporting List Layouts on Mobile Devices

Business admin users can define list layouts for objects to customize the columns displayed in search modals. This allows end users to view relevant information when searching for records to populate reference fields, providing better context for their selections.

Who can use this feature?

Configuring List Layouts for Search for

End users need at least Read field permission to the columns in a search modal or the columns do not display. For example, if the user does not have Read field permission to the approval_status__v field, information for the field does not display in search modals.

Defining List Layouts as

To define a list layout:

  1. Navigate to Admin > Configuration > Objects.
  2. Select the appropriate object.
  3. Select the Fields tab.
  4. Select the Display in default lists and hovercards option for each field to include in the list layout.

  5. Navigate back to the object.

  6. Select the List Layout tab.
  7. Select Reorder.

  8. Select and drag the fields to arrange them in the order you want them to display in search modals.

  9. Select Save.

Using List Layouts for Search as

When searching for records to populate a reference field, end users can view the defined list layout columns in the search modals. Fields defined in the list layout display after hardcoded columns.

List layouts are not supported for reference fields in the following areas:

  • Call Report

    • Only Account reference fields on the call report are supported in list layouts.

  • New Account Wizard
  • New Address Wizard
  • Parent Account Wizard

Attachment fields are not supported in list layouts and do not display in search results.

Additionally, the following reference fields are not supported in list layouts:

Object

Unsupported Fields

em_attendee__v
  • account__v
  • person__v
  • event__v
  • user__v

em_event_material__v

email_template__v

em_event_rule__v

country_override__v

em_event_speaker__v

speaker__v

em_event_team_member__v

group_name__v

em_expense_estimate__v
  • event_budget__v
  • expense_type__v

expense_header__v
  • incurred_expense_account__v
  • incurred_expense_attendee__v
  • incurred_expense_speaker__v
  • incurred_expense_team_member__v
  • incurred_expense_vendor__v
  • incurred_expense_venue__v
  • payee_account__v
  • payee_attendee__v
  • payee_speaker__v
  • payee_team_member__v
  • payee_vendor__v
  • payee_venue__v

expense_line__v
  • event_budget__v
  • expense_estimate__v
  • expense_type__v

expense_type__v
  • country__v
  • parent_expense_type__v

Related Topics

Configuring Vault Objects

Using Validation Rules on Mobile Devices

Supporting Field Calculations on Mobile Devices