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?

Recommended

Working around the 2,000-row cap on report exports after step-up authentication (opens in a new tab)

You will learn why scheduled report exports now fail or stop at 2,000 rows after the Summer '26 changes, and the four practical options for fixing refreshes: manual export, narrower reports, a suitable connector, or SOQL.

  1. Export manually for a one-off pull
  2. Narrow the report with filters
  3. Use a connector built for the change
  4. Move recurring extracts to SOQL
Four ways to adapt a report export that stops at 2,000 rows

From July 1, 2026, Salesforce requires step-up authentication for exporting and printing reports, even for users already signed in with MFA. Viewing or running a report does not trigger the check. Admins can configure the policy under Session Security Level Policies with a step-up period from 1 to 120 minutes. Scheduled jobs cannot complete the check, so spreadsheet and BI tools have moved to the Analytics API, which uses OAuth and does not trigger it.

The Analytics API returns at most 2,000 rows per report run, and no permission or setting raises that cap. Other limits apply too: 500 synchronous report runs per hour, 1,200 asynchronous requests per hour, 20 Custom Field filters per run, and 100 columns per report. These limits are shared across the org, so heavy scheduled refreshes can affect other processes.

The article offers four options. For a one-off need, use a Details Only export by hand. To stay under the cap, narrow the report with filters such as My or My Team’s, fewer columns or a shorter date range, and apply tighter filters in your own pull rather than editing a shared report. For recurring pulls over 2,000 rows, choose a connector that uses the Analytics API and retrieves the full report. For large, regular extracts, use SOQL, which avoids the export and API report limits, though groupings, subtotals and formulas must be rebuilt and queries should be reviewed against the report’s logic.

The article closes by advising a review of scheduled refreshes before they compete for the shared API limits. It also promotes Xappex connectors, which handle these cases, and this promotion is the source’s own commercial interest.

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

Worth reading?

Must-read

Salesforce's new Core, Advanced and Max editions and what they mean at renewal (opens in a new tab)

You will understand how the Core, Advanced and Max editions replace Enterprise, Unlimited and Agentforce 1, what each costs per user, and what to check before a renewal under the new tiers.

Replaced editions

  • Enterprise Edition: $175
  • Unlimited Edition: $350
  • Agentforce 1: $550

New editions

  • Core: $195 (+11%)
  • Advanced: $395 (+13%)
  • Max: $550 (no change)
Old and new editions, per user per month, with the price change at renewal

Salesforce announced three new editions in early September: Core, Advanced and Max. They replace the Enterprise, Unlimited and Agentforce 1 tiers, and each bundles Agentforce, Slack, Slackbot, embedded agentic analytics, data security and a Premier Success Plan. The editions differ in how many Flex Credits they include, with Core at 500,000, Advanced at 1M and Max at 2.75M. Existing Agentforce 1 customers can move to Max at no extra cost, with up to $500 in added value.

Per user per month, Core costs $195, Advanced $395 and Max $550. Measured against the editions they replace, Core rises $20 (11%) over Enterprise, Advanced rises $45 (13%) over Unlimited, and Max matches the former Agentforce 1 price. Salesforce claims added value of 70%, 50% and 60% respectively, although the author notes it is unclear how that figure is calculated. Salesforce says legacy customers’ pricing is unchanged, which the author questions.

The author argues that bundling can justify the increase if your org already pays for Slack, Tableau and Premier Success, since a standalone Slack Business+ seat is about $180 a year and Premier Success adds roughly 30% to licence costs. Otherwise you may pay 11% more for products you do not use. The article suggests listing what you already use, matching the edition to your actual feature needs, and waiting for official pricing on agentic MCP and API calls and Industry Clouds before deciding if those will affect your choice.

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

Worth reading?

Salesforce Maps mobile app retires on 31 August 2026 (opens in a new tab)

You will learn that the standalone Salesforce Maps app and Maps Live Tracking Mobile are retired on 31 August 2026, where reps should go instead, and what a self-owned field app would involve.

  1. 31 Aug 2026: Standalone Salesforce Maps app retired
  2. 31 Aug 2026: Maps Live Tracking Mobile retired
Key dates for the retirement of the standalone Salesforce Maps app and Maps Live Tracking Mobile

