Bulk edit canvas records

Before you begin

Add the records you want to change to the canvas. Bulk edit works on one Salesforce object and one field at a time. It can include new drafts, existing records, or a mixture of both.

In a Team workspace, a workspace admin must grant you the Bulk edit records permission.

Choose the tool that matches the change:

• Bulk edit for one exact value or a straightforward text replacement across many records.
• Fill records for filling empty fields without replacing values already present.
• Run script for conditional changes or values calculated from other fields.

The process

1. Optionally select the records you want to target.
2. Open Tools ▾ → Bulk edit.
3. Choose the object, field, and scope.
4. Choose Set value or Find & replace.
5. Review the affected count and select Apply.
6. Review the cards, then upload when you are ready.

Step 1: Open Bulk edit

Select records first if you intend to use Selected only. Then open Tools ▾ and choose Bulk edit. If nothing is selected, the initial scope is all canvas records of the chosen object.

Step 2: Choose the object, field, and scope

• Object lists the object types currently represented on the canvas. A mixed selection still requires one object at a time.
• Field lists fields available for editing according to the connected org's Salesforce metadata.
• All [object] records affects every real record of that object on the canvas.
• Selected only affects only selected records of that object. It is unavailable when none are selected.

The preview below the controls updates as you make choices. When the scope includes existing Salesforce records, it also reminds you that a later upload will write those staged changes to Salesforce.

Step 3A: Set the same value

Choose Set value and enter the new value. The input matches the field type: picklists offer active choices, dates use a date control, booleans offer True or False, and number fields accept numbers.

• The new value replaces the current value on every record in scope.
• Choose the empty or clear option to clear the field.
• For a lookup field, enter a 15-character or 18-character Salesforce record ID. This changes the field value but does not draw a relationship link between canvas cards.

Set value overwrites existing values. Use Fill instead when you want to leave populated fields unchanged.

Step 3B: Find and replace text

Choose Find & replace, enter the text to find, and enter the replacement. The search is literal, so characters such as periods, brackets, or dollar signs are treated as normal text rather than special patterns.

• Leave Case sensitive clear to match different capitalization. Select it when capitalization must match exactly.
• Select Match whole field only when the entire field must equal the Find value.
• Leave Replace with empty to remove the matched text.

Find and replace is offered for text-like fields. Number, date, and boolean fields use Set value instead. Records that do not match are left unchanged and are not marked as modified.

Step 4: Apply and review the change

Confirm the count in the preview, then select Apply. The window closes and the cards update immediately. Drafts remain drafts. Existing records become modified when their staged value differs from the Salesforce value that was loaded.

Applying a bulk edit still does not write to Salesforce. Inspect the cards and the modified-record count, then choose Upload to Salesforce when the result is correct. Salesforce performs the final permission and validation checks.

Undo a bulk edit

The confirmation message shown after Apply includes Undo. Use it before making another edit to the affected records. It restores every record changed by that one bulk operation.

Undo is intentionally refused if an affected record has been edited again since the bulk edit. This prevents an old Undo action from erasing newer work. In that case, correct the values manually or run another bulk edit.

After the changes have been uploaded, use Recall to review whether the uploaded fields can be restored safely.

Important behavior

• Temporary object placeholders are not included in the affected count.
• If no fields are available, ask a Salesforce administrator to review the user's field access and the object's metadata.
• Salesforce remains authoritative at upload time. A staged field can still be rejected or omitted if the connected user cannot write it.

See also

• Filling empty fields
• Running a script
• Recalling a Salesforce upload