Key takeaways
- Summer ’26 rolled out to sandboxes from May and to production orgs across May and June 2026, depending on instance.
- Flow gained new operators for Date fields, such as “Is Today” and “Is Tomorrow”, which simplify common conditions.
- Object Manager adds a field access summary that helps admins see who can access fields.
- As every release, review Release Updates, retirements and security changes before your production upgrade.
Salesforce’s Summer ’26 release followed the usual pattern: a sandbox preview in May, then production upgrades on scheduled weekends by instance. Here are notable changes and, more importantly, a practical checklist for reviewing this or any release.
Flow: date operators
Flow conditions gained new operators for Date fields, such as “Is Today” and “Is Tomorrow”. Conditions that previously needed formulas comparing against the current date become simpler and easier to read. Note that these operators apply to Date fields; DateTime fields need separate handling.
Flow: comparing versions
Building on recent releases, flow version comparison continues to improve, making it easier to see what changed between versions during reviews and troubleshooting.
Security and governance: field access visibility
A field access summary in Object Manager helps admins understand which users, permission sets and profiles grant access to a field. This supports least-privilege reviews and audit questions such as “who can see this sensitive field?”
A Summer ’26 review checklist
- Release Updates: review items approaching enforcement and test them in a sandbox.
- Retirements: check the release notes for features or legacy behaviors being retired and confirm whether you use them.
- Security changes: review authentication, session and code security changes noted in the release.
- Regression tests: run key business processes, flows, integrations and reports in a preview sandbox.
- Quick wins: adopt the new date operators in new and updated flows; use field access summaries in your next access review.
Why a consistent routine matters
Release content changes every time, but the routine does not: read, test, adopt, communicate. Teams that follow it rarely have release surprises and steadily benefit from new features. Keeping a short release log of what was tested and adopted also helps auditors and new admins.
This summary covers a selection of changes reported for Summer ’26. Feature availability depends on edition and configuration; the official Summer ’26 release notes are the authoritative source.
Our administration and support team runs release reviews for clients every season.
Using the new date operators
Conditions such as “appointment date is today” or “renewal date is tomorrow” are common in scheduled and record-triggered flows. Previously they often needed formula resources comparing against TODAY(). The new operators make such conditions readable at a glance, which helps future admins understand the flow. When updating older flows, replace formula-based checks gradually and test that time zones and DateTime fields behave as expected.
Building a release log
| Date | Release item | Action taken | Owner |
|---|---|---|---|
| Preview | Release update reviewed | Tested in sandbox, activated | Admin |
| Preview | Critical flows regression tested | Passed | Admin and key users |
| After upgrade | New feature adopted | Used in new intake flow | Admin |
Frequently asked questions
When did Summer ’26 reach production?
Production upgrades ran on scheduled weekends between May and June 2026, depending on the instance. The Trust site lists your instance’s date.
Do the new date operators work with DateTime fields?
They are designed for Date fields. DateTime conditions still need other approaches, such as formulas.
Where do we find retirements for this release?
In the official release notes, which list retirements, release updates and security changes.