Salesforce retired the standalone Salesforce Maps app for iPhone and Android on 31 August 2026. Reps now use the Maps tab inside the main Salesforce mobile app. On the same day Salesforce retired Maps Live Tracking Mobile, and live tracking did not move into the main app. Salesforce points to Check-In and Mileage Administration in its place, through third-party products named TripLog and Voze. Desktop Salesforce Maps is unchanged.

The article sets out three options for a field sales team. The first is to stay on Salesforce and move reps to the Maps tab in the mobile app, which suits reps who work in Salesforce all day. The second is to move to a dedicated per-user field tool such as Badger Maps, SPOTIO or Map My Customers, which suits teams where route optimisation and live mapping are central. The third is to own a field app, which the author suggests for teams that visit the same customers on a cycle and take orders and collect payments.

The author’s own product, Beatplan, is presented as the third option. It offers daily visit plans, GPS-verified check-ins with photos, order handling through dispatch and payment, cash and cheque collections, customer balances, and a manager dashboard on iPhone, Android and web. The article is explicit that it has no live location tracking, no route optimisation, no CRM deal pipeline and no Salesforce or Zendesk sync, and that dealer orders need a connection while visits, plans and payments work offline. It is sold once for US$2,900, with hosting from about US$25 a month.

The piece is disclosed as written by a person who works on the product and was produced with AI assistance. Its facts were checked against vendor pages in November 2026, and readers are advised to confirm current vendor documentation before acting.

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

Worth reading?

Trailblazer Community forums move to Slack, with read-only dates and access steps (opens in a new tab)

You will learn the timeline for the forum shutdown and Slack open beta, how to sign in with your TBID, and how groups, channels and synced content change.

  1. 15 Sep 2026: Move to Slack announced at Dreamforce
  2. October 2026: Group leaders attend workspace training
  3. 30 Oct 2026: Online forums become read-only
  4. November 2026: Slack community opens as open beta
  5. Early 2027: Accepted answers sync to community site
Key dates as the Trailblazer forums move to Slack, from announcement to web sync

The Trailblazer Community forums stopped accepting new posts on October 30, 2026, and the online community is moving to a Slack workspace that is now in open beta. Salesforce says the move is meant to support real-time conversation, help members find local Trailblazers and groups, and speed up answers through Slackbot and an Answers Agent. The full timeline runs from the September 15, 2026 announcement at Dreamforce through the November 2026 beta launch to early 2027, when accepted answers from Slack product channels begin syncing back to the community website.

The web forums now work as a read-only archive. Members can browse and search every historical discussion, and Salesforce says it will not remove any content. Joining is free: you sign in with your existing Trailblazer ID, so no paid Slack license or separate account is needed. If an employer blocks Slack, the article suggests using a personal device and the personal email tied to your TBID, or opening the workspace in a web browser.

Members who answered questions in the old forums may see a large unread count, because some forum data was synced into Slack with original authors attributed. The article gives a shortcut to clear it: open the workspace, press Shift + Esc to mark all messages as read, and confirm. Group pages stay on trailblazercommunitygroups.com, local groups gather in regional hubs such as #hub-northern-california, and global channels cover topics like Admins, Developers, Architects and Agentforce. Every channel is public, and members can request new ones after launch.

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

Worth reading?

AgentExchange now lets partners sell apps and services in one private offer (opens in a new tab)

You will learn what AgentExchange Commerce now allows partners to bundle into a single private offer, and what changed for multi-year terms and renewals.

Why read this

It is most useful to ISV partners and the architects who advise them.

Before

  • Managed package sold alone
  • Services bought separately
  • Separate invoices

Now

  • Package, SaaS and services in one offer
  • Mixed one-time and recurring charges
  • One consolidated invoice
A private offer can now bundle the app, services and subscriptions that used to be bought separately

Partners can now bring a Managed Package, partner-hosted SaaS products and professional services together in one private offer on AgentExchange. The offer can combine one-time service charges with recurring software or support subscriptions in a single order. Licenses for the Managed Package are provisioned automatically and kept in sync with the order, and the buyer receives one consolidated invoice.

