Today7 stories · 1 brief

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

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

Must-readArchitecture

Metadata Grounding lets coding agents search your org's Metadata by intent (opens in a new tab)

You will learn how the Metadata Grounding MCP Server indexes org metadata, how to connect it, and how to use describe, search and query so agents reuse existing components instead of rebuilding them.

  1. describe_metadata: list types and schemas
  2. search_metadata: find items by intent
  3. query_metadata: read the full record
The three Metadata Grounding tools run in order, so the agent checks the org before writing code

Coding agents working on a Salesforce org often build new components because they only see the part of the org that has been retrieved into a local project. The Metadata Grounding MCP Server (Beta) addresses this by searching a pre-indexed catalog of the whole org’s metadata, so an agent can check what already exists before writing code. It is one of three pieces in the Headless Toolkit, alongside Skills, which teach patterns, and the Headless 360 MCP Server, which lets the agent act. Metadata Grounding answers the question of what is currently in the org. It is read-only, runs as the authenticated user so it returns only what that user may access, and covers more than 70 core metadata types, though not Data 360 metadata.

The server exposes three tools: describe_metadata lists available types and their schemas, search_metadata finds components by natural-language intent with optional type and subtype filters, and query_metadata returns the full record for a result. The recommended workflow is describe, then search, then query. Behind it, Salesforce Catalog extracts metadata from the org, stores it in a Data 360 data lake object mapped to a Catalog data model, and indexes it with a hybrid of vector and keyword search. Catalog updates supported types incrementally and runs a full refresh every 24 hours, so very recent deployments may take time to appear.

The article illustrates two uses in Pronto, a sample food delivery org. In the first, a vague bug report about a non-working menu category was traced to an Apex controller and a Lightning Web Component found by describing the symptom, with the type filter narrowing noisy results. In the second, an agent found an existing Apex class with a summarize-reviews action and extended it rather than building a duplicate. The article advises adding a project rule telling agents to search the org first. It also covers setup: an org with a supported Data 360 edition, Salesforce Catalog enabled, and admin activation of the server, with the server available either standalone for any MCP client or inside the Headless 360 MCP Server, which will later be renamed the Salesforce MCP Server. Caveats include that search only finds candidates, which should be confirmed by query; the server does not return source code; and usage is metered in production but not in pre-production orgs. Planned additions are AI-generated metadata descriptions and a Metadata Graph for dependency analysis.

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

Worth reading?

Must-readDevOps

Catching AI-Generated Apex that breaks governor Limits with budget tests in CI (opens in a new tab)

You will learn how to measure governor limit consumption in Apex tests, set per-context budgets, and close the loop so AI agents fix limit-heavy code before it merges.

Why read this

The post includes a snapshot class pattern, a limits table and a retry-and-escalation design.

  1. Agent pushes code with bulk tests
  2. CI measures limit consumption
  3. Breach sends feedback to agent
  4. Up to two refactor attempts
  5. Human architect review if still failing
How the CI loop handles a governor limit breach in agent-written code

The article argues that AI-generated Apex can be functionally correct and fully unit-tested yet still exhaust shared transaction budgets, because agents build each feature in isolation and small additions compound until a governor limit is breached. Standard small-data tests rarely expose this, and since governor limits are platform capacity ceilings, the author recommends treating them as architectural contracts and enforcing them automatically before code merges. It illustrates the compounding with a sprint-by-sprint example where SOQL consumption climbs from 15% to 59% through individually harmless changes.

The proposed approach has several parts. Teams should supply a shared, immutable GovernorLimitSnapshot test utility, require agents to write bulk tests of 200 records that capture before and after snapshots, and have CI verify that these test conventions are present. A table compares synchronous and asynchronous limits, and a budget-allocation table recommends consumption thresholds by execution context: roughly 40 to 50% for trigger code, 60 to 70% for service classes, 80 to 85% for isolated asynchronous jobs, and 20 to 30% for Scheduled Apex. Snapshots should be taken just before Test.stopTest() so the synchronous footprint is measured separately from asynchronous work, which is tested in its own method.

