The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Using latest for the REST API trades upgrade control for convenience (opens in a new tab)

You will learn what the latest alias for REST API versions changes, why it shifts upgrade timing onto your release testing, and why even fixed versions still depend on the current platform.

Fixed version

  • Upgrade is a planned event
  • Testing happens before the switch
  • Still runs on current platform

latest alias

  • Upgrade arrives with the release
  • No action needed to adopt it
  • Testing moves to release preview
Fixed versions and latest differ in who decides when an upgrade happens

Winter ’27 lets integrations target the REST API with the alias latest in place of an explicit version number such as v68.0. The alias removes the need to update integration versions every four months and spares you from tracking version retirements, since requests always reach the current release.

The author argues the convenience comes at a cost of control. An integration on latest picks up whatever Salesforce treats as current, so when the next version arrives, behavioral differences, new fields or updated metadata can reach your code without a planned upgrade. Salesforce recommends fixed versions for production integrations with a specific contract and latest for scripts and internal tools.

The post also points out that a fixed version does not fully protect you. Once a new version goes live, requests to older fixed versions are served by the current platform with backward compatibility applied, so the platform underneath you still changes. The author concludes that non-critical work can use latest, while critical integrations should stay on fixed versions and be regression tested every release.

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

Worth reading?

A practical framework for managing sandbox previews and testing quarterly Salesforce releases (opens in a new tab)

Readers will learn how to structure their quarterly release cycle using targeted sandbox strategies, filtered release notes, and systematic testing to prevent production issues.

Salesforce ships three releases a year, and the article argues that release readiness should become a routine habit rather than a scramble. It explains the feature lifecycle: Pilot features go to a small opted-in group, Beta features are broadly available for testing with limited support, and Generally Available features are formally part of the release. The author stresses that admins act as product managers for their org, deciding whether to adopt, wait on, or flag each feature. The recommended routine has four steps: plan and learn, get hands-on, test, and communicate.

The planning step covers tracking key release dates, completing the Release Trailhead module, and getting into a pre-release org early. During the roughly four-week sandbox preview window, the author advises keeping a mix of preview and non-preview sandboxes, with non-preview sandboxes forming the deployment path to Production. Deploying from a preview sandbox straight into non-preview Production is the path to avoid, because new metadata such as permissions may not exist there yet and deployments fail. Release Notes are too long to read in full, so the author suggests filtering them with AI tools while keeping a human check on the results, and reviewing Release Updates in Setup well before their enforcement dates.

The hands-on step means exploring features in a pre-release org or preview sandbox, involving power users early, and identifying configuration prerequisites such as page layouts and field-level security. The testing step calls for regression testing in preview sandboxes, ideally with automated tools, verifying suspected bugs in non-preview sandboxes, and opening Salesforce Support cases when problems are confirmed. The author also recommends evaluating new features for business value and compatibility with existing customizations. The final step is communication: sharing knowledge with admins and developers through sessions, preparing training and in-app guidance for users, and meeting people where they already work. The article closes by advising readers to improve one weak step each release.

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

Worth reading?

Must-read

Salesforce introduces beta Test Mode for Flow debugging and regression testing (opens in a new tab)

You will learn how to enable and use the new Test Mode beta to save, reuse, and automate Flow validation without leaving the builder.

Why read this

You will also understand upcoming capabilities like element mocking, test coverage tracking, and Agentforce powered troubleshooting.

Traditional Approach

  • Debug button only for troubleshooting
  • Testing and debugging require separate actions
  • Manual checks lack reusable configurations
  • Cluttered design canvas during validation

Test Mode Workspace

  • Dedicated view replaces Debug button
  • Merges debugging and automated testing
  • Saves runs as reusable manual test scenarios
  • Converts manual tests to regression tests with assertions
How Test Mode consolidates Flow debugging and automated testing

Salesforce has released a beta version of Test Mode, a dedicated workspace that replaces the traditional Debug button in Flow Builder. This update merges debugging and automated testing into a single interface, requiring administrators to enable the feature through Process Automation Settings before it becomes available for Record-triggered and autolaunched flows.

The new workspace allows builders to save execution runs as reusable manual test scenarios. These saved configurations preserve triggering records, input variables, and mocked outputs. Administrators can now supply static record identifiers for poorly searchable objects and populate primitive collections directly in the test panel. Once validated, these manual scenarios can be transformed into permanent regression tests by attaching expected results.

Test Mode also introduces element mocking, which simulates outputs for subflows and external actions to keep testing isolated from live endpoints. The roadmap includes Winter ’27 enhancements such as visual test coverage tracking on the canvas and Agentforce powered capabilities. These future features will synthesize transaction context to diagnose cross automation failures and automatically generate comprehensive test scenarios with isolated data silos.

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

Worth reading?