Today8 stories

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

Vol. I · No. 6The independent daily for Salesforce admins, developers and architects8 stories

Must-readAgentforce and AI

Preparing your org for the Claudeforce partnership and new billing model (opens in a new tab)

Readers will learn how to configure the Salesforce in Claude plugin, audit permissions for agentic access, and prepare for the November billing model using Flex Credits and agent registration.

  1. Audit Permission Sets and profiles
  2. Clean the fields the skills read
  3. Keep approvals on
  4. Pilot in a sandbox
  5. Name an owner for connections
Five checks to prepare your Salesforce org for Claudeforce and AIforce billing

Claudeforce, the expanded Salesforce and Anthropic partnership announced on August 26, 2026, works in two directions. Claude becomes a reasoning model inside Agentforce and the default model in Slack, while Salesforce reaches into Claude through the Salesforce in Claude plugin. That plugin bundles 37 prebuilt sales skills covering account research, call prep, pipeline review and CRM updates, with Salesforce and Slack connectors. It is in beta for approved orgs on paid Claude plans and requires the latest Sales Cloud Enterprise edition.

On security, sellers sign in with their own Salesforce credentials, so Claude can only do what their permissions allow, and by default it asks for approval before any write. Salesforce Help notes that when a custom action uses a Claude model hosted inside the Salesforce Trust Boundary, data stays inside that boundary, though Einstein Trust Layer data masking is disabled for those agents and zero data retention still applies. The article advises reading that page in full before writing a risk assessment, and it warns that most capability claims come from launch material and should be tested in a sandbox first.

The setup path has four stages. First, the org confirms eligibility and gets approval through the beta sign-up on AgentExchange. Second, a Salesforce admin creates an External Client App for Claude, because Connected Apps are not supported for MCP clients. Third, a Claude Primary Owner or Owner enables the plugin in Organization settings and enters the app’s consumer key and secret. Finally, each member signs in with their own Salesforce account on first use.

The billing changes are targeted for November. Admins register agents, each of which gets its own identity and can hold a narrower Permission Set than a human user. Every successful MCP or API call from a registered agent counts as a Headless Platform Interaction, paid with Flex Credits, though the rates are still TBA and metering applies only to active production orgs, with 30 days’ notice before it starts. Customers who buy on or after September 17, 2026 must register agents at purchase, while existing customers register at renewal. The article does not say how the Salesforce in Claude plugin will be classified under this model.

The article recommends five preparation steps: audit Permission Sets and Profiles, clean the fields the skills read, keep approvals switched on, pilot in a sandbox, and name an owner for connections and consumption. Cloud Odyssey’s own view is that Claudeforce exposes existing CRM data quality problems, and it suggests starting with a health check, connecting surrounding systems, piloting with one team, and keeping model choice open.

Read the original at Cloud Odyssey (opens in a new tab)

Worth reading?

Must-readAgentforce and AI

Configuring permissions and security guardrails for Agentforce and Prompt Builder (opens in a new tab)

Readers will learn how to structure Permission Sets and groups for different AI roles, understand how field-level security applies at runtime, and implement human-in-the-loop controls for autonomous agents.

Generative AI Security Setup

  • License and Permission Set Allocation
  • Field-Level Security Inheritance
  • Agentforce Action Boundaries
Breakdown of the three core pillars for AI governance

The article outlines a structured approach to managing generative AI access by separating feature availability through Permission Set Licenses from functional capabilities via Permission Sets and Permission Set Groups. It defines four core roles, including an AI System Administrator, Prompt Template Author, Standard End-User, and Agentforce Runtime User, emphasizing that bundling permissions into groups prevents security drift when users change departments.

When prompts execute on record pages, Prompt Builder enforces security before data reaches the large language model. The system validates object read access, applies field-level security by nullifying restricted merge fields, and respects Sharing Rules. A practical example shows how a customer support representative without access to a profit margin field receives a blank value, ensuring sensitive financial data never leaves the organization or enters the model cache.

For autonomous execution, Agentforce supports three action modes ranging from full autonomy to requiring explicit user approval. The piece recommends starting with safe defaults that allow read-only lookups while triggering human confirmation for write operations. It demonstrates a human-in-the-loop pattern where an agent drafts an email via a flow, leaving the final review and send capability restricted to a human user.

Finally, the guide provides a deployment checklist covering permission group assembly, field security verification, action boundary configuration, and Einstein Trust Layer settings like zero data retention and data masking to ensure compliance before production rollout.

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

Worth reading?

RecommendedAgentforce and AI

Building a custom Apex tool for Lead conversion with Salesforce Model Context Protocol (opens in a new tab)

You will learn how to configure a Salesforce Model Context Protocol server and write an Invocable Apex class to handle Lead conversion through AI agents.

Why read this

The piece clarifies why generic record mutation tools cannot replace the native conversion process.

Introduces Salesforce Headless 360 and the Model Context Protocol as methods for AI agents to interact with orgs. Explains that basic access is free but may consume Flex Credits.

Walks through creating a custom MCP server in Setup and notes that default tools do not support Lead conversion. Details the architectural reason why generic SObject mutation tools fail for this task, citing atomic execution, field mapping, deduplication, and related record reparenting.

Outlines the requirement to build an Invocable Apex class using Database.convertLead(). Describes the necessary annotations and access modifiers needed to expose the method to the MCP framework.

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

Worth reading?

RecommendedAgentforce and AI

Fixing time zone mismatches in Agentforce agents with proper input types (opens in a new tab)

