The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Spring '27 upgrade dates and how to find yours (opens in a new tab)

You will know where to check when your production instance and sandbox receive Spring '27, and why to test before the upgrade.

Why read this

The article gives the main release weekends and sandbox preview dates but not the release notes themselves.

  1. 9-10 Jan 2027: Sandbox upgrade weekend
  2. 10 Jan 2027: Sandbox preview period begins
  3. 16 Jan 2027: Main release weekend
  4. 6 Feb 2027: Main release weekend
  5. 20 Feb 2027: Main release weekend
Key Spring '27 dates for production and sandboxes

Salesforce Spring ’27 is approaching, and the article argues that admins need to know when their environments will be upgraded in order to prepare. It recommends testing key functions in production before the Winter ’27 release lands, even though upgrades rarely cause major problems.

The release date for each instance depends on which instance the org runs on. The main release weekends listed are January 16, February 6 and February 20, 2027. To find an exact date, the article says to open Salesforce Trust, search by instance name or domain, and select Maintenance. If the instance is unknown, Company Information in Setup shows it.

Sandboxes are the chance to test the new release against your own configuration. Sandboxes are either Preview or Non-Preview instances, and each has its own upgrade window. The Spring ’27 sandbox preview period begins on January 10, 2027, with upgrade activity over the January 9-10 weekend, though the exact date depends on the instance. A pre-release org is useful for a first look, but it does not contain your setup.

The article notes that release notes are the most anticipated item, and that they will be linked once published.

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

Worth reading?

Must-read

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?

Recommended

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?