Today7 stories

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

Vol. I · No. 46The independent daily for Salesforce admins, developers and architects7 stories

Must-readAgentforce and AI

Building Custom Objects and Permission Sets with the Salesforce Development Plugin for Claude Code (opens in a new tab)

You will learn how to set up the Salesforce Development Plugin in Claude Code, prepare an org with the metadata-experts and salesforce-api-context MCP Servers, and generate a Custom Object, Permission Sets and a Lightning page as metadata.

Why read this

You will also see why the older Salesforce DX MCP Server is being retired and why deployments should stay with humans.

  1. Create the DX project
  2. Build the Custom Object and fields
  3. Build the Permission Sets
  4. Build the Lightning page
  5. Package the metadata for a human to deploy
The main stages of building metadata with the plugin in the worked example

The article explains how the Salesforce Development Plugin for Claude Code differs from other tools with similar names. It groups Skills, the Salesforce CLI and hosted metadata servers into one toolset, while the Salesforce DX MCP Server reaches end-of-life on November 2, 2026, and Salesforce in Claude is aimed at end users rather than builders. The author lists the prerequisites: Node.js, Python, the Salesforce CLI and Claude Code, with a Claude plan that includes Claude Code. The org must have the MCP Servers page under Integrations and API Catalog used to enable the metadata-experts and salesforce-api-context MCP Servers.

The walkthrough then installs the plugin with the claude plugin install command and runs the setup command to check the org connection. The author builds a worked example, The General Store, using prompts that create a DX project, an Equipment Loan Custom Object with picklists, a lookup and a long text field, two Permission Sets, and a Lightning Record Page. He reviews the generated XML to confirm the read, create and edit permissions match the requirements.

The piece closes with advice on safety. It recommends building in a sandbox, Developer Edition org or Scratch Org, keeping deployments in human hands, and giving the agent specific field names and permissions because the model is trained on generic data.

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

Worth reading?

Must-readFlow and admin

How Round Robin lead Assignment works in Salesforce, HubSpot and pipedrive (opens in a new tab)

You will learn how each of the three platforms rotates leads between reps, including the Salesforce formula and assignment rule setup and the common reasons assignment rules fail to fire.

Why read this

You will also see how availability, weighting and rule order differ between them.

Salesforce

  • No round robin switch built in
  • Autonumber, formula and rule entries
  • Edit formula when team changes

HubSpot

  • Rotate record to owner action
  • Load balanced, round robin, random
  • Assign to available users only
Salesforce and HubSpot round robin setups differ in what the platform provides

Round robin lead assignment hands each new lead to the next rep in a fixed order, which suits teams where reps sell the same thing and leads are broadly alike. The article sets it against weighted, load-balanced and rules-based approaches, and notes that real setups usually combine rules to pick a team with a rotation inside it. It lists four common cases where a plain rotation breaks down: leads from existing accounts, uneven lead quality, reps who are away, and reps who own territories.

In Salesforce there is no round robin switch. The article walks through the build: an Autonumber field, a Round Robin ID formula using MOD over the number of reps, and one Assignment Rule entry per rep, with a catch-all entry at the bottom. Each time a rep joins or leaves, the formula and entries must be changed by hand. The article then lists why rules often appear not to fire, such as API calls missing the AssignmentRuleHeader, Data Loader imports without the rule ID, the Lightning checkbox setting, and Flows using the Run Immediately path.

HubSpot uses the Rotate record to owner workflow action, available on Sales Hub and Service Hub Professional and Enterprise, with options for round robin, load balanced and random, and an option to skip users who are set to Away. Its first assignment is random, counts are kept per action, and changing owners resets the counts. Pipedrive offers automatic assignment on Professional and higher plans, where each rule keeps its own rotation, there are no caps or weights, and a rep on leave must be removed from rules by hand.

A comparison table sets the three platforms side by side, covering built-in support, plan requirements, handling of absent reps, and how imports and API traffic are treated. The article then describes Operelio, a tool that applies routing before a lead reaches the CRM, and its routing rules, round robin and CRM checks.

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

Worth reading?

RecommendedDevOps

Two VS Code extensions bring visual context back to agent-driven Salesforce work (opens in a new tab)

You will learn what the Metadata Visualizer and Live Preview VS Code extensions show, which metadata types and UI bundles they cover, and how to open them.

Why read this

