Considerations for Inline Editing in a List View in Lightning Experience

Consider these points when editing fields on records directly from a list view in Lightning Experience. These considerations also apply when editing records in a multiline layout in Lightning Experience.

Required Editions

Important
Important Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained certain terms to avoid any effect on customer implementations.
Available in: Lightning Experience
Available in: All editions

General

Not all fields on records in a list view or multiline layout view can be inline edited. To find out whether a field supports inline editing, hover over it and look for the pencil Pencil icon. Non-editable cells have a lock Lock icon. When making inline edits in a list view, required fields can’t be left blank.

  • By default, list views and multiline views that contain more than one record type aren’t inline editable. To inline edit across multiple record types, select Make inline edits in list views with multiple record types in User Interface Settings. Otherwise, filter your list view to contain only one record type. The exception is Pipeline Inspection, which supports inline editing across multiple record types by default.
  • Inline edit doesn’t apply to components in the small region.
  • You can inline edit in Recently Viewed or Team list views that are predefined to contain only one record type. You can also edit tasks on the tasks object home page even though they’re not in a list view.
  • You can’t inline edit in split view.
  • If Enable Automated Account Fields in Account Settings is enabled, you can’t inline edit Account Name.
  • Your changes show in the list view as soon as you finish an inline edit. However, so that you can review your changes and fix errors if needed, any filters applied to the list view don’t apply automatically to your inline edit. To apply the filter criteria to the updated record, refresh the page.
  • In list views rendered with Lightning Web Components (LWC), a number field can store more decimal places than it’s configured to show. For example, if you enter 90.678 in a number field that accepts two decimal places, the list view displays 90.68, but the full value of 90.678 is saved in the database. If you inline edit the same field later, you see the saved original input of 90.678. In list views rendered with Aura, if you enter 90.678 in a number field that accepts two decimal places, the value is saved and displayed as 90.68.
  • In orgs that use the Thai locale, the list view displays a date format with the Gregorian year. However, the date picker uses the Buddhist Era year. For example, when the list view shows 31/10/24 in Gregorian year format, the date picker that appears during inline edit shows 31/10/2567 in Buddhist Era format.
  • Disabling the Mass Edits from Lists user permission prevents a user from mass editing list views only in Salesforce Classic. If all other configurations and permissions allow it, then the user can still mass edit list views in Lightning Experience.

Fields and Field Types Not Inline Editable

These fields and field types aren’t inline editable.

  • Built-in fields like Record ID or Created Date (never editable from the user interface)
  • Compound fields including Name, address fields, and geolocation fields. To inline edit names, use the First Name and Last Name fields.
  • Controlling or dependent picklists. If you have access to the controlling picklist field but not the dependent picklist field, the controlling field is inline editable.
  • Custom date/time fields
  • Encrypted text fields on some objects. Encrypted text fields are editable only when the object’s list views render with Lightning Web Components (LWC).
  • For orgs with person accounts enabled, if your list view is filtered by the Person Account record type, the Account Name field isn’t inline editable. If your list view is filtered by the Business Account record type, Account Name is inline editable. By default, if your list view includes multiple record types, no fields are inline editable. Selecting Make inline edits in list views with multiple record types in User Interface Settings lifts this restriction, but your list view must still be filtered to include only Person Account records or to exclude Person Account records for inline editing to work.
  • Formula fields
  • Standard fields of type date/time, auto number, rollup summary, record type, master-detail, rich text, checkbox, or hierarchy
  • By default, fields that aren’t on the page layout—including fields added to a Dynamic Forms-based Lightning page—aren’t inline editable. To make these fields inline editable regardless of page layout, select Remove list view inline edit dependencies on page layout in User Interface Settings.

Fields on Objects Not Inline Editable

The fields aren’t inline editable on these objects.

Object Fields Not Inline Editable
Campaign Parent Campaign
Document All Fields
Event All Fields
Opportunity
    • Amount
    • Expected Revenue
    • Forecast Category
    • Probability
    • Quantity
Price Book
  • Active Field
  • Description
  • Price Book Name
Task
  • Name
  • Private