Today5 stories · 3 briefs

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

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

Must-readAgentforce and AI

Building a shared semantic model for conversational analytics with Data 360 and Tableau semantics (opens in a new tab)

You will learn the workflow for defining business metrics in OSI YAML, converting them to a Tableau SDM, validating and querying the model, and exposing it to Agentforce and MCP clients.

Why read this

The piece gives the concrete API commands needed to do this.

  1. Ingest CRM data into DLOs
  2. Define metrics in OSI YAML
  3. Convert to SDM JSON
  4. Create and validate the model
  5. Query via Semantic Query API
The workflow runs from ingested data through the OSI specification to a queryable semantic model

The post argues that AI agents need a shared semantic layer so that terms such as revenue and pipeline are defined once and reused across reports, applications and agent answers. Data 360 ingests CRM records into data lake objects, and a Tableau semantic data model adds relationships, metrics and calculations on top of them. Business context is captured first in an OSI YAML specification, which the Salesforce converter translates into an initial SDM JSON file.

The article walks through creating, validating and querying the model with Salesforce APIs, including the converter command, the model creation and validation requests, and a semantic gateway query. It also covers business preferences that steer agent terminology and scope, and verified questions created through Q&A Calibration to make answers more consistent. Agentforce and Claude connected through MCP are shown answering the same pipeline question from the same model.

The post notes that governance through Data 360 classifications, tags and policies can limit access to sensitive data. Its conclusion recommends starting from one business question, defining its terms, validating results, and then extending the shared foundation to more questions and agents.

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

Worth reading?

RecommendedArchitecture

Lessons from building a Flow Version Cleaner on the Tooling API (opens in a new tab)

You will learn how to choose between the Tooling API, Metadata API and Apex Metadata for deleting flow versions, and how to handle authentication, object dependencies and state across asynchronous jobs.

Why read this

The piece also sets out safeguards for destructive metadata automation.

  1. Keep the active flow version
  2. Keep newer versions under review
  3. Keep recent inactive versions as fallback
  4. Delete flow interviews via callouts
  5. Delete remaining obsolete flow versions
The cleaner's flow version decision sequence, from protected versions to safe deletion

The author built an open-source Flow Version Cleaner to prune obsolete flow versions in orgs with hundreds of flows. The tool keeps the active version, keeps newer versions that may be under review, and retains a configurable number of recent inactive versions as a fallback. Requirements were refined during the build, once it became clear that version numbers alone do not show which versions are safe to remove.

The article compares the Apex Metadata namespace, the Metadata API with destructive changes, and the Tooling API. The Tooling API was chosen because it lets each flow version be queried and deleted individually at run time, so one failure does not roll back the whole run. Authentication uses Named Credentials rather than the running user’s session, since session IDs can be null in asynchronous work and should not carry the permissions of whoever started the job. Flow interviews must be deleted before flow versions, and because Apex does not allow a callout after DML in the same transaction, both steps use callouts. Versions owned by managed packages cannot be deleted by subscribers.

For asynchronous work, the author recommends building an explicit payload between jobs, since inner-class fields can arrive null without any error, and using one snapshot of org state for both the decision and the action. Destructive metadata work should run in dry-run mode first, record every candidate, and isolate failures, because deleted metadata cannot be restored from the Recycle Bin.

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

Worth reading?

RecommendedFlow and admin

Rehearse a Salesforce Data load locally before uploading to the Org (opens in a new tab)

You will learn how to simulate a Salesforce data load against your project's triggers, flows and Validation Rules on your own machine, catching refused rows before any reach the org.

Why read this

The piece is a product walkthrough, so treat its claims about the runtime's fidelity with some caution.

  1. Map the CSV onto an object
  2. Simulate rows in a rolled-back transaction
  3. Fix refused rows and simulate again
  4. Upload to Org
How a data load is rehearsed before it reaches the org

The article argues that a Salesforce data load is effectively a deploy: each row runs through the org’s triggers, Validation Rules and flows, and problems usually surface only after the rows are in. It presents Renmy runtime, a local Apex runtime that runs the same automation on a developer’s or admin’s own computer against an embedded database, with no org, Scratch Org or sandbox needed. The piece is a vendor product walkthrough, so its claims about how closely the runtime matches Salesforce should be read with caution. The article points to a public parity record, which it says lists where the runtime matches the platform and where it does not.

The walkthrough runs in IntelliJ IDEA through the plugin Renmy Runtime - Salesforce IDE. The user opens the Salesforce DX project their developers keep in version control, which supplies the triggers, flows and Validation Rules. They then load a CSV in the plugin’s Data Loader, map its columns to object fields, and flag unreadable cells before anything runs. Pressing Simulate processes the rows in batches of 200 inside a transaction that is rolled back, and reports which changes would be made and which rows would be refused, with the platform’s own error messages. The user fixes the file and simulates again as often as needed, and only then uses Upload to Org to send the same file to a chosen org, with a confirmation that names the org and row count. The example is an invoice update in which three rows fail a Validation Rule and three dates cannot be read.