It helps you judge whether they fit a workflow built on agents and the Headless Toolkit.

Setup and XML route

  • Retrieve long XML file
  • Navigate Setup to change permissions
  • Retrieve updated metadata
  • Commit changes to version control

Headless Toolkit route

  • Query and modify from terminal
  • Edit metadata locally
  • No retrieve after changes
  • Run operations in parallel
Editing a Permission Set with and without the Headless Toolkit

Building with agents lets developers skip many Setup clicks, but it removes the visual context that makes Flows and Permission Sets easy to grasp. The post presents two VS Code extensions, Metadata Visualizer and Live Preview, as a way to restore that context. It frames them as the visual companion to the Headless Toolkit, which combines agent skills, hosted MCP servers and the Headless Experience Layer.

The author describes the Headless Toolkit through a Permission Set example. Working through Setup meant retrieving a long XML file, navigating menus to understand and change permissions, then retrieving and committing the result. Through agents and the toolkit, the same change can be queried and edited from the terminal in seconds, locally and in parallel, without repeated round trips.

Metadata Visualizer renders read-only views of Salesforce metadata and comes with the Salesforce Extension Pack for VS Code. It covers agents, Flows, Lightning pages, objects and Permission Sets as of November 2026, and is opened by clicking Visualize in the editor. Users can analyze in the visualizer and ask an agent to apply changes, and with Agentforce Vibes they can select elements to have the agent edit them. Live Preview covers Lightning Web Components and Multi-Framework UI bundles, using live org data, and HXL widgets, using sample data that can be customized as JSON.

The post closes by suggesting that future interactive widgets could show metadata directly in agent responses, replacing some of these extensions and builders.

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

Worth reading?

RecommendedAgentforce and AI

A four-bucket Kit of 100 prompts for Admin work with Agentforce Vibes (opens in a new tab)

You will learn how the Admin Accelerator Kit's four prompt buckets (Understanding, Configuring, Troubleshooting, Documenting) are meant to be used, and which prompts to run first in a sandbox.

Why read this

You will also see how the buckets chain together on a real change, such as converting a text field to a picklist.

  1. Understanding: map what the org already does
  2. Configuring: plan, then build the change
  3. Troubleshooting: diagnose what breaks
  4. Documenting: record the change and the why
The four prompt buckets are meant to be used in sequence on a single change

The post introduces a set of 100 ready-made prompts for everyday admin tasks, presented at a Dreamforce 2026 session on Agentforce Vibes. The prompts are hosted as a markdown file in the Admin Accelerator Kit on GitHub, and readers can simply browser-copy them. They are organized into four buckets of five categories with five prompts each, and placeholders in angle brackets must be replaced with real API names. The authors note the prompts also work with other agents connected to a Salesforce org through MCP.

The author advises starting in a sandbox or Developer Edition org, especially for Configuring prompts, because Understanding and Documenting prompts mostly read metadata while Configuring prompts change it. Understanding prompts help map objects, Flows, permissions and business processes, and impact-analysis prompts help check what breaks before a field change. Configuring prompts range from “How do I” questions that yield click paths to “Create” and “Write” prompts that generate Flow or Validation Rule metadata for review before deployment.

Troubleshooting prompts cover Flow errors and permission problems, with the advice to paste the full fault email along with record IDs and the affected user. The kit also addresses conflicting automations that silently revert field values. Documenting prompts produce data dictionaries, release notes, deployment checklists and, most importantly, a record of why a rule was configured as it was.

The post closes by showing the buckets chained together on a Region picklist change, and invites feedback and contributions to the kit’s repository.

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

Worth reading?

Architecture

A blameless postmortem template for Salesforce incidents caused internally (opens in a new tab)

You will get a reusable postmortem template for Salesforce incidents, with the org queries to rebuild the timeline and a method for finding where warnings were lost.

  1. Build the timeline from org records
  2. Search tickets and chat for earlier warnings
  3. Ask each person individually what they saw
  4. Record contributing factors by role, not name
  5. Assign each change an owner and a due date
The order in which a blameless postmortem is built, as the article describes it

The author argues that when a Salesforce production incident happens, the first question is often who deployed, which discourages people from speaking up. A blameless postmortem instead asks how the process let the problem through and whether anyone saw it coming. The piece offers a template with sections for the incident summary, timeline, what the team knew beforehand, contributing factors, and a changes table with owners and due dates. Two rules keep it blameless: names appear only in the timeline, never in contributing factors, and every action needs an owner and a date.

