---
schema_version: "1"
id: 6ece2aab15034a1f8aa77c3d450e93562a3369c517b04b0f9cbc93459c61e443
title: List Views
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/260-0-0/rn_list_views.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_list_views.htm&release=260&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: de640f26ef90a5f35e89e9b97f5b626358e7e12e15f6bdcb8c0b9ac297caa000
description: When you sort a list view, blank fields are sorted as the highest value in the list instead of the lowest value. In list views rendered with Lightning Web Components (LWC), you receive an error notification earlier in the edit process if you try to edit more than 200 records at a time.
products:
  - Cross Cloud Packages Solutions
release: "260"
---
# List Views

When you sort a list view, blank fields are sorted as the highest value in the list instead of the lowest value. In list views rendered with Lightning Web Components (LWC), you receive an error notification earlier in the edit process if you try to edit more than 200 records at a time.

- **[List View Edit Limits Are Communicated More Clearly](https://help.salesforce.com/s/articleView?id=release-notes.rn_list_views_edit_limits.htm&release=260&type=5)**  
    List views rendered with Lightning Web Components (LWC) now prevent you from selecting or attempting to edit more than the supported maximum of 200 records at one time. Previously, if you selected more than 200 records, the edit icon still appeared and Salesforce didn’t restrict you from changing a field. However, when you attempted to apply your changes, an error notified you that your changes were unsaveable. To save you time and prevent the input of changes that can’t be saved, list views now enforce the 200-record limit earlier in the edit process.
- **[Use Updated Empty Value Placement in List View Sorting](https://help.salesforce.com/s/articleView?id=release-notes.rn_list_views_empty_value_sort.htm&release=260&type=5)**  
    When you sort a list view, blank fields, or null values, now are treated as the highest value in the dataset. For example, let’s say you have a column with the data 5, 9, null, and 2. If you sort this column in ascending order, you see 2, 5, 9, null. Previously, Salesforce treated blank fields as the lowest value, so that in the example given, you saw the data as null, 2, 5, 9.