Today6 stories · 1 brief

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

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

Must-readApex and platform

How a local Apex runtime speeds up testing without replacing your org (opens in a new tab)

You will learn how a local runtime executes Apex and Flow metadata against an embedded database while enforcing governor limits and order of execution.

Why read this

The article explains how this approach accelerates the edit-test cycle and fits into your standard deployment workflow.

Local Apex runtime

  • Apex interpreter
  • Local database for SOQL and DML
  • Rule engine for limits and execution
The local Apex runtime is built from three core components

The article, written by the maker of renmy runtime (formerly Nimbus, renamed in October 2026), introduces a local Apex runtime: a program that executes Apex, SOQL and DML on a developer’s own machine without a Salesforce org. It argues that Salesforce developers work in a slow loop, where every edit is deployed to an org and tested there, while developers in Java, JavaScript and Go run tests locally in about a second. The author attributes this gap to Apex being multi-tenant and tied to the platform’s data model and order of execution. Cited costs include round trips to the org, CI that needs org credentials, outages that halt testing, and AI coding agents that cannot iterate quickly. A local runtime has three parts: an Apex interpreter, an embedded PostgreSQL database for real queries and DML, and the platform’s rules, including enforced governor limits, triggers and Flows in order of execution, and per-test rollback. A sample test runs in tens of milliseconds, and the article says the runtime is not a mock, not a Scratch Org and not a transpiler.

The article is clear that a local runtime does not replace the org. Lightning pages, user-facing Screen Flows, permission checks, real integrations and the deploy itself with Salesforce’s metadata validation still happen in the org. The author compares this to a Java team’s staging environment, which stays for integration and final checks but is not the only place code runs. The renmy deploy is described as running local test and coverage gates first, then a check-only validation in the target org, then the deploy. The tool also offers coverage reporting, mutation testing, a debugger in VS Code and JetBrains, an MCP server for AI coding tools, and an IDE plugin. A published benchmark reports that 837 tests from four open-source suites ran in about 2.4 seconds locally versus about 1 minute 46 seconds in an org, with all tests passing in both.

Installation is a single binary for macOS, Linux and Windows, with no JVM, Docker or org required, and the commands are renmy test “” from the project root, plus options for single classes, coverage and a browser dev UI. The free tier covers individual developers, while Pro and Team tiers are free during the public beta and listed at $19 per month and $49 per developer per month. The article links to a parity record, which it describes as not a claim of 100 percent accuracy, and to GitHub for issues and releases.

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

Worth reading?

Must-readIntegration

Migrating HubSpot to Salesforce: External IDs, upsert, and load order (opens in a new tab)

Readers will learn how to structure a reliable HubSpot to Salesforce data migration using External IDs, proper load ordering, and Bulk API, including strategies for handling hierarchies, deltas, and validation.

  1. Cleanse data and map picklists
  2. Dry run in sandbox with disabled automations
  3. Load records following dependency order
  4. Enable read only mode and run delta load
  5. Verify record counts and relationship integrity
Phased migration process from HubSpot to Salesforce

The article addresses the complexity of moving historical records and relationships from HubSpot to Salesforce, emphasizing that simple export import fails due to differing data models. It establishes the External ID field as the foundation for tracking records, enabling idempotent upserts, and linking related objects without relying on Salesforce generated identifiers.

It outlines a strict dependency sequence for loading records, starting with Users and Accounts before moving to Contacts, Opportunities, and Activities. Special attention is given to Account hierarchies, recommending a two pass approach to avoid parent child reference errors. The piece includes a Python example using the Bulk API to demonstrate upserting an Opportunity by matching its Account via an External ID rather than a native Salesforce identifier.

Before migration, the author stresses data cleansing, deduplication rules, and mapping picklist values like pipeline stages. A sandbox dry run is recommended to generate repeatable error reports and to temporarily disable automations such as Flow and Apex triggers that could trigger unwanted side effects during bulk loads.

The final phase uses a delta load strategy to capture changes made after the initial bulk transfer, requiring source system read only mode and timestamp tracking. Post migration validation involves comparing record counts, verifying relationship integrity, reconciling financial totals, and spot checking field values to ensure data accuracy before full team adoption.

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

Worth reading?

RecommendedCareer and certifications

Agentforce Specialist exam outline updates and a four-week study plan (opens in a new tab)

Readers will learn the updated Spring 2026 Agentforce Specialist exam structure, key topic weights, and a hands-on preparation plan using Developer Edition orgs and core platform tools.

The Spring 2026 Agentforce Specialist exam has been restructured, removing separate Sales Cloud and Service Cloud sections while adding Agent Script, hybrid reasoning, Testing Center workflows, governance, and multi agent orchestration. The assessment consists of 60 scored multiple choice questions plus five unscored ones, lasts 105 minutes, requires a 72 percent passing score, and costs 200 dollars to register.