To build the timeline from the org, the article points to Setup Audit Trail, which can be queried with SOQL on SetupAuditTrail for the last seven days or exported with the Salesforce CLI. It also suggests checking Setup > Deployment Status for recent deployments and their initiators, and Flow and Apex error emails for exact timestamps and failing elements. If nobody receives those error emails, the author says that gap itself belongs in the changes table.

The section on what the team knew before is presented as the most important part. The author recommends searching tickets, pull request comments and chat threads, then asking people individually whether they noticed a concern and whether they raised it. Where a warning was raised but lost, the document should say so plainly, since it shows where the process drops warnings. The article closes with tips for running the review meeting, such as having the most senior person speak last.

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

Worth reading?

Flow and admin

How to set up Enhanced Omni-Channel Routing for Service Cloud agents (opens in a new tab)

You will learn what Enhanced Omni-Channel requires, how queue-based, skill-based and external routing differ, and the main steps to enable routing and test it.

Why read this

You will also know that Standard Omni-Channel was retired in Summer '26 and that existing configurations carried over.

  1. Turn on Enhanced Omni-Channel Routing
  2. Choose queue-based or skill-based routing
  3. Configure queues or skills and agents
  4. Define routing configurations
  5. Test with a sample case
The order of steps for a first-time Enhanced Omni-Channel setup

Standard Omni-Channel was retired in Summer ’26, and Salesforce upgraded orgs automatically during the rollout. Enhanced Omni-Channel, generally available since 2023, takes work items such as Cases, Leads, chats, messaging sessions and voice calls and routes them to reps based on availability, skills, capacity and priority. Existing routing configurations, queues, skills and routing rules were carried over. The feature requires a Service Cloud license or one of several add-on licenses, and it works only in Lightning Experience.

To enable it, go to Setup, then Feature Settings, then Service, then Omni-Channel Settings, and turn on Enhanced Omni-Channel Routing. The article describes three routing options: queue-based routing for smaller teams and simpler product lines, skill-based routing for complex cases that need specific expertise, and external routing for keeping logic in a third-party tool that connects through APIs. Enhanced Omni-Channel adds destinations including a queue, a skill, a specific rep and an Agentforce Service Agent.

Queue-based setup can be started with the guided flow under Omni-Channel Setup, which covers creating a queue, assigning agents and setting workload, followed by defining routing configurations. Skill-based setup is more involved: enable Omni-Channel and Field Service settings, create Skills, create active Service Resource records for agents with skill levels and dates, define Skills-Based Routing Rules through skill mapping sets, and confirm the routing configurations use those skills.

The article closes by describing the agent experience: the Omni-Channel Utility Bar item in the Service Console, where agents log in as available and receive incoming work with an audio notification. Its advice is to start with the simplest setup that covers the team, test with a sample Case, and add precision later.

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

Worth reading?

Agentforce and AI

Writing clearer prompts for agents when you administer Salesforce (opens in a new tab)

You will learn eight writing principles for prompting an agent on admin work, and see a weak prompt rewritten into a strong one for a Validation Rule.

Why read this

The advice applies to any agent request you make.

Joshua Birk argues that prompting an agent is a writing skill rather than a form of engineering, and that admins can apply the communication habits they already have. He notes that a good prompt is usually three to six plain-language sentences that name the exact objects, fields and Flows by API name, explain the business reason, and state the output wanted and the guardrails. A one-line prompt tends to cost several rounds of clarification, while a few extra sentences up front save them.

The article then sets out eight lessons: know your audience, lead with the goal, be specific, give context and explain why, define the output format, show examples, use plain language, and set constraints. Each comes with an admin example, such as naming the team size so the agent pitches its answer correctly, or pasting an existing Validation Rule so the agent follows its naming pattern. Constraints such as working only in a sandbox or not touching active Flows are written into the prompt from the start.

To show the lessons together, Birk rewrites a vague request to create a close-reason Validation Rule into a detailed prompt covering the object, field, error message, naming convention, length limit and a no-deploy instruction. He closes by saying that one prompt rarely produces a finished solution, so admins should plan follow-up prompts, and he points to Trailhead modules and a GitHub kit of 100 admin prompts.

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

Worth reading?