Today5 stories · 2 briefs

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

Vol. I · No. 35The independent daily for Salesforce admins, developers and architects5 stories · 2 briefs

Must-readAgentforce and AI

Building and testing agents in the new Agentforce Builder (opens in a new tab)

You will learn how to create an agent from a natural-language description, switch between Canvas and Agent Script views, and test with Simulate and Live Test before committing and activating a version.

Why read this

It is a practical walkthrough of the Builder's main workflow.

  1. Describe the agent in natural language
  2. Refine in Canvas or Script view
  3. Test in Preview
  4. Commit Version
  5. Activate the version
The Builder workflow from creating an agent to going live

The new Agentforce Builder, found under Agentforce Studio, is presented as a way to make agent behavior more predictable by combining an upgraded reasoning engine, Agent Script that mixes natural language with programmatic logic, and built-in AI assistance. An agent can be started by describing its role and tasks in natural language, after which Agentforce generates an initial configuration that can be refined through chat or configured manually.

The Builder is organized into an Explorer for navigating settings, subagents, actions, variables and connections, a Canvas for editing configuration in a low-code block view, a Preview panel for testing, and an Agent Optimizer for natural-language changes. Canvas and Script views stay in sync, so changes made in one are written into Agent Script in the other. Typing a slash adds inline logic such as if/else conditionals, and typing an at-sign opens a resource picker for subagents, actions and variables.

Preview offers Simulate, which skips permission checks and does not run actions or touch data, and Live Test, which runs actions and changes data in the org. Both show reasoning explanations, traces, variable values and timing per step. Finally, a version is committed as a locked snapshot and activated; only one version can be live at a time, and activating a new one turns the previous one off.

Read the original at Salesforce Time (opens in a new tab)

Worth reading?

RecommendedAgentforce and AI

Fixing the field-access error in Agentforce Answer Questions with Knowledge (opens in a new tab)

You will learn the five checks to run when an Agentforce Service Agent fails with a field-access error while answering from Knowledge articles, and the order to run them in.

Why read this

The piece is a practical troubleshooting guide rather than new platform news.

  1. Assign Data Cloud User Permission Set
  2. Grant Read on Knowledge and mapped fields
  3. Enable Allow View Knowledge
  4. Verify data space access
  5. Confirm search index is Ready
The five checks to run in order when the field-access error appears

The article covers an error that appears when the Answer Questions with Knowledge action runs against an Agentforce data library: the agent’s running user cannot read one or more fields the library depends on. The usual causes are missing permissions, missing field-level security, or an incomplete Data Cloud setup. The agent runs as the user with the Einstein Agent User profile, and every object, field and Data Cloud resource the data library touches must be readable by that user.

The guide gives five checks in order: confirm the Data Cloud User Permission Set is assigned to the agent user, confirm Read access on the Knowledge object and every mapped field, enable Allow View Knowledge, verify the user’s data space access in Agent Studio, and confirm the search index for the Knowledge data library is Ready. It also recommends a dedicated Permission Set for the agent user, re-auditing field-level security whenever the library changes, granting least privilege, and testing as the agent user rather than as an admin.

The author notes that the source material contained no code, and that the link between an unready search index and this specific message is not confirmed in the source, so it should be checked as a separate cause.

Read the original at InfallibleTechie (opens in a new tab)

Worth reading?

RecommendedDevOps

Reconciling record Counts and field values before a Salesforce go-live (opens in a new tab)

You will learn a spreadsheet-based method for proving a Salesforce data migration is complete and accurate, using external keys, SOQL counts and totals, and case-sensitive value comparisons.

Why read this

You will also see how to tell nulls and truncation apart from other mismatches.

  1. Reconcile record counts per object
  2. Compare totals on amount fields
  3. Compare field values on an external key
  4. Sign off each object
The migration check runs in four steps, from counts to sign-off

A load that finishes without errors only shows that Salesforce accepted the rows sent to it. It does not show that every source record arrived or that the values arrived unchanged. The article sets out a check per object that compares record counts with SOQL, excluding records created by hand in the sandbox and records left out on purpose, and reports the difference in a status column.

Count matches are not enough on their own, so the author compares summed amounts per object and per StageName group, including the handling of corporate-currency totals in multi-currency orgs. Field values are then matched on an External ID using INDEX and MATCH, with EXACT used for a case-sensitive comparison and a sample taken for large objects. Nulls and truncation are flagged separately, because they have different causes and fixes.

The article closes with a per-object sign-off table that can only read Ready when counts, totals and value checks all pass, with a Counts only status for objects whose values have not been checked. The formulas were tested in LibreOffice Calc and are noted as untested in Excel and Google Sheets.

Read the original at dev.to (opens in a new tab)

Worth reading?

Apex and platform

How the merge() API handles Lead records and their MCAE Prospects (opens in a new tab)

You will learn which fields, history, related records and dates survive when Leads are merged, and how the linked MCAE Prospect behaves.

Why read this

You will also see how to find merged records afterwards with queryAll().

  1. Keep the chosen master Lead
  2. Reparent related records to it
  3. Copy the field values you supply
  4. Delete victims and set MasterRecordId
What the merge() call does to the victim Leads

The merge() SOAP API combines up to three records of the same type into one. The caller chooses the master record and the victims, and Salesforce keeps the master, reparents related records from the victims, deletes the victims and sets MasterRecordId on them. Field values are not copied automatically; any value the caller wants from a victim must be supplied on the master record in the MergeRequest.

For a merged Lead, the victims’ lead history is not carried over, but the surviving Lead gets a new “Lead Merged” history line showing the victim’s original name and company. Created By and Created Date are taken from the oldest victim. Related records such as Tasks, Campaign Members and Messaging Sessions move to the surviving Lead.

When both Leads are linked to MCAE Prospects, the Prospects are merged too and attached to the surviving Lead. The surviving Prospect keeps its original created date, but its conversion date and Recent Interaction date come from the oldest victim, and its audit log includes the victims’ activity. The article also notes an audit line reading “Started matching Marketing Data Sharing criteria”. Use queryAll() with MasterRecordId to find the records a merge deleted.

Read the original at SimplySfdc (opens in a new tab)

Worth reading?

Flow and admin

Using Flow Orchestration to coordinate multi-step business processes (opens in a new tab)

You will understand how Flow Orchestration organizes stages and steps across automated and interactive work, and when it is better than chaining several Flows.

Why read this

The article gives a worked onboarding example and a short checklist for a first build.

  1. Automated Flow stage
  2. Interactive Screen Flow stage
  3. Automated provisioning stage
A Flow Orchestration advances to the next step only when the previous one completes

Most automations start as one Flow, but as a process grows, several Flows can conflict, run out of order or duplicate work. Flow Orchestration, which the article describes as generally available in recent releases, lets you build one process made of stages and steps, where each step is an automated Flow, a background Apex or invocable action, or an interactive Screen Flow or approval assigned to a user or queue with a due date.

An orchestration advances to the next step only when the previous one completes. If a step fails, the orchestration pauses rather than continuing silently, and the orchestration run record shows the current stage, step, assignee and status in one place. The author’s onboarding example has an automated stage that creates tasks and a project, an interactive stage where a specialist confirms a kickoff call within three days, and an automated stage that provisions a portal user and sends a welcome email.

The article says orchestration suits processes with handoffs between people and automation, such as approvals, onboarding, case escalation and quote-to-cash, and is excessive for a single condition-and-action rule. It advises mapping the process on paper first, keeping one job per Flow, and remembering that orchestration runs consume Flow interviews and so still need governor-limit planning.

Read the original at dev.to (opens in a new tab)

Worth reading?

In brief