Metavaro (PTY) LTD. Logo
Admin & Configuration

Bulk Operations & Book Move

Change thousands of records in one pass, with permissions checked up front, business rules still running, and a field-level before-and-after trail on every record touched.

Illustrative UI only. Data and individuals shown are fictitious; any resemblance to real persons or data is coincidental.

Every object, no special build

Bulk update is a platform primitive available on any record type, and it picks its execution strategy by volume, so ten rows and ten thousand each get the right plan.

All or nothing on permissions

The batch is authorised as a whole. If the actor can't edit even one record in it, the whole batch refuses and says so. It never silently shrinks to the rows it could touch.

The rules still run

Record-level business rules see every row in the batch, so bulk isn't a side door around validation. A sweep obeys the same logic a one-at-a-time edit would.

A book move that's accountable

Reassigning a book of business runs as one transaction that completes entirely or rolls back entirely, and every record keeps its own before-and-after history with the acting admin attached.

Why we like this one

Bulk tools earn distrust by reporting success they didn't have: "947 of 1,000 updated" with no word on which 53, or why. The design choice we respect here is refusal over partial success: a batch you aren't fully allowed to make doesn't shrink, it stops and tells you. Partial successes are how data quietly forks, and a tool that would rather halt than guess is the one you can hand to an admin on a Friday afternoon.

Book a demo ➝