The upcoming Salesforce Spring ’26 Release is rolling out soon—and if you’re responsible for your org, you’ll want to be ready. New system behaviors will be enforced in January 2026, and organizations that don’t prepare may face unexpected disruption.
Here’s a breakdown of the key changes and how to prepare in your sandbox and production environments.
What’s New & Key Changes
1. Calculate Tax-Only and Product-Only Price Adjustments
If your org uses the Order Item Summary object (commonly used in Commerce/Order Management), Spring ’26 changes how tax-only and product-only adjustments are calculated.
Impact Areas:
- Integrations
- Reports
- Apex logic referencing
adjustmentType
Recommended Actions:
- Enable the release update test run in sandbox.
- Test fee cancellations, blind returns, and returns involving fees.
- Activate in production during a low-usage window.
2. Escaped <apex:inputField> Labels in Visualforce
Salesforce will begin automatically escaping the label attribute on <apex:inputField>. If your pages already escape labels manually, you may see double-escaping.
Recommended Actions:
- Scan Visualforce pages for
<apex:inputField>. - Enable the update in sandbox and validate all impacted pages.
- Deploy necessary updates before production enforcement.
3. Hard-Coded Instance URLs Must Be Updated
API calls using instance-specific domains (e.g., na76.salesforce.com) will no longer be automatically redirected. My Domain URLs must be used.
Recommended Actions:
- Review Apex, Flows, middleware, and integrations for hard-coded instance URLs.
- Replace with My Domain URLs.
- Validate functionality in sandbox before enabling in production.
4. Additional Enforcements
Spring ’26 includes other required changes, such as updates to the SAML framework and restrictions on Flow runtime permissions. Review applicable updates in the release notes.
How to Prepare
Sandbox Preparation
- Enable each update in Test Run mode.
- Conduct regression testing for Apex, Flows, integrations, and UI components.
- Monitor logs for exceptions or behavioral changes.
User Communication
- Notify impacted teams before changes take effect.
- Provide clear documentation for any changes to workflows or behavior.
Production Deployment
- Schedule changes during low-traffic windows.
- Activate updates incrementally.
- Maintain a rollback plan in case unexpected issues arise.
Post-Go-Live Review
- Monitor error logs and user reports.
- Verify integrations and automation paths.
- Update internal documentation as needed.
Final Thoughts
Spring ’26 includes several mandatory backend changes that require preparation and testing. By completing validation in sandbox, communicating updates early, and deploying strategically, organizations can ensure a smooth transition without disrupting business operations.
Leave a Reply