Custom List Views Management

Viewing Records

In a list view, you can view details about a record by clicking it. You see only the data that you have access to. You can view records that you own, have read or write access to, or are shared with you. List views also include records owned by or shared with users in roles below you in the hierarchy. The fields you see depend on your page layout and field-level security settings.

When you access a tab, the default list view assigned to the object is shown. To switch to a different list view, click the app bar and then select from the available lists.

Searching List Views

Use the list view search box to search for records in a list view. Click the search box, enter your query, and press Enter. The list view search looks at all searchable fields even if the corresponding columns aren’t shown in the list view. In your search, you can enter any special character except for the % since it’s treated as a wildcard.

Considerations for Custom List Views

• Custom list view is supported for use only with the Lightning Web Components (LWC) framework. To use custom list views, the user must have the Access Lightning Web Components for Field Service Mobile permission enabled.
• You can view and prime a maximum of 200 records per custom list view.
• To ensure optimal performance of your custom lists:
  • Configure your list view to return the minimum number of records.
  • Avoid using reference fields in the list view.
  • Minimize the number of fields you use on each object.
• Custom lists sorted by Last Modified Date are always ordered newest to oldest, which is standard for all related lists.
• The Recently Viewed list view isn’t supported. When accessed, it doesn’t return records, and an error is returned.
• Limitations apply to what filter configurations are supported. When encountered, no records are returned and an error is shown. Here’s a list of known filters that aren’t supported in mobile list views. Other filters not in this list can apply. 
  • A filter that uses a multiple currency field
  • A filter that uses a locale and org-based date literal, such as
    • THIS_WEEK
    • THIS_FISCAL QUARTER
    • LAST_WEEK
    • THIS_WEEK
    • NEXT_WEEK
  • A filter that uses a polymorphic field
  • A filter that uses a number n type date literal, such as
    • LAST_N_QUARTERS
    • NEXT_N_QUARTERS
    • LAST_N_WEEKS
    • NEXT_N_WEEKS
    • LAST_N_YEARS
    • NEXT_N_YEARS
    • N_DAYS_AGO
    • N_WEEKS_AGO
    • N_MONTHS_AGO
    • N_QUARTERS_AGO
    • N_YEARS_AGO
  • A filter that uses an unsupported scope
  • In some cases, new records aren’t shown on certain custom list views. For example, in a Case custom list view that filters on closed = false, a new offline Case record isn’t shown on the list view because closed isn’t populated. The filtering criteria don’t apply to this record.
  • In some cases, a record created offline doesn’t show all the details in the card for the record. For example, if a contact is created with the first name and last name but the header of the card uses name only. The header can be blank because the name field isn’t populated.
  • Fields that have a reference that could be many different things, a reference to either a group or a user, aren’t supported.

Performance Considerations

• The number of objects in your database can impact the performance of custom list views.
• The number of fields entered when you’re performing a search can also affect performance.
• Your current network speed can affect the performance of network requests.