A four week preparation strategy emphasizes practical application over rote memorization. Week one focuses on prompt engineering and the Trust Layer using field generation and flex templates grounded in record data. Week two covers Data Cloud fundamentals, guiding readers to build a file based Data Library and connect policy documents to test retrieval behavior. Week three shifts to agent creation, requiring the construction of an agent with Flow backed actions and deterministic decision filters. The final week covers the Testing Center, deployment procedures, analytics, and governance monitoring.

Common study mistakes include relying on outdated outlines, underweighting the AI Agents section, treating Data Cloud as optional, and ignoring annual maintenance requirements that expire the certification. The article concludes that demonstrating configured solutions and tested agents during technical interviews carries more weight than the certification badge alone.

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

Worth reading?

Agentforce and AI

Connecting Data Cloud to Agentforce Studio to build an agentic RAG pipeline (opens in a new tab)

Readers will learn how to configure a custom retriever in Agentforce Studio, create a Flex Prompt Template in Prompt Builder, and deploy a subagent that grounds responses in live Data Cloud vector data.

The article explains how to configure a custom retriever in Agentforce Studio to fetch vectorized chunks from a Data Cloud data model object. It details setting result limits, mapping target fields, and activating the retriever so it can be referenced elsewhere.

Next, it walks through creating a Flex Prompt Template in Prompt Builder by modifying a standard knowledge template. The author shows how to add the retriever as an action, bind the query parameter, and write strict instructions that force verbatim source extraction and handle missing data gracefully.

Finally, the piece covers assembling an Agentforce Service Agent, keeping only essential routing subagents, and linking the custom Prompt Template as an action. The author validates the workflow by testing destination queries and confirming the agent returns accurate, grounded answers sourced directly from the live Data Cloud index.

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

Worth reading?

Data Cloud

Set up Data Cloud web crawlers to ingest and vectorize external pages for AI agents (opens in a new tab)

Readers will learn how to configure a Data Cloud Web Content Connector, filter target elements with CSS selectors, and generate searchable vector chunks from live websites.

Why read this

The guide also shows how to verify the ingested data using Data Explorer and SOQL.

The article introduces Retrieval-Augmented Generation and explains why keeping AI agents grounded in real-time data matters. It outlines the prerequisites of enabling Einstein, Agentforce, and Data Cloud in a development org.

It details the configuration of a Web Content Connector in Data Cloud Setup. The steps explain how to set crawl depth to zero to avoid following irrelevant links and how to use browser developer tools to copy CSS selectors for targeting specific page elements.

The guide describes creating a Data Lake Object and its corresponding Data Model Object. It notes that semantic search must be enabled while skipping image embedding and knowledge harmonization for this text-only use case. It concludes by showing how to validate the chunked output through Data Explorer and standard SOQL queries against the unstructured data model object suffix.

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

Worth reading?

Architecture

Architecting HCP and HCO 360 data models and integrations in Life Sciences Cloud (opens in a new tab)

Readers will learn how to design the reference architecture, data model, and integration sequence required to implement HCP and HCO 360 profiles in Life Sciences Cloud.

Why read this

They will also understand best practices for managing affiliations, resolving duplicates, and aligning field territories.

This guide explains how to design and implement HCP 360 (healthcare professionals) and HCO 360 (healthcare organizations) in Salesforce Life Sciences Cloud. It starts from the problem that a single doctor can appear across several hospitals and in multiple systems such as CRM, marketing platforms, and external healthcare databases, leaving sales reps with inconsistent or incorrect information. HCP 360 gives a connected view of an individual professional’s details, workplaces, contact data, territory, and interaction history, while HCO 360 gives account managers a view of an organization’s location, departments, affiliated professionals, parent group, and engagement history.

The article recommends a reference architecture before any configuration begins. External data providers supply identifiers, specialties and addresses; master data management decides how records are matched and which system owns each attribute; Life Sciences Cloud runs customer engagement; and Salesforce Data 360 can unify sources for analytics and segmentation without automatically replacing the master data system. The data model should reuse standard Life Sciences Cloud entities such as provider, provider organization, affiliation, identifier, specialty, and territory before any Custom Objects are added. Affiliations must support multiple roles, dates and history, and HCO hierarchies must be kept distinct from professional affiliations.

For duplicates, the guide sets out a five-step process: standardize data, match on reliable identifiers, compare supporting attributes, send uncertain matches to a data steward, and keep source-system references. It warns against merging on name alone. For integration, it recommends loading HCOs first, then HCPs, then affiliations, then territory alignment, and finally validating counts, duplicates and relationships, using bulk processing and retry and error logging. The article also covers territory design beyond geography, keeping consent management separate from record-level security, and building HCP and HCO 360 pages on standard features first. Common mistakes include unnecessary Custom Objects, unclear data ownership, copying too much external data, overwriting affiliation history, and building interfaces before data quality is fixed. A pre-go-live checklist and an FAQ close the piece.

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

Worth reading?

In brief