Today5 stories · 1 brief

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

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

Must-readReleases

Spring '27 release updates to Test before enforcement, part two (opens in a new tab)

You will know which Spring '27 release updates in this part affect your org, how to find the impacted Visualforce pages, Apex, Flows and permissions, and how to test each one in a sandbox before it is enforced.

  1. Review release notes and affected features
  2. Test each update in a sandbox
  3. Deploy the changes to Production
  4. Schedule the change outside working hours
A safe order for preparing Spring '27 release updates

This second part of Tom Bassett’s guide for the Salesforce Spring ’27 Release covers the remaining release updates due to be enforced around the January 2027 release, and explains how to test each one before it reaches production. Release updates change how existing features behave, so the guide recommends checking your org early, either with no-code tools or with pro-code methods such as SFDX, Workbench or Salesforce Inspector Reloaded. It also warns that Salesforce may delay, change or cancel updates, so the Winter ’27 release notes should be checked, and that managed packages should be confirmed with their providers.

The first update makes Visualforce pages that render as PDFs use an accessible rendering engine, currently in beta. Admins should find pages set to renderAs=“pdf”, use the Test Run in a sandbox, and confirm that the pages still display correctly with screen readers. Sharing recalculation is the next change, moving some work to asynchronous processing. It is most likely to affect orgs with large data volumes and high ownership skew, or with Apex and Flows that change group membership or roles or rely on immediately updated share records. This update has no Test Run, so the guide advises enabling the “Test asynchronous sharing recalculation in Apex tests” setting in a sandbox to simulate it.

Several smaller changes follow. The View Setup Audit Trail permission will be granted automatically to anyone who has View Setup and Configuration, so teams should review who holds the older permission and remove it where it is not needed. Personal information fields will be masked separately for Guest Users, and once enabled this cannot be turned off, so guest access should be audited and tested in a sandbox first. Manual assignment of commerce application usage types will become possible, which means automation that assumes checkout is the only source needs review, and that change also cannot be reversed.

Platform Event triggers will roll back their whole transaction on unhandled exceptions, so triggers relying on partly saved records need regression testing. Finally, the OAuth User-Agent and Hybrid User-Agent flows retire on February 20, 2027. Login History, which holds six months of data, can reveal which integrations use them, and those should move to the Web Server flow or Hybrid Web Server flow with PKCE. The guide ends by urging early preparation and reminding readers to read the first part.

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

Worth reading?

RecommendedReleases

Spring '27 release updates that need testing before enforcement, part one (opens in a new tab)

You will learn which of the first Spring '27 release updates, due before the release, affect your org, how to find the affected Connected Apps, SOAP logins and email settings, and how to test and deploy each change safely.

  1. Find impacted features in a sandbox
  2. Test each release update with Test Run
  3. Re-test impacted connections and users
  4. Deploy to Production outside working hours
  5. Check results and keep a rollback plan
The recommended sequence for preparing Spring '27 release updates before enforcement

Tom Bassett’s guide is the first of two parts covering the 16 release updates due to be enforced before, during or just after Salesforce’s Spring ’27 release in January 2027. Salesforce will enforce some updates before the release window, which the author notes is unusual and tied to security. The guide advises testing in a sandbox before deploying to production, ideally outside working hours, with a communication plan and a rollback plan. It also suggests developers use tools such as SFDX, Workbench or Salesforce Inspector Reloaded to find dependencies, and that users check the Winter ’27 release notes, since Salesforce may delay, change or cancel updates. Installed managed packages should be confirmed with their providers.

This part covers the first group of updates. The OAuth 2.0 Device Flow restriction, enforced on November 30, 2026, affects Connected Apps, packaged External Client Apps and Local External Client Apps without a Callback URL. Teams should review Login History for OAuth device logins, which is only kept for six months, migrate affected Connected Apps to External Client Apps, and confirm Local External Client Apps have a Callback URL. The SOAP Login change, effective December 1, 2026, gates access behind the Use Any API Auth permission, so affected users and integrations need a Permission Set granting it, verified through Login History. The email verification exception is being retired: existing Email Domain Allowlists will stop working, so orgs should move to Authorized Email Domains, especially if DKIM verification is turned on, to avoid users being unable to send email. The accessibility change for To Do Lists and Lightning Dual Listboxes, due January 2027, affects users browsing at more than 200% zoom, so custom and Visualforce pages should be tested at that level.

Other updates also due in January 2027 need attention. Aura action responses will no longer return non-public system fields, so Lightning components and their Apex classes must be reviewed for references to undocumented fields, and the author found standard objects were affected too. Salesforce Connect Cross-Org legacy OAuth and password authentication is being removed, so External Data Sources should be migrated to Named Credentials and re-authenticated. Salesforce to Salesforce is being retired, so organizations should check whether it is enabled, export any backup records, and move to an alternative such as Partner Cloud, Data Cloud One, MuleSoft or a third-party tool.