Two further capabilities are added. Eligible partners can offer 24- or 36-month agreements with annual invoicing, though multi-year terms need account-level enablement from a Salesforce Partner Account Manager. Renewals can start from a pre-populated offer based on an existing order, with automated billing and license reconciliation at the contract anniversary and advance renewal notifications whose cadence is configured through Flow Builder.

Buyers must opt in to private offers in their Salesforce org before they can receive and accept them. The post points to release notes and a partner marketing hub for further detail.

Read the original at Salesforce Blog (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?

Must-read

Which Salesforce Certificate changes actually affect your org (opens in a new tab)

You will learn which of the three upcoming certificate changes apply to your org, how to check for mutual TLS and certificate pinning, and what to ask your integration team before the March 2027 deadlines.

  1. Check whether the org uses inbound mTLS
  2. Review which systems connect to Salesforce
  3. Plan renewals as certificate lifespans shorten
  4. Confirm connected systems trust Mozilla's roots
Three certificate changes, each checked in turn to see whether an org is affected

An “ACTION REQUIRED” email from Salesforce on October 29, 2026, warned of three certificate changes that could cause security problems or service disruption. The article argues that many orgs need only a few checks. Admins should first ask three questions: whether mutual TLS (mTLS) is in use, which is checked under Certificate and Key Management (the Mutual Authentication Certificates section is hidden until Salesforce Support enables it); whether external systems such as middleware or on-premises servers connect to Salesforce; and whether their team renews public certificates by hand.

The first change affects only orgs using mTLS. Under Chrome Root Program Policy v1.8, a certificate can no longer serve both server and client authentication, so existing dual-use certificates may not be renewable after March 2027. The fix is a dedicated client certificate from a supported public authority, such as DigiCert, SSL.com, Sectigo or GlobalSign. Salesforce does not currently accept private certificate authorities for inbound mTLS. The integration owner handles the replacement, while the admin confirms who that is and that a plan exists.

The second change shortens the maximum lifespan of publicly trusted TLS certificates: 398 days before March 2026, 200 days from then, 100 days from March 15, 2027, and 47 days from March 2029. Salesforce rotates its own certificates at least 45 days before expiry, so the risk lies with systems that pin a specific certificate, which Salesforce strongly advises against. Self-signed certificates are not subject to the new limits but still expire after a year. Admins should decide who owns manual renewals, assign the Expired Certificate Notification permission, and consider automation through the Metadata API Certificate type.

The third change concerns root certificates and trust stores. Salesforce recommends that connecting systems trust all roots on Mozilla’s Server Authentication list, since it may switch roots. Older Java or SAP integrations, particularly those more than ten years old running JDK 8 or earlier, may need extra files to support its cryptographic algorithms. Self-signed and custom CA-signed certificates are exempt, and MuleSoft users should follow separate guidance. The admin’s role is to pass three questions to IT about trust stores, pinning and Java versions, and then confirm that each check has an owner. Salesforce is also running webinars for engineering and security teams on November 4 and 5, 2026.

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

Worth reading?

Salesforce's Braze acquisition raises questions for Marketing Cloud teams (opens in a new tab)

You will learn what the announced Braze acquisition means for Marketing Cloud Engagement and Marketing Cloud Next, and which skills and architectural decisions it may affect.

Why read this

The article also makes clear that no combined roadmap exists yet.

Marketing Cloud Engagement

  • Relies on Journey Builder
  • Established automation offering

Marketing Cloud Next

  • Emphasises Data 360 and AI
  • Automation through Flow Builder
The two Marketing Cloud platforms the Braze deal must fit alongside, as the article describes them

Salesforce has agreed to acquire Braze, an engagement platform that reacts to customer behaviour in real time across email, push, in-app messaging, SMS and WhatsApp, in a deal valued at around $5.66B. Salesforce expects to close during fiscal 2028, subject to shareholder and regulatory approval. Braze says in an SEC filing that its integration with Data 360, Customer 360 and Agentforce remains a possibility and that no decisions have been made.

The article notes that Salesforce has not published a combined roadmap showing how Braze’s capabilities will overlap with Marketing Cloud Engagement, which relies on Journey Builder, and Marketing Cloud Next, which centres on Data 360, AI and Flow. Salesforce’s president of applications and marketing suggested Braze would extend Marketing Cloud Next with real-time, mobile-first engagement rather than replace Marketing Cloud.

For practitioners, the piece argues that the greatest risk is over-specialising in one orchestration tool, and that event tracking, identity, API integration and data architecture skills will grow in value. It also expects consulting work around integration, migration and platform rationalisation, while warning that pricing, packaging and third-party integration openness remain unknown.

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

Worth reading?

Must-read

B2C Commerce October 2026 release adds events GA and self-service unpairing (opens in a new tab)

You will learn what the October 2026 B2C Commerce release changes for integrations, environment setup and licensing, including the Event Framework going generally available and the removal of the Data 360 license requirement for the trusted connection.

Why read this

You will also see which agentic and developer tooling features arrived with it.

Before October 2026

  • Data 360 license needed
  • Admin support ticket to reset pairing
  • Sandbox type limits

October 2026

  • No Data 360 license needed
  • Self-service unpairing
  • Any Salesforce sandbox type
Trusted connection to a Salesforce org no longer requires a Data 360 license

The October 2026 release for B2C Commerce focuses on speed, automation and unified commerce. It adds Universal Commerce Protocol integration, which lets merchants turn on UCP-powered checkout on Google so shoppers can buy directly from surfaces such as the Gemini app and Google Search while the merchant stays the merchant of record. Agentic features built into Business Manager include conversational catalog search, where the Merchandising Agent builds filter logic from plain English, and AI-suggested category assignments with a dashboard insight for uncategorized products.

For integration work, the most relevant changes are the Event Framework going generally available, with process-level and granular replication events, shopper registered and order placed events routed to HTTP webhook connectors, and support for custom events declared in a cartridge. The trusted connection to a Salesforce org no longer needs a Data 360 license, admins get self-service unpairing after a sandbox refresh, and developers can pair non-production instances with any Salesforce sandbox type. Profile updates now sync to connected Person Accounts in near real time, and partial POS catalog syncs let stores receive only modified pricing and product data.

On the tooling side, the Agentic Developer Toolkit gains more built-in knowledge, new operations runbooks that always ask for approval before making changes, and SCAPI Code Mode, which lets an AI assistant look up Salesforce Commerce API operations and run small scripts against a live instance. Direct SCAPI security controls for rate limits, WAF rules and cache purges are also available in Business Manager or by API.

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

Worth reading?

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?

Must-read

Salesforce moves Trailblazer Community forums to Slack in November 2026 (opens in a new tab)

You will learn the exact timeline for the Trailblazer Community migration to Slack, how historical forum data will be preserved and indexed, and practical steps to prepare your account before the switch.

Existing Forums

  • Asynchronous replies taking time
  • Full forum threads remaining indexed
  • Structured questions and answers

New Slack Community

  • Real-time conversations and quicker interactions
  • Summarized accepted answers syncing back
  • Conversational discussions in channels
Comparison of the current Trailblazer Community forums versus the upcoming Slack workspace

Salesforce has announced that the online Trailblazer Community forums are moving to Slack, with the new experience becoming generally available in November 2026. The forums become read-only on October 30, 2026, so members can still browse and search existing posts but cannot publish new ones, and there is a gap before the Slack community opens during which new questions cannot be asked. The move is presented as a response to member requests for real-time conversation, easier peer connection and quicker access to trusted answers. The Slack version will be built around channels chosen during onboarding based on location, role, industry and products, a Slackbot to help find channels and Trailhead resources, and an Answers Agent AI that draws on trusted community knowledge. Joining is free, requires no paid Slack license, and uses an existing Trailblazer ID.

The historical forum archive is to remain accessible and searchable after October 30, so members need not export their saved threads. New answers in Slack will not be immediately visible to web searches. Accepted answers from product channels are to be anonymized, summarized and synced back to the website starting in early 2027. The author flags several gaps: answers posted before that rollout may not be indexed, only accepted product-channel answers will sync, full conversations will not be preserved, and contributors will receive less public credit. Local and specialist Trailblazer groups will not get their own Slack spaces by default. Instead, they will sit within regional hubs and global channels, group pages will stay on the separate group site, and new public channel requests will be reviewed by Salesforce.

The article gives practical advice for preparing: check which email address is linked to your Trailblazer ID and consider using a personal address, find out whether your employer blocks Slack and, if so, plan to use a personal device, and learn the basics via the Get Started in Slack trail on Trailhead. The author is cautious about whether the AI agent could reduce human participation and reputation-building, and notes that the FAQ leaves open questions such as whether the agent will use the forum archive, how reputation carries over, and what happens to the Forum Ambassador program. The author concludes that the success of the move depends on balancing Slack’s immediacy with the lasting, searchable value of forums, and encourages members to post outstanding questions before October 30 and to keep helping others once the new community launches.

Read the original at Salesforce Ben (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?

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?

B2C Commerce release 26.9 introduces edge credential detection and SFRA password warnings (opens in a new tab)

Readers will learn how to configure Cloudflare firewall and rate limiting rules in B2C Commerce to block leaked credentials, and how to implement server-side header checks in SFRA to prompt users to rotate breached passwords.

The September 2026 update to B2C Commerce adds built-in credential stuffing protection through its eCDN layer without requiring additional entitlements. Four new detection fields evaluate login attempts against known breach data, allowing administrators to create custom firewall and rate limiting rules at the network edge.

The article provides exact rule syntax examples to throttle malicious traffic while preserving verified search crawlers. It explains how to use managed challenges for password leaks and emphasizes separating counting expressions from rule expressions to avoid penalizing legitimate bot activity.

For storefront implementations, the piece details how to read a server-side request header added by Cloudflare after a successful login. A working SFRA code example demonstrates how to map header values to user-facing warning messages and direct shoppers to a password reset flow, deliberately avoiding failed login responses to prevent information leakage to attackers.

Finally, the author outlines monitoring strategies using Security Analytics in Business Manager and eCDN Logpush exports, recommending these detections as a baseline before layering in broader bot mitigation controls.

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

Worth reading?

Salesforce Winter '27 brings Flow testing, bulk screen actions, and higher heap limits (opens in a new tab)

Readers will learn how to implement the new Flow Test Mode, process multiple records via List Views, and adjust to increased Apex heap limits and updated REST API versioning without manual tracking.

The release introduces Test Mode for Flow Builder, enabling repeatable testing with assertions and mock outputs for external callouts. Screen Flows launched from List Views or Related Lists can now process multiple selected records by accepting a lowercase ids collection variable. Reactive Formulas allow Conditional Visibility to evaluate same-screen inputs instantly, while new save-time validation catches missing Required Fields and character limit breaches before runtime.

Logic handling gains Split by Field Value and Split by Date elements, which create automatic branches but do not fully replace Decision elements. Navigation improves through an Unused Resources filter, Element Grouping, and an Edit History panel. Security receives a User Context option that enforces running user permissions, and an org-wide toggle preserves Manual Shares when record ownership changes.

Synchronous Apex transactions now support a 10 megabyte heap limit, while asynchronous transactions reach 25 megabytes, with a transition setting available to manage the shift. List View inline editing expands to include off-page layout fields and mixed Record Types. Integrations may use latest for REST API versioning, and Field History Tracking becomes generally available for the User object.

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

Also told by Salesforce Ben on YouTube (opens in a new tab)

Worth reading?

Winter 27 release brings Headless Toolkit, Multi Framework support, and Data SDK extensions (opens in a new tab)

Readers will learn how to build cross-framework applications on the platform using the new Headless Toolkit and understand how to extend the Data SDK with custom logic.

The Winter ’27 release, whose final rollout is set for October 9, 2026, centers on the Headless Toolkit. Salesforce capabilities are exposed as APIs, Model Context Protocol (MCP) tools and CLI commands that any authenticated caller can use. The Salesforce Development plugin for Claude Code adds Salesforce-specific skills, org context and recommendations for specialized plugins, and its skills also work with other coding agents. Multi-Framework apps now support Angular alongside React, with new templates, 2GP packaging and a Data SDK that can package custom logic as typed extensions. Beta microfrontends let an app run inside a Lightning page, with data passed down from the host component and events sent back up.

The Headless Experience Layer (Beta) lets a developer define a widget once and render it in Agentforce, Claude and Slackbot, linked through Apex, Lightning type and widget metadata. MCP now works in both directions, so Agentforce agents can be exposed as tools on custom MCP servers and AgentExchange MCP tools can be added to agents. The Marketing Cloud Engagement MCP server gains 40 tools. The CLI stops printing access tokens and secrets, with the temporary workaround ending October 28, 2026, and it adds async Apex templates and Scratch Org settings. API version 68.0 requires the Use Any API Auth permission for SOAP login from December 1, 2026, retires API versions 31.0 through 40.0, and adds a latest alias for REST URIs.

In Lightning Web Components, template expressions and LWC:external reach general availability, and state managers gain a refresh() method. Apex heap limits rise to 10 MB for synchronous and 25 MB for asynchronous transactions, and integration tests, FORMULA() and the Apex Symbol API are in preview or beta. Agentforce gains new Agent Script language features, file uploads in conversations, and generally available Multi-Agent Orchestration, along with simplified agent metadata types. Data 360 adds a context precision metric for retrievers and Python code extensions for zero-copy data. Web Console, a browser-based IDE, is generally available and needs no installation.

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

Worth reading?

Winter 27 release adds inline editing, sharing controls, email security, and report previews (opens in a new tab)

You will learn how to configure new Winter 27 capabilities that improve List View editing, preserve manual sharing during record transfers, streamline email domain verification, and enhance Lightning Reports and Dashboards.

The Salesforce Admins Blog has published a launchpad for the Winter ’27 release, which ships three times a year and is 600-plus pages of notes. The author urges admins to focus on the features that matter to their own org rather than reading everything. The post also explains that features move through pilot, beta and generally available (GA) stages, with beta features carrying limited support and best tested in a sandbox.

On the core platform, two new User Interface Settings let users inline-edit any field they can access, even if it is not on the page layout, and let List Views mix record types. Both are off by default. User field history tracking reaches GA, covering up to 20 fields on the User object and retaining history in the UI for 18 months. The standard Follow button can also be shown in the Dynamic Highlights Panel. For sharing, a setting now keeps manual shares when a record’s owner changes, and a forward-looking note says custom row causes for standard objects are targeted for October 10 through the Metadata API.

The security and email section covers a consolidated User Email Domains page in Setup, which shows verified and unverified address counts per domain. Admins can copy verified authorized domains from production into a new sandbox with one click, and set verification to Always, For Updated Addresses Only, or Never for each domain. Secondary sender addresses let sensitive emails route through Salesforce’s own Mail Transfer Agent. Experience Cloud Trusted URLs can now take individual Chrome extension IDs, with wildcards unsupported.

The Reports, Dashboards and Flow sections are the longest. Beta features include record previews in Lightning Reports, a Common Rows Only option for joined reports, and Lightning Reports and Dashboards embedded in LWR Experience Cloud sites. Flow Builder adds version Edit History with restore, element grouping, an Unused resource filter, Agent Action details in the canvas, and a User Context run option for flows using API version 68.0 or later. It also brings auto-generated element labels, persistent end elements, and save-time warnings for missing required fields and field length. Flows can now retry on record lock errors, Screen Flows can run as mass actions from List Views and Related Lists, and a native Time component is available. Beta Test Mode and mock outputs for Action and Subflow elements round out the testing tools.

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

Worth reading?

Salesforce announces general availability of Web Console as a modern browser-based IDE (opens in a new tab)

Readers will learn how to access and use the new Web Console for inline Apex and Lightning Web Component editing, debugging, and query execution directly inside their org.

Why read this

The article explains the production guardrails, Setup steps, and how it differs from the legacy Developer Console and Agentforce Vibes IDE.

Salesforce has released Web Console as a generally available browser-based integrated development environment. Built on VS Code for the Web and the existing Salesforce extensions, it serves as a modern replacement for the legacy Developer Console while maintaining platform safety standards.

The tool supports core development tasks including inline editing of Apex classes and triggers, viewing and modifying Lightning Web Component files, running anonymous Apex scripts, and executing SOQL queries with optional Performance Plans. Developers can also run test suites, manage Trace Flags for debugging, and navigate the entire metadata tree using the Org Browser.

Access controls differ by environment, allowing read-only inspection in production orgs while permitting direct saves in sandboxes. Administrators can enable the feature through the Setup menu, where it is turned on by default. The announcement clarifies that this lightweight single-org editor targets quick troubleshooting and routine edits, distinct from the heavier virtual machine-backed Agentforce Vibes IDE.

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

Worth reading?