The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

Winter '27 release brings user history tracking and manual share retention (opens in a new tab)

Readers will learn how to enable native field history tracking on the User object, preserve manual record shares during ownership transfers, and leverage new Lightning App Builder layout controls without writing code.

Why read this

They will also discover diagnostic tools for monitoring Custom Field indexing and query frequency to reduce technical debt.

The Winter ’27 release makes field history tracking generally available for the User object, allowing administrators to monitor up to twenty fields such as profile, role, and active status directly through the Object Manager. An org-wide toggle under Sharing Settings now prevents manual record shares from being deleted when a record owner changes, which helps maintain collaboration during territory restructures.

The update expands Lightning App Builder capabilities by adding dynamic sorting for Related Lists based on formulas or lookups, conditional section headers that show or hide accordion groups, and scheduling tools for in-app prompts to prevent user fatigue. These layout enhancements align with SLDS 2 Cosmos accessibility standards and require no custom components.

Administrators can now view index status reports for Custom Fields within the Performance Metrics dashboard to troubleshoot slow SOQL queries and report timeouts. Object Manager also displays last modified dates and query frequency for each Custom Field, enabling safer and faster cleanup of unused fields before deprecation.

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

Worth reading?

Must-read

Winter ’27 release guides architects through security enforcement and agent scaling (opens in a new tab)

You will learn which authentication methods retire by early 2027 and how to migrate integrations to secure alternatives.

Why read this

The piece also outlines updated platform limits, new Agentforce orchestration patterns, and governance tools that shape long-term org architecture.

Winter ’27 Release

  • Mandatory security enforcements
  • Capacity and automation updates
  • Agentic architecture design
  • Governance and observability
The Winter ’27 release guides architects through four key architectural focus areas

The Winter ’27 guide presents the release as a set of coordinated architecture decisions across security, capacity, agentic design and governance. It recommends starting with operational risk, then judging whether new platform capabilities help existing configurations scale and fit the longer-term architecture roadmap.

The security section focuses on deadlines. Production refresh tokens expire after 30 days of inactivity starting November 4, 2026, which can break low-frequency integrations. The OAuth 2.0 device flow is restricted from November 30, 2026, and the username-password, user-agent and hybrid user-agent flows are retired on February 20, 2027. Salesforce to Salesforce retires in Spring ’27, and cross-org adapter authentication must move to Named Credentials. Connected Apps lose support by Summer ’27, so teams should move to External Client Apps, which are closed by default. The guide advises inventorying integrations, defining each trust boundary, and choosing replacements that will not face further restriction.

The capacity section covers higher limits and their risks. Synchronous Apex heap rises from 6 MB to 10 MB and asynchronous heap from 12 MB to 25 MB, so workarounds may be simplified. Elastic Async Apex Jobs (Beta) now covers batch jobs as well as future and Queueable jobs, with extra capacity capped at the lower of the licensed limit or 2 million jobs, and should be tested in non-production first. Flow improvements may make Apex built around older constraints unnecessary. Retained manual shares on ownership changes can replace recreation logic, but processes that depend on ownership changes removing access need review.

For Agentforce, Multi-Agent Orchestration is generally available and should be treated as a design-time topology decision. The API Catalog should be governed as the control point for the MCP servers and APIs agents can call, and Data 360 hierarchies should be planned as a data-architecture task. Governance tools include Security Health Review, Scale Center, MCP Server Monitoring (Beta) and Security Mesh. Each has edition, license or support-plan limits, and the guide names fallbacks such as Health Check, debug logs and existing observability tools. The guide closes by recommending an architectural decision record for each significant change.

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

Worth reading?