You will learn how to prevent time zone conversion errors in Agentforce by enabling user profile context, adding explicit LLM instructions, and typing action inputs as ISO 8601 strings.

Why read this

The guide also shows how to structure these elements in an Agent Script that calls a Flow.

The article addresses a common failure mode where Agentforce agents misinterpret local time because Salesforce stores DateTime values in UTC while users communicate in their local time zones. It outlines three required components to fix this: exposing the user profile context, providing explicit reasoning instructions to the large language model, and defining action inputs with the correct data type.

A complete Agent Script example demonstrates an Employee Agent that manages calendar events. The script enables the user profile context to retrieve the current user time zone without asking the user. Reasoning instructions direct the model to apply that time zone for display purposes while omitting offset details from the conversation. Conditional logic gates event actions behind a valid record identifier.

The workflow passes deterministic parameters like account identifiers directly to the Flow, leaving only the start datetime field open for natural language processing. By assigning the lightning__dateTimeStringType complex data type to that input, the agent converts conversational phrases into structured ISO 8601 values before handing them off to the downstream Flow.

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

Worth reading?

Agentforce and AI

Managing Restricted Picklists in Agentforce through dual-layer validation (opens in a new tab)

You will learn how to prevent FIELD_INTEGRITY_EXCEPTION errors when Agentforce updates Restricted Picklist fields.

Why read this

The piece outlines a dual-layer strategy combining explicit prompt instructions in the Agent Definition with runtime validation in Lightning Flow.

When Agentforce processes natural language requests to update Restricted Picklist fields, the underlying large language model often passes synonyms or different casing that do not match the exact API names. This mismatch triggers a FIELD_INTEGRITY_EXCEPTION during Flow execution.

The author recommends a dual-layer validation approach to solve this. The first layer occurs at the Agent Definition stage, where developers configure action parameters using structured instructions. These instructions whitelist exact values, define case sensitivity, map common synonyms to valid API names, and direct the model to request clarification instead of guessing invalid inputs.

The second layer enforces checks within the backend Lightning Flow before any record update occurs. By combining strict prompt guardrails with explicit flow logic, practitioners can ensure reliable data ingestion while maintaining the integrity of Restricted Picklist fields.

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

Worth reading?

Agentforce and AI

Configure Prompt Builder to ground Flex templates with Salesforce Files (opens in a new tab)

Readers will learn how to configure a Flex Prompt Template in Prompt Builder to automatically pass Salesforce Files attached to a record as context for an AI model.

Why read this

The guide covers prerequisites, step-by-step setup, sample prompt syntax, and security best practices.

Prompt Builder now allows administrators and developers to attach Salesforce Files from a record Related List directly into a Flex Prompt Template. This grounds artificial intelligence models with actual document content instead of relying solely on record fields, reducing manual review time for tasks like vendor evaluation or contract analysis.

The setup requires three main actions inside Prompt Builder. First, create a Flex Prompt Template to define custom inputs. Second, add an Object type input pointing to the target record, such as Account. Third, insert the Notes and Attachments Related List as a resource within the prompt workspace so the system can resolve the attached files during execution.

Only Salesforce Files are supported, meaning legacy classic attachments must be converted before testing. Builders must assign the Prompt Template Manager Permission Set or Customize Application permission, and select an artificial intelligence model that accepts file inputs. The article recommends previewing templates with representative records, screening documents for sensitive data, and maintaining human oversight for generated summaries.

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

Worth reading?

Flow and admin

Decouple dynamic business rules from Salesforce Flow using reference tables (opens in a new tab)

You will learn how to move static routing logic out of Flow elements into external reference tables, reducing deployment risk and enabling non-technical staff to manage updates.

The article argues against hardcoding business rules directly inside Flow decision nodes or Formula Fields, explaining that this practice creates maintenance debt and increases deployment risks. Instead, it recommends externalizing ever-changing logic into reference tables stored as either Custom Objects or Custom Metadata Types.

A detailed comparison outlines when to choose each storage method, noting that Custom Objects are better for frequently updated operational data managed by business users, while Custom Metadata Types suit static configuration moved through deployment pipelines. The author walks through building a territory assignment engine using a Custom Object to route Opportunities based on postal codes.

Key implementation details include optimizing the Flow for fast field updates, using a Get Records element with a CONTAINS filter, and sorting results by last modified date to handle overlapping rules safely. The piece also warns about partial string matching pitfalls and suggests padding delimiters to prevent incorrect matches.

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

Worth reading?

Architecture

Optimizing Apache Spark workloads at scale using telemetry and evidence-based tuning (opens in a new tab)

You will learn how to collect execution telemetry without modifying application code and validate resource sizing changes against runtime and reliability metrics before production rollout.

The Salesforce engineering team addressed inefficient compute allocation across millions of daily Apache Spark jobs by shifting from success-based metrics to evidence-driven resource sizing. They identified that successful job completion often masks unused capacity, pod churn, and unnecessary executor allocations.

To gather comparable measurements without altering customer applications, the team instrumented a shared submission gateway using open-source listener hooks. These listeners exported structured telemetry through Kafka into a curated analytical layer, which standardized metrics for applications, jobs, stages, and executors while explicitly tracking missing data and retry semantics.

The team used the modeled data to distinguish between genuine waste and underlying bottlenecks like shuffle failures or memory pressure. By testing targeted reductions in initial executors and maximum limits, they validated changes against p95 runtime, spill rates, and platform health indicators. The adjustments yielded a thirty-one percent weekly compute cost reduction without degrading performance or increasing failures.

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

Worth reading?