Introduction

Bulk actions in tables are a powerful feature, allowing users to perform an operation on multiple records simultaneously. However, users may have noticed that the "Select All" functionality is only available when dealing with a smaller number of records (specifically, less than 250). This article explains the technical reasons for this limitation and provides a recommended best practice for using bulk actions effectively.

The Technical Reason: Immediate vs. Scheduled Execution

The behavior of bulk actions is by design and is rooted in how the system processes these requests. Here's a breakdown of why the limitation exists:

When a user initiates a bulk action, the system triggers multiple, parallel requests from the user interface to execute the operation immediately. This synchronous approach ensures that the user gets instant feedback. However, this can be resource-intensive and is not designed to scale for a large number of records.

In contrast, scheduled jobs are designed to handle large datasets. They are executed asynchronously, often during off-peak hours when server load is low, or the task is delegated to a secondary server. This prevents performance degradation of the main application.

Recommended Best Practice for Bulk Actions

To ensure system stability and achieve your desired outcome, it is recommended to filter your data to a more manageable size before performing a bulk action.

Follow these steps for optimal results:

1. Filter Your Data: Use the available filters in the listview to narrow down the records to a smaller, targeted subset that aligns with your use case.

2. Select All: Once the record count is below 250, the "Select All" checkbox will become available.

3. Perform the Bulk Action: Execute the desired bulk action on the selected records.

By following this approach, you can still leverage the power of bulk actions without compromising system performance.