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 real record card 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 All drafts, All existing, or Selected.
- Choose Fill required fields, Fill all fields, or Clear all fields.
- Review the preview, select Run, and confirm the action.
- 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 records modal opens with three scopes:
- All drafts includes new records that have not been uploaded.
- All 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 All drafts when drafts are available. The count beside each scope shows how many records it contains.
Step 2: Fill required fields
Choose Fill 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 preview counts relationships that still need a canvas connection.
Step 3: Fill all empty fields
Choose Fill all 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 preview shows how many empty fields can be filled. If field metadata has not loaded yet, open one of the records to load its schema or run Auto-fill and let Org Loom retrieve it before changing values.
Step 4: Clear field values
Choose Clear all fields to remove every field value from the records in scope, including required fields. Org Loom shows the number of values that will be cleared and asks for confirmation before changing the canvas.
Clearing existing records stages Salesforce changes. If All 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 preview and confirmation call this out explicitly.
Step 5: Run, review, and undo
After choosing a scope and action, read the preview and select Run. The confirmation names the affected records, the object types, and the effect of the selected action. 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 All existing or include them in Selected.
- Pending placeholders and schema cards are ignored. Only real record cards are eligible.
- Samples are a starting point. Review them and the upload preflight 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.