Record-by-record editing wastes time. If you need to update 50 Opportunities or 20 Accounts at once, the UI forces you through click-for-each-record hell. Mass editing solves this. The Avonni Data Table gives you two ways to do it: a flow-based approach with a two-flow pattern, or a no-code Dynamic Components setup that works directly on Lightning Pages. Both let your users select multiple records and update them all in one shot.

The pain of record-by-record editing

Let's be concrete. You need to update the Stage on 50 opportunities from "Prospecting" to "Qualification." In traditional Salesforce:

That's 50 clicks, 50 page loads, 50 saves. At 10 seconds per record, that's nearly 8 minutes. For 50 records.

Now add the error factor. After clicking the 30th opportunity, mental fatigue sets in. Did you update this one already? Did you change the Stage or leave it blank? You might update the wrong field, or update only 40 records when you meant to update all 50. The time cost scales, but so does the error rate.

Multiply this across your org. If your team does bulk updates quarterly, that's lost productivity adding up to hours every year, multiplied by hundreds of users.

Salesforce's native mass edit limitations

Salesforce offers list view inline editing. You can select multiple records and edit them in-line, which is faster than the record-by-record approach. But there are limits:

What about the other native options?

Data Loader: Powerful for admins, but not something you'd hand to an end user. It requires CSV exports, manual edits, and re-imports. Too many steps for a sales rep who just needs to update 20 opportunity stages.

Mass actions in Lightning: Limited to owner changes and a few other predefined operations. You can't mass-update custom fields or picklist values.

Mass editing via Avonni Data Table in Flow solves all of these limitations.

Why bulk editing in flows is better

A flow-based bulk edit gives you:

Understanding the performance implications

When you update 100 records, Salesforce writes 100 changes to the database. Here's what matters:

Configuration tips for large record sets

Pagination for scanning

If you're editing 500 records, showing all 500 rows on one screen is overwhelming. Configure the Data Table to show 25 rows per page. Styling your Data Table for visual consistency also helps with large datasets.

Limit visible fields

Don't show every field. Show only the fields users need to edit plus context fields like Owner.

Filter before loading

Use the flow's filter logic to narrow the record set before the Data Table loads them. Smaller datasets load faster and are easier to edit.

Field validation during bulk edit

Required field validation

Mark fields as required in your Data Table configuration. If a user tries to save without filling a required field, the Data Table prevents save and shows an error message.

Pattern validation

For fields like email or phone, Avonni can validate patterns (e.g., "must be valid email"). Configure this in the Data Table column settings.

Custom validation logic

Before the update, run a flow decision. Example: "If Status = Closed AND Amount = 0, show an error message."

Real-world use cases for mass editing

You'll need the Avonni Components Package installed.

The flow approach: two flows working together

Two flows work together:

Let's build it

Step 1: Build the main flow

The main flow is what your users see — a Data Table with records and a Bulk Edit button that launches the second flow. You'll configure the table, point it at a data source, and add the button.

Step 2: Build the bulk edit flow

This second flow opens as a modal when the user clicks Bulk Edit. It receives the selected record IDs from the main flow, loads only those records, makes them editable, and saves the changes back to Salesforce when the user hits Save.

Step 3: Connect the flows

Final piece: wire the Bulk Edit button on the main flow to launch the second flow as a dialog, pass the selected IDs across, and refresh the main table once the bulk edit completes.

You've built mass editing. Users select records, click Bulk Edit, update them all at once, and the main table refreshes.

Related: Full flow tutorial.

The Dynamic Components alternative

If you're building on Lightning Pages instead of Flows, the Data Table's bulk edit works as a Dynamic Component too. The setup is simpler: no second flow, no modal configuration. The component handles everything built-in.

Your users select multiple rows, click one button, and a modal appears where they update the same fields across all selected records at once. Hit Save, and Salesforce updates every record. No Flow needed. No Apex. Nothing to maintain on the backend.

The setup comes down to three things:

Once those three pieces are configured, the Data Table handles everything else: rendering the modal, showing the right fields, and pushing the mass update to Salesforce. Most admins have it running in under 15 minutes.

Full walkthrough with screenshots: Dynamic Components bulk edit tutorial.

Tips from teams already using bulk edit

Every click you eliminate is time back in your team's day. Bulk edit turns a 30-minute task into 30 seconds.