Skip to content

Bulk Operations & Mass Update

Part of: ClientVerse Core (every client). New in Core 1.1.7.

What it is

Four tools for the jobs that are not "open a record and edit it" — you have a spreadsheet from a conference, or two hundred contacts that all need the same field changed.

Tool Use it when
CSV Import You have a spreadsheet of contacts or accounts to bring in
Bulk Add Many records need adding to a list or campaign at once
Bulk Activity The same interaction needs logging against many contacts
Mass Update Many records need the same field set to the same value

Before 1.1.7 each of these meant a data loader and an administrator. That is the change: the work moved to the people who actually have the spreadsheet.

Who it's for

Marketing, BD, and data stewards, gated by CV_Bulk_Tools_Access (the first three) and CV_Mass_Update_Admin (the fourth).

How it works

Every job writes to Clientverse_Log__c under a Bulk Operations record type — the same shared log object Dispatch and ERM use, isolated onto its own record type and layout so the different consumers do not clutter each other's views. That row is both the live progress tracker while the job runs and the permanent audit trail afterwards.

If a bulk job produced a surprising result, that log is where the answer is. It records what ran, who ran it, and what it touched.

CSV Import

Upload, map your columns, resolve duplicates, run.

Column mapping suggests matches, including for headers that do not match exactly. The duplicate check looks for likely matches rather than only exact ones, so "Bob Smith" and "Robert Smith" are flagged rather than silently added twice.

The flagged rows need a decision, not a click-through. Fuzzy matching is the right default — exact matching quietly creates the duplicates you will pay someone to merge later — but it means the importer is exercising judgement and showing you its work. Brief anyone you give this to.

Bulk Add

Select records from a list view or Client Locator result and add them to a list or campaign in one action. A Campaign also carries a quick action that launches it directly. This is the fast path from "the search found me 340 people" to "they are all on the invitation list".

Bulk Activity

Writes the same activity to every selected record — the right tool after an event or a mailing, so the interaction lands in each person's touchpoint history and feeds relationship scoring, rather than living only in somebody's memory.

Mass Update

Filter to the records you mean, set the field, apply.

This one has real blast radius. Grant CV_Mass_Update_Admin narrowly and check the record count before applying. There is no undo beyond the audit trail — the log tells you what changed, but reversing it is another mass update.

Before a large run

  • Consider the automation kill switch. Packaged automation can be disabled per object for the duration of a load, which avoids firing rollups and triggers once per row. Re-enable it and run a rollup recalculation afterwards — and put that step in the plan, not in your memory.
  • Sequence data-quality work after the load, not during. See Data Quality & Governance.

A note on what changed in 1.1.7

Job tracking used to live on Audit_Log_Import__c and Mass_Update_Job__c. Both were retired and consolidated onto Clientverse_Log__c. If you built reports on either, re-point them.