The article also describes a Workbench for editing individual records with automation switched on, and a Save as Fixture option that turns rows into test data for developers. It is explicit about the limits: the rehearsal cannot see automation that exists only in the org until it is retrieved, and for updates the referenced records must also exist locally, where Clone Org Data can copy a slice of the org down. The org remains the final authority. The article also says the rehearsal does not contact an org and keeps source, schema and data on the local machine, and that the Free tier covers the Data Loader and Simulate. It describes the Pro tier as free during the public beta, with a listed price of $19 a month afterwards. It presents the tool as suited to admins with no coding skills, though a developer’s project checkout is needed.

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

Worth reading?

DevOps

Running Apex tests locally lets new developers skip the sandbox wait (opens in a new tab)

You will learn how a committed renmy.properties file and a local Apex runtime let a new developer run the full Apex test suite on day one without an org.

Why read this

You will also see the same command reused in CI, with its trade-offs.

  1. Clone the repository
  2. Install renmy runtime
  3. Run renmy doctor
  4. Run renmy test
Day one with a local Apex runtime takes four steps, none of which needs an org

The article argues that onboarding a Salesforce developer usually means waiting days for a sandbox, a user, a Permission Set and VPN access before the first Apex test can run. It presents renmy runtime, a local Apex runtime made by Renmy UG in Berlin, as a way to skip that wait. The tool executes Apex, SOQL, DML and Salesforce Flows on the developer’s machine against an embedded PostgreSQL, ships as one binary for macOS, Linux and Windows, and needs no org, Scratch Org, Docker or JVM. The author says governor limits are enforced and each test runs in its own transaction, and cites a public benchmark in which 837 tests ran roughly 45 times faster locally than in an org.

The article walks through a four-step day one: clone the SFDX repository, install the binary with a one-line script (or let the IntelliJ plugin or VS Code extension handle it), run renmy doctor to check the project layout, and then run renmy test “” or narrow it to a class or method. The test environment lives in a renmy.properties file that the team lead generates with renmy config init and commits to the repository. That file sets org defaults such as currency, locale and timezone, seeds Custom Settings so code reading getOrgDefaults() works without @testSetup, and defines a stricter ci profile. Permission Sets load from metadata already in the repository.

Some gaps still need attention. Managed packages whose source is hidden need stubs pulled once by someone with org access and then committed, and multi-currency orgs need a feature flag. The doctor output and failure traces name missing pieces, so closing a gap in the repository helps every later developer. Org access remains necessary for deployment and browser-based work, so the access request still goes in on day one but is off the critical path. The same renmy test “” command runs in CI with the ci profile and needs no connected org, though it requires a license key secret. The Free tier costs nothing per developer for one machine, while the Team tier adds CI runs and seat management, is free during the public beta, and lists at $49 per developer per month. The article concludes that sandboxes remain the right place for UI work and deployment.

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

Worth reading?

Career and certifications

Salesforce Ecosystem grows at the top while Salesforce talent demand contracts (opens in a new tab)

You will see where the Salesforce ecosystem is growing and shrinking, from partner counts and talent demand to salary trends.

Why read this

The piece shows why demand is shifting toward AI, data and revenue skills and away from generalist platform roles.

  • +14%: Consulting partners, to a record 4,247
  • −13%: Global demand for Salesforce talent, year on year
  • $3.9B: Agentforce and Data 360 annual recurring revenue
Partner growth and talent demand moved in opposite directions in 2026

Salesforce itself continues to grow. Its Q2 FY27 revenue reached $11.3B, up 11% year on year, with a $456M Informatica contribution, and Agentforce and Data 360 annual recurring revenue approached $3.9B. Even so, IDC shows Salesforce’s CRM market share slipping to 20% in 2025 from 20.7% in 2024.

The 10K Salesforce Ecosystem Report for 2026 counts a record 4,247 consulting partners, up 14%. Growth sits almost entirely among small firms with five or fewer certified experts, while every consulting tier above ten experts shrank. Global demand for Salesforce talent fell 13% year on year, though the authors say demand for AI, data and revenue management skills grew sharply while generalist skills dropped.

The author’s Salary Survey 2026 points the same way: 89.4% of respondents found the market harder than in past years, and among those who changed jobs, 41.6% reported lower pay against 22.6% who reported higher. The conclusion is that the ecosystem is changing shape, with growth concentrated in specialist areas and pressure on generalist roles, large firms and individual bargaining power.

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

Worth reading?

In brief