The article then describes a closed feedback loop in CI. When a test breaches its budget, a structured prompt containing the metric, consumption, threshold and required optimization steps goes back to the agent, which gets up to three attempts, with the delta between attempts supplied on later tries. If the third attempt fails, the merge is blocked and a human architect is asked to review, possibly moving the logic to Queueable. Agents must not be allowed to weaken tests or thresholds, and the author notes that some limits, such as callouts and Platform Event publishing, need production monitoring as well. Thresholds should start generous, use warning and violation tiers, and be tightened over time, with a closing checklist for rolling the pattern out.

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

Worth reading?

RecommendedAgentforce and AI

Quick Pages beta lets users build governed single-page views in Salesforce (opens in a new tab)

You will learn what Quick Pages does, how its Permission Sets and read-only beta limits affect your org, and what is planned next.

Why read this

Useful if you plan to let users build their own views.

  1. Describe the page in natural language
  2. Review a live preview as it is built
  3. Share with individuals, groups or the org
How a user builds and shares a Quick Page in the beta

Quick Pages, now in beta, lets users in an org build and share their own single-page apps with charts, data tables, tabs and actions, described in natural language through Agentforce Coworker or the Quick Pages tab. The pages are grounded in the org’s metadata, including Custom Objects and fields, and show a live preview while they are built.

The pages follow the standard Salesforce security model, so users see only the data they can access, and they pull from live data rather than going stale. Building a page does not change the org’s metadata. Admins control access with the “Create and View Quick Pages (Beta)” and “View Quick Pages (Beta)” Permission Sets, and can view and manage every page. The Headless Toolkit applies the same permission checks and data rules whichever client builds the page.

During beta, AI chat is free but will be metered at general availability. Pages built in beta are read-only, so users cannot change records from them yet, and they will remain viewable after general availability. Planned additions include record editing, Apex and Connect REST API data sources, Data 360 support, and a Claude integration.

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

Also told by Salesforce Ben (opens in a new tab)

Worth reading?

RecommendedData Cloud

Setting up proactive Intelligence in Tableau Next with Slack and MCP (opens in a new tab)

You will learn the setup path for Tableau Next's three proactive features: autonomous insights, data alerts and intelligence briefs.

Why read this

You will also see how admins scope agents and users, and how alerts are created and managed through Slackbot.

  1. Set up Tableau Agent in Tableau Next
  2. Connect Slack to Salesforce
  3. Enable Tableau Next MCP server for Slackbot
The one-time admin setup that connects Tableau Next to Slack and MCP

Proactive Intelligence in Tableau Next has Tableau Agent monitor business data in the background and push prioritized insights to Slack, Salesforce or any MCP-compatible client. The article describes three capabilities that work together: autonomous insights, which explore data for risks nobody thought to ask about; data alerts, which notify on conditions such as a commit drop or a large deal slipping; and intelligence briefs, which run scheduled or on-demand reviews of core KPIs. All three draw on the governed semantic model so calculations follow the organisation’s definitions.

Setup is a one-time admin task. Prerequisites are Tableau Next in Enterprise, Performance or Unlimited edition, at least one AI-ready semantic data model, and Slack with the Salesforce app and Slackbot connected to MCP. The admin sets up a Tableau Agent, connects Slack to Salesforce, and enables the Tableau Next MCP server for Slackbot. For autonomous insights, the admin turns on the feature under Administration settings, scopes the agent to semantic models, creates an Agentforce Studio skill that supplies business context without scripting output, grants the AI Skill User Permission Set, and assigns an agent to each user, since no one receives insights until that step is done.

Alerts can be created in plain language through Slackbot, or through built-in metric alert types such as period-over-period change, unusual change, goal and threshold. Alerts check daily or weekly and notify only when the condition is met. The article recommends a phased rollout: start with one key alert, pilot autonomous insights with a small group of leaders, then automate one recurring review with an intelligence brief.

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

Worth reading?

DevOps

Detecting wrong-parent Contacts after a migration using External IDs and SOQL (opens in a new tab)

You will learn how to test whether Contacts still point to the correct Account after a migration, using External ID keys, a child-to-parent SOQL export, and a source-to-target comparison.

