Today7 stories · 1 brief

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

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

Must-readFlow and admin

Checking dependent picklist combinations by Record Type before a CSV load (opens in a new tab)

You will learn how to snapshot dependent picklist values per Record Type from the UI API and run a local preflight that flags CSV rows whose controlling and dependent values do not fit the intended target configuration.

Why read this

The piece is clear that findings are review prompts, not proof of import rejection.

  1. Save per-record-type dependent picklist response
  2. Preserve exact API values in the CSV
  3. Run local preflight against saved metadata
  4. Review each non-match row with its owner
The preflight runs in four stages before any row is trusted

The article argues that dependent picklist checks must be made on the pair of controlling and dependent values for the target Record Type, since a value valid in one Record Type may not be valid in another, and checking each column against a global list misses this. It recommends saving the dependent field response from the UI API object-info endpoint for each intended target Record Type, recording the org, API version and access scope, and keeping API values rather than translated labels.

A Python 3 standard-library script is provided that reads the saved metadata and a CSV, then assigns each row a status such as CONFIG_MATCH, COMBINATION_NOT_AVAILABLE, VALUE_NOT_AVAILABLE_FOR_TYPE, UNKNOWN_CONTROLLER or REVIEW_BLANK. The worked example with invented fields shows one match and five rows for review, and the script deliberately treats malformed or incomplete metadata as a review case rather than a pass.

The author is explicit about limits: the snapshot reflects UI-available combinations for the reader’s access, not full server validation, and required fields, Validation Rules, Flows, field-level security and import-path behavior still need separate review. The approach is scoped to a single confirmed controlling and dependent single-select pair.

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

Worth reading?

Must-readDevOps

Running Apex tests in CI without a Scratch Org, with gated deploys (opens in a new tab)

You will see how Apex tests can run on a CI runner against a local runtime, what a gated deploy with a check-only validation looks like, and the trade-offs of keeping the org only for the final deploy.

Why read this

The piece is also a product pitch for renmy, so weigh its benchmark claims accordingly.

  1. Run local runtime gates on the bundle
  2. Check-only validation of the same bytes
  3. Deploy to the target org
The gated deploy sequence renmy deploy follows before any metadata reaches the org

The piece argues that most Salesforce CI pipelines waste time and reliability on provisioning a Scratch Org or shared sandbox just so Apex tests have somewhere to run. Its proposed alternative is renmy runtime, a local Apex runtime that executes Apex, SOQL, DML and Salesforce Flows on the CI runner itself, backed by an embedded PostgreSQL database. The author says this removes the need for a JWT certificate, a Dev Hub allocation or a Scratch Org for the unit-test job, and that tests finish in seconds with JUnit XML and Cobertura coverage output. The runtime is presented as an interpreter that enforces governor limits and platform rules, not a mock framework or a transpiler. The piece includes a GitHub Actions example in which the only secret needed is a license key, and it notes that tests can keep running during a Salesforce incident even though deploys cannot.

The piece also describes a gated deploy command, renmy deploy. It snapshots the source into a content-addressed bundle, runs the local test and coverage gates against those exact bytes, then runs a real check-only validation of the same bytes in the target org, and deploys only after that succeeds. A coverage floor can be set with a minimum-coverage flag. For teams that need an approval step, a release command validates and writes a receipt containing the bundle digest, git revision, org fingerprint, gate results and validation job id. After approval, a deploy step quick-deploys the validated job within Salesforce’s 10-day window, or resends the stored bundle, and rejects changed, expired or wrong-org receipts. The author also covers pinning the Salesforce CLI version and recovering deploys stuck in the org’s Pending queue.

The author is candid that the org still matters for anything a person inspects, for integration tests against real endpoints, and for the final validation and deployment. The main claim to weigh carefully is the vendor’s own benchmark: about 1 minute 46 seconds to deploy and run 837 tests in an org against 2.4 seconds locally, roughly 45 times faster, with all tests passing in both. The method is published by the vendor and has not been independently verified in the piece. Branch coverage is reported locally but not by the org, so the two coverage figures are not directly comparable. The piece also notes that the Team tier, which covers CI runner use, is free during the public beta, with a listed price of $49 per developer per month, and that an individual Free tier exists.

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