The guide closes with two adjustments Salesforce has made to earlier updates. The OAuth 2.0 Username-Password Flow retirement for Connected Apps is now due on February 20, 2027, and the update to instanced URLs in API traffic is now due in Spring ’27. The author points readers to part two for the remaining updates.

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

Worth reading?

RecommendedDevOps

Finding hidden duplicate accounts after a Salesforce Data migration (opens in a new tab)

You will learn how to normalise legacy keys, count duplicates in a spreadsheet and in SOQL, separate true duplicates from key collisions, and repoint child records before deleting a duplicate Account.

  1. Normalise the legacy key
  2. Count raw and normalised keys
  3. Classify each duplicate group
  4. Repoint child records
  5. Delete the duplicate
The duplicate clean-up sequence for migrated Accounts

Matching record counts after a migration can hide duplicates. Re-run loads, insert calls used where an upsert on an External ID was needed, and keys that differ only by case, spaces or leading zeros all leave duplicates behind. Salesforce duplicate and matching rules do not examine a legacy key unless a rule is built for it.

The article walks through normalising the key with spreadsheet formulas, counting raw and normalised keys, and classifying each group as unique, exact duplicate, hidden duplicate or key collision. A SOQL GROUP BY query with HAVING clause provides the same check inside the org, though it catches case differences only, not leading zeros or trailing spaces.

Before deleting anything, the author chooses a survivor, usually the Account with the most Contacts, and repoints Contacts, Opportunities and Cases to it with Data Loader or the Account merge operation. The checklist ends with marking the External ID field Unique so the next load cannot insert the same key twice.

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

Worth reading?

Agentforce and AI

Koa Decisions brings fast single-step decision models to Salesforce builders (opens in a new tab)

You will learn what a decision model is, how it differs from a general-purpose LLM for choosing among options, and how Koa Decisions is positioned to reach flows, Apex and Prompt Templates.

Why read this

The article also points to a free Trailhead demo for testing it.

Decision model

  • Reads the whole request at once
  • Returns one choice in one step
  • About 26 ms in Agentforce routing

General-purpose LLM

  • Writes its answer token by token
  • Generates text before the choice
  • About 1.4 s in Agentforce routing
A decision model returns one choice directly, while an LLM writes its answer token by token

Salesforce has introduced Koa Decisions, the next version of its HyperClassifier model. It reads a request and a list of categories the user defines, then returns a decision in a single step, in milliseconds. It was built by applying training techniques to Google’s open-weight Gemma model, and it adds multimodal support for images and audio. Salesforce plans to extend it beyond Agentforce routing into flows, Apex and Prompt Templates, plus an API for developers. It joins a separate reasoning model built with NVIDIA in the Koa family.

The article argues that much of an agent’s work is choosing an option, a yes or no, or a score rather than generating text. A decision model returns that choice directly, while an LLM writes its answer one token at a time. In Agentforce routing measurements, the decision model took roughly 26 milliseconds against about 1.4 seconds for a general-purpose LLM. New categories can be added without retraining, which the article contrasts with building a custom predictive model over months.

Readers can test the model through the Koa Decisions demo on a free Trailhead account by changing the options and request text. The article also notes pricing and availability are subject to change and vary by region.

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

Worth reading?

Agentforce and AI

Tableau Data Apps bring governed agentic analytics to vibe-coded apps (opens in a new tab)

You will learn what a Tableau Data App is, where it can be built and published, and how it inherits Tableau's security, semantics and refresh model.

Why read this

The piece is a product overview in beta, so the detail on setup is thin.

  1. Connect your agent via MCP
  2. Prompt your intent
  3. Preview, iterate and verify
  4. Publish and share
The four steps to get a Tableau Data App from prompt to shared link

Tableau Data Apps, now in beta, are custom interactive analytical web apps hosted and powered by the Tableau platform. They separate the visual front end from the query engine, so builders can use AI agents to produce apps quickly while the apps still draw on Tableau’s semantics, connectivity and governance. The article argues that visualization was never the hard part, and that without an analytics platform agent-built apps risk guessing at business definitions, running slow and costly query loops, and leaking credentials or data.

Apps can be built in Tableau Studio or with any third-party agent connected through the Tableau MCP server or Tableau Next MCP server. Apps built in Tableau Studio publish to Tableau Cloud or Server, while apps built with third-party agents can publish to Tableau Cloud, Server or Tableau Next. Inside Tableau Cloud and Server, apps sit in workbooks and query Published or Embedded Data Sources, and in Tableau Next they sit in workspaces and use Tableau Semantics.

Data freshness comes from live connections or scheduled extract refreshes, and federated queries let apps reach heterogeneous sources without copying data. Database credentials stay in Tableau, and object-level and row-level security apply to every user. The getting-started steps are to connect an agent, prompt the intent, preview and verify the logic, then publish and share.

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

Worth reading?

In brief