Why read this

The method works with native tools and needs no third-party code.

  1. Confirm keys are unique
  2. Export Contacts with parent key
  3. Match Contacts on their key
  4. Compare Account keys
The wrong-parent check compares Account keys for each Contact across two orgs

Record Ids usually change between orgs, so comparing AccountId values across a migration tells you nothing. The article proposes a stable External ID on both Account and Contact, then checks that the parent Account’s key is the same on each side for every Contact.

The workflow starts with uniqueness and blank-count queries on the keys, then uses a single child-to-parent SOQL export from Contact via Data Loader to pull Account.External_Key__c onto each row. The same view can be built as a Contacts & Accounts report. Rows are then matched on the Contact key and the Account keys compared, with blanks flagged as unresolved and missing rows reported separately.

The author notes limits: the method needs a shared stable key, Data Loader does not support nested subqueries, and a clean parent check does not validate field values, sharing or record types. The article is written by the vendor of a paid CSV comparison tool, which it discloses.

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

Worth reading?

Agentforce and AI

AIforce is a separate Layer from Agentforce, and developers shift to design and review (opens in a new tab)

You will learn how the Headless Toolkit and AIforce differ from Agentforce, and how the developer role is shifting toward guidelines, review and guardrails.

Why read this

The piece is a session recap rather than a technical guide.

Headless Toolkit

  • MCP Servers
  • Headless Experience Layer
  • Multi framework support
The Headless Toolkit has three pieces that together open Salesforce to any agent

The author writes that AIforce does not replace Agentforce. Agentforce remains Salesforce’s own AI, while AIforce is the layer that opens Salesforce to any MCP client or agent, together with partnerships with agent vendors. He lists the Headless Toolkit’s parts: MCP Servers that expose business logic to any agent, a Headless Experience Layer that renders interfaces dynamically inside agents, and support for frameworks such as Angular and React alongside Lightning Web Components.

According to Alba Rivas of Salesforce, as cited in the piece, the classic workflow of creating objects, writing queries, classes, tests and deploying has less time left. The developer’s work moves to design (asking an agent for a solution that follows your guidelines), review (checking that output matches the request), and guardrails (giving the agent knowledge and limits). Building an app that works in a production enterprise environment is the hard part.

The piece also notes that the Claude relationship continues with an existing Salesforce plugin, while OpenAI and NVIDIA also appeared on stage. It describes MCP as becoming a universal protocol used by business users too, and skills as Markdown files that can be shared across a team.

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

Worth reading?

Flow and admin

Salesforce Health Insights scans an org and ranks what to fix first (opens in a new tab)

You will learn what Salesforce Health Insights does, its two pillars of Product Adoption and Implementation Health, and who can access it in the Winter '27 release.

Why read this

The piece stays at the level of an overview and does not explain how to configure it.

  1. Scan org configuration and usage
  2. Evaluate against benchmarks
  3. Rank findings by severity
  4. Deliver next best actions
How Salesforce Health Insights turns an org scan into next actions

Salesforce Health Insights is a Salesforce-native solution that scans an org, evaluates it against benchmarks, and turns the findings into prioritized next best actions. The article presents it as a way to replace a manual org health review, which it says can take up to three weeks, with an on-demand scan that returns ranked results in near real time. The recommendations are built from the org’s own configuration, feature set and usage patterns, and ranked by criticality and the effort needed to fix them.

The tool has two pillars. Product Adoption shows which licensed capabilities are owned, which are used, and where there is room to grow, including license utilization over the past 30 days. Implementation Health delivers severity-ranked insights across Security and Process Automation, with recommendations meant to reduce exposure and prevent automation failures. The article also describes a headless delivery model, with a conversational view inside Salesforce and access through Slackbot outside it.

According to the article, Salesforce Health Insights is available with the Winter ’27 release for Signature Success Plan customers on Core products at no extra cost, and is found by searching for it in the App Launcher. The piece is a product announcement written by Salesforce and gives no detailed configuration steps or measured results.

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

Worth reading?

In brief