The Salesforce Spring ’25 release is just around the corner, bringing a mix of exciting new features, critical updates, and changes designed to enhance the platform’s usability and security. However, with each new release comes the responsibility of preparation, ensuring that your Salesforce environment remains seamless and efficient. Whether you’re a developer, admin, or end user, staying informed and proactive is key to leveraging these updates to their full potential. This blog explores the essential updates in the Spring ’25 release, offering practical steps and tips to help you prepare your Salesforce org, minimize disruption, and make the most of the new features.
Image source: Salesforce
General Preparation Tips
-
Use Sandboxes
Perform all updates in sandboxes before production deployment.
-
Schedule Changes
Make changes during non-working hours to allow rollback if issues arise.
-
Review Managed Packages
Check compatibility with package providers for impacted features.
These steps will ensure your Salesforce org is ready for the Spring ’25 release updates with minimal disruptions.
Key Changes in Spring ’25
-
.Change Einstein Activity Capture Permissions for Sales Engagement Basic Users
-
Impact
Users with the Sales Engagement Basic User permission set will lose access to Einstein Activity Capture. They need to be assigned the Standard Einstein Activity Capture permission set. Cloned permission sets will also lose access.
Image Source :Salesforce Help
-
Preparation
- No Code:
- Create a Permission Set List View showing permission sets with “Use Einstein Activity Capture.”
- Pro Code:
- Search metadata for AutomaticActivityCapture references.
- Adjust permissions in a sandbox first. Ensure users have appropriate access without losing needed permissions from Sales Engagement Basic User.
- No Code:
-
Production Steps
After sandbox testing, update permissions in production and validate Einstein Activity Capture functionality.
-
Enable ICU Locale Formats
-
Impact
Salesforce is moving from Oracle’s JDK Locale Formats to ICU Locale Formats, which affect date, time, names, addresses, and number formats.
Enforcement rolls out until Summer ’25. Users with en_CA locales should ensure ICU formats are enabled. For Formats, follow this guide on Salesforce Help. -
Preparation
- Check current formats using Salesforce Help.
- For JDK Locales:
- Enable a test run in a sandbox.
- Update Apex classes, triggers, and Visualforce pages as needed.
- Test impacted functionality thoroughly before enabling the update.
-
Production Steps
- After sandbox validation, deploy updates outside working hours.
- Enable the update well ahead of enforcement to allow rollback if needed.
-
Verify Your Return Email Address for Sender Verification
-
Impact
Return email addresses must be verified before being used. Users will receive verification emails once per release until Spring ’25.
-
Preparation
- No Code and Pro Code:
- Users should check their email settings at:
/lightning/settings/personal/EmailSettings/home. - If the “Resend Verification Email” option is available, users should click it and follow the email instructions.
Image Source: Salesforce
- Users should check their email settings at:
- No Code and Pro Code:
- Production Steps:
- Ensure users verify return email addresses before Spring ’25 enforcement. For return email addressREAD MORE: Verify Your Return Email Address for Sender Verification (Release Update)
Conclusion
Remember, preparation is not just about addressing immediate impacts but also about future-proofing your Salesforce org for sustained success. Stay informed, collaborate with your team, and leverage Salesforce tools to make this release work to your advantage. With the right approach, you can turn these updates into opportunities to optimize processes and enhance the user experience.
