All topics
Get started8Account, team & permissions44Units & fields70Records, views & tasks39WhatsApp & Cortex Chat68Email & social27Lead ads & distribution38Automations52Documents & quotes32Dashboards40Cortex AI18Developers & API12
Help Center·448 guidesAll topicsContact support

Edit, assign or delete several records at once

Select rows, or every record that matches the view, then choose edit, assign or delete. Up to 100 records are done straight away, and more run in the background with a progress bar.

5 min
Before you start · for managers and agents
The edit permission, plus assign or delete depending on the action
  • You need: The edit permission, plus assign or delete depending on the action

Steps

1
Select rows in the table. To act on every record that matches the view, tick the box at the top of the table, then press Select all … matching filters.
2
After selecting all, you can unselect specific rows.
3
Choose the action from the bar: Fields to edit a field, Assign to, or Delete.
4
Confirm. For more than 100 records, tick the I agree that I will … box first.
Up to 100 records: the result shows straight away. More than 100: a progress card shows and moves with each batch.
5
Review the result: how many succeeded, and the reason for the records that failed.

How large jobs work

The job is split into batches of 500 records. Your teammates’ jobs take turns with yours, so a small job never waits long.

In a bulk edit, a record that fails doesn’t stop the rest. Each record is checked with the same rules as a single edit: required fields, status rules and conditions.

Canceling

You can stop the job while it runs with Cancel. Stopping isn’t undoing: what was written stays written, and the message shows where it stopped.

What you see while it runs and after

What you see
What it means
A card with “Updating records…”, a progress bar and a count such as 300 / 640
The job is running. The card also shows how many failed so far, and Cancel
“Updated 640 records.”
Every record succeeded. Other actions say “Deleted…”, “Assignees updated on…” or “Copied…”
“Updated 600 of 640.”
Some succeeded and some failed, with nothing rolled back. The reason shows under it, with Retry
“Bulk action failed.”
Nothing succeeded. Press Retry to try again
“Cancelled at 300 of 640.”
You stopped it. The rows already written stay written, and the rest were skipped

If something goes wrong

What you see
Why
What to do
“Nothing to act on.”
The selection is empty: the filter matches no records, or you unselected every row after selecting all.
Change the filter or select rows, then try again.
“You can’t cancel a job started by another user.”
A teammate started the job.
Ask them to follow it up.
“Progress report expired. Refresh to see the latest state.”
24 hours have passed since the job.
Check the records directly, or the Activity tab.
“Updated 600 of 640.”
Some records were refused because of a required field or a status rule.
Read the reason under the message, fix those records, then press Retry.

A real example

Shield Security Co.
The situation

A technician moved to another branch, leaving 640 open contracts.

What they did
  1. The manager filtered the contracts by assignee = the old technician.
  2. He selected all 640 matching contracts, then assigned them to the new technician.
The result

The job ran in the background in two batches, and every one of the 640 contracts was reassigned.

A made-up company, to show the idea. The numbers are rounded.

Good to know

Up to 100 records are done straight away; more run in the background in batches of 500.
Selecting all includes only the records you can see, and each record is checked for the edit permission.
Only the person who started the job sees its progress and report, and the report is kept for 24 hours.
Bulk delete checks the delete level for each record.
Bulk assign needs the assign permission.
Did this guide solve it?
If not, we’ll ask what was missing.
Open in Corteksa
Did this guide solve it?

We read every answer. To get a reply, use Contact support.