Worth reading?

RecommendedFlow and admin

Builder Central is a beta hub for building apps and agents in plain language (opens in a new tab)

You will learn what Builder Central does beyond Setup with Agentforce, how its metadata visualizations and preview orgs protect your org, and the steps to enable the beta.

  1. Describe the app or agent in plain language
  2. Answer clarifying questions
  3. Review metadata and test in preview org
  4. Deploy to sandbox via Lifecycle Center
Builder Central takes a solution from plain-language idea to sandbox deployment

Builder Central is a new no-code experience in beta that lets admins build and deploy apps and agents from plain-language prompts. It works as one hub for work that would otherwise be spread across Setup and several builders, and it draws on the org’s existing data model, configuration, security and permissions so that what it creates fits the business and inherits access controls.

The article distinguishes it from Setup with Agentforce, which makes direct, simple administration changes such as creating a field. Builder Central targets larger builds like full data models, flows and agents. It asks clarifying questions before building, deploys through Lifecycle Center, and complements Flow Builder, Lightning App Builder and Agentforce Builder rather than replacing them.

To keep orgs safe, it offers interactive metadata visualizations for reviewing generated components and ephemeral preview orgs, temporary clones of a sandbox, where solutions can be tested before anything is published. To start, admins grant the Access Builder Central user permission, enable the beta feature and activate the Metadata Experts MCP Server in Setup, ideally in a Developer or Developer Pro sandbox.

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

Worth reading?

RecommendedFlow and admin

Building an e-invoicing process in Salesforce across german, belgian and french Rules (opens in a new tab)

You will learn how national e-invoicing rules in Germany, Belgium and France differ and what each means for Salesforce invoice data, configuration and exchange channels.

Why read this

The article also outlines a readiness checklist for a multi-entity org.

ZUGFeRD

  • XML embedded in the PDF
  • Human-readable PDF included

XRechnung

  • Structured XML file
  • No PDF included as part of format
Germany's ZUGFeRD and XRechnung formats differ in how they carry structured data

The article argues that a Salesforce team cannot treat European e-invoicing as one rule set. Each legal entity and transaction must first be checked against the applicable country’s deadlines, structured format and exchange method. Germany’s ZUGFeRD and XRechnung, which have transition periods running through 2026 and 2027, are contrasted with Belgium’s mandatory Peppol-based structured invoicing from January 2026 and France’s phased platform-based model starting in September 2026.

For the Salesforce implementation, the author recommends mapping the regulatory scope, defining the required output and exchange method, auditing that the needed seller, customer, tax, line-item and reference data exists at generation time, and adding controls with Validation Rules, Flow or Apex. The lifecycle should also cover receiving incoming e-invoices and handling corrections.

The piece then shows how the Finblick application on AgentExchange supports these needs with Legal Entity records, Matching Rules tied to Tax Rules, ZUGFeRD and XRechnung generation from the Invoice record, and Credit Notes for corrections. It closes by recommending testing across entity, country, VAT and correction combinations, and ongoing review as national rules change.

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

Worth reading?

LWC and UI

How LWR differs from Aura for Experience Cloud sites and what migration involves (opens in a new tab)

You will learn how Lightning Web Runtime delivers pages differently from Aura, where the performance gains come from and where they do not, and what an Aura-to-LWR migration usually involves.

Why read this

The piece helps you decide whether a new or existing site should move to LWR.

Aura

  • Components delivered dynamically
  • No republish for component changes
  • Broader existing template set

LWR

  • Static, cacheable resources
  • CDN can serve eligible files
  • Republish to expose component changes
LWR publishes cacheable resources, while Aura delivers components dynamically

