The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

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?

Using Agentforce Vibes Skills to inspect and configure your Salesforce org (opens in a new tab)

Readers will learn how to access the prebuilt Skills library in Agentforce Vibes and use them to inspect, modify, and deploy metadata changes through a plan and verify workflow.

Why read this

The guide demonstrates practical administration tasks like creating reports and Record-Triggered Flows without writing code.

The article introduces Agentforce Vibes as a browser-hosted Visual Studio Code instance configured specifically for Salesforce development and administration. Although it functions as a developer environment, the piece emphasizes its value for administrators by focusing on the Skills feature, which bundles instructions for distinct configuration actions into reusable packages.

Administrators can browse the preinstalled Skills library through the Toolkit menu after launching Vibes from Setup. The system automatically detects verbs in user prompts and maps them to the appropriate Skills, allowing the agent to execute tasks efficiently without manual selection. Users can also manually add new Skills to expand the toolkit over time.

Changes made through Vibes follow a strict plan, verify, and deploy sequence. Modifications are initially written to the virtualized local filesystem rather than directly to the connected org. Administrators review the generated change plan, approve it, and then trigger deployment using built-in commands or conversational prompts, with the agent handling connection tokens and API calls behind the scenes.

The author strongly recommends testing these workflows in trial environments such as Scratch Orgs, Developer Edition, or sandboxes. Example use cases include creating Custom Objects, adding fields, generating Permission Sets, running SOQL queries, and building Record-Triggered Flows. While early deployments may encounter errors or require multiple attempts, the structured approach provides a safe way to explore AI-assisted platform configuration.

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

Worth reading?