Walkthrough

Fill or clear canvas records

Use Auto-fill to add fictional sample values to empty fields or clear values from several canvas records at once. Choose the records and the action before anything changes.

Before you begin

Auto-fill is useful for building test data, completing draft records, and resetting a group of cards. The generated values are fictional and based on the field types and choices available in the connected Salesforce org.

You will need:

At least one draft or loaded record on the canvas.
An active Salesforce connection so Org Loom can read the field definitions.
The Auto-fill permission in the active workspace.

Auto-fill changes the canvas only. It does not write to Salesforce. Filled or cleared values reach Salesforce only if you later include those records in an upload.

The process

Open Tools ▾ → Auto-fill.
Choose Fill empty required fields, Fill all empty fields, or Clear fields from Action.
Choose the record scope from Apply to.
Select the action button. Clearing loaded records requires confirmation.
Review the cards and use the toast's Undo action if needed.

Step 1: Open Auto-fill and choose the records

Open Tools ▾ in the canvas toolbar and choose Auto-fill. The Fill or clear fields modal offers three scopes in the Apply to dropdown:

Drafts includes new records that have not been uploaded.
Existing includes records loaded from Salesforce.
Selected includes the cards that were selected when the modal opened.

The modal starts with Selected when records are selected; otherwise it starts with Drafts when drafts are available. The count beside each scope shows how many records it contains.

Step 2A: Fill required fields

Choose one of the three actions below, then continue to Step 3. They are alternatives, not steps to run in sequence.

Choose Fill empty required fields to add sample values only where Salesforce requires a value to create the record. For example, an Account normally needs Name, while a Contact normally needs Last Name.

Each record is evaluated against its own object, so a mixed canvas of standard and custom objects can be filled in one run. Existing values are preserved, and generated name-like values are varied across records.

Required relationship fields are handled differently. Auto-fill does not invent a Salesforce Id or choose a related record for you. The fill result reports relationships that still need a canvas connection.

Step 2B: Fill all empty fields

Choose Fill all empty fields to populate empty writable fields, including optional fields. Values already present are never overwritten.

Picklists use an available Salesforce value.
Dates, numbers, email addresses, URLs, phone numbers, and checkboxes receive values appropriate to their field types.
Calculated, auto-number, and other non-writable fields are skipped.
Relationship fields remain unchanged unless a safe existing value or canvas connection already satisfies them.

The Apply to dropdown shows the number of records in scope. Only empty, eligible fields receive sample values; records with no eligible empty fields are unchanged.

Step 2C: Clear field values

Choose Clear fields to remove every field value from the records in scope, including required fields. Org Loom shows the number of records in scope and asks for confirmation when the scope includes loaded Salesforce records.

Clearing existing records stages Salesforce changes. If Existing or a mixed Selected scope is used, the cleared fields become local edits. The next upload will try to set those fields to blank in Salesforce. The additional confirmation explains the Salesforce effect.

Step 3: Run, review, and undo

After choosing a scope and action, select the action button. Clearing loaded records asks for an additional confirmation. Canceling either modal leaves the canvas unchanged.

After a successful fill or clear, the toast reports how many records actually changed and offers Undo. Undo restores the values from immediately before the run.

If you edit any affected record after Auto-fill, that older Undo is refused rather than replacing the newer work. Changes to unrelated records do not invalidate it.

Safety and expected limits

Fill is additive. It writes only to empty fields; use Clear and then Fill when you deliberately want new samples.
Drafts are the safe default. Existing Salesforce records are included only when you select Existing or include them in Selected.
Pending placeholders and schema cards are ignored. Only draft and loaded record cards are eligible.
Samples are a starting point. Review them and the upload preview before using them outside a test or demo dataset.
User records remain inactive. Auto-fill does not activate a generated User and trigger unintended onboarding.