Lightning Web Runtime (LWR) is the newer runtime behind Experience Cloud templates such as Build Your Own (LWR) and Microsite (LWR). Components are built with Lightning Web Components, and the site publishes prepared, cacheable resources that can be served through a content delivery network. Aura delivers components dynamically, so LWR can load faster, but the article stresses that speed is not guaranteed. Large images, unnecessary API calls and poorly designed custom components still slow pages, and integration changes may matter more than the storefront technology.

The main practical differences are in publishing and component support. Aura sites can pick up component code changes without republishing, while LWR sites must be republished for updated components to reach visitors. Standard LWR templates use LWC only, and LWR offers fewer templates and components than Aura, so some Aura features have no direct equivalent. Salesforce recommends LWR for new B2B Commerce storefronts and encourages migration from Aura-based B2B stores.

Migrating an Aura site usually means replacing Aura components with LWC, while many existing LWCs can be reused with few changes. The article advises inventorying components and dependencies, transferring storefront configuration, and testing the full user journey. It also recommends recording baseline performance with tools such as Lighthouse, WebPageTest and Core Web Vitals before and after migration.

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

Worth reading?

Flow and admin

How Salesforce Go organizes Feature Setup for admins (opens in a new tab)

You will learn what Salesforce Go is, which editions and permissions it needs, and how Feature Sets, Features and feature monitoring work in its setup dashboard.

Why read this

It is a practical orientation for admins adopting it.

  1. Turn on the feature
  2. Configure the setup steps
  3. Monitor it once completed
Enabling a feature from Salesforce Go follows three stages

Salesforce Go began as Sales Cloud Go to help Sales Cloud admins enable new features, and its scope now covers all Salesforce feature setup. It is found in the Setup menu, and it is available to users with the View Setup and Configuration permission in several editions with Service Cloud. Additional permissions may still be needed depending on the feature being enabled.

The dashboard groups cards into Agents, Features and Feature Sets, and each Feature Set bundles the features that work toward one outcome, such as the Capture & Auto-Qualify Leads set. Each feature links to Salesforce Help, and includes snapshots, videos and a Copy Details option for sharing with stakeholders. The author walks through turning on Sales Engagement from the dashboard, then configuring access with a Manage button or a Go to Setup button where the task lies elsewhere.

Once a feature is marked Completed, Salesforce Go can also be used to monitor it, manage its configuration, assign permissions and track license consumption where applicable.

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

Worth reading?

Agentforce and AI

Agentforce Coworker adds Teams, mobile and desktop access and a $50 per-user price (opens in a new tab)

You will learn what Agentforce Coworker now does across Microsoft Teams, mobile and desktop, what is available now versus later, and how it respects Salesforce permissions and governance.

  1. Employee delegates a job
  2. Coworker plans the steps
  3. Agents and flows run
  4. Results return for review
How Coworker handles a delegated job, as described in the article

Salesforce reports that more than 185,000 users are working with Agentforce Coworker, with usage up 21x in three months. The release adds Conversation History, reusable Skills and scheduled tasks, plus connections to Google Workspace and Microsoft 365 so that email, calendar and file data can sit alongside Salesforce records. Coworker can be used from Microsoft Teams and new iOS, Mac and Windows apps.

Coworker plans multi-step jobs, coordinates Agentforce agents, flows and business actions, and returns results for review. It is described as working within existing Sharing Rules, permissions and configured access controls, with approval and audit capabilities for supported operations. A new $50 per-user, per-month option is offered for predictable budgeting.

Availability is staged: Google Workspace and Microsoft 365 connectivity, Conversation History, Skills and the per-user SKU are available now; the Teams, iOS and desktop apps and a Coworker MCP server are slated for November 2026; Daily Digest, scheduled tasks and mobile apps for Field Service, Consumer Goods Cloud and Life Sciences Cloud are expected in December 2026. The article notes pricing and features may change, and much of the piece is customer testimony and marketing framing.

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

Also told by dev.to (opens in a new tab)

Worth reading?

In brief