ICU Locale Formats, API Version ↓45 - Spring 25 Release Error

With Spring ’25, Salesforce will attempt to enforce the Enable ICU Locale Formats release update and enable the new ICU locales in all orgs.

If Salesforce attempts to enforce the release update on either a sandbox or production org, and the enforcement fails, the org admin will receive an email. If the release update fails, we will retry to enforce the release update in the next release.

The most common failure occurs if an org contains Apex Classes, Apex Triggers and Visualforce Pages that don’t meet the minimum required API version 45.0. If your org contains lower API versions of these components, Salesforce won’t enable ICU locale formats in your org. Your org will remain on JDK until you manually enable ICU locale formats.

Resolution

Salesforce Org Review & API Version Update Process

  1. Access the Client’s Salesforce Org - Gain access to the client’s Salesforce environment for review.

  2. Verify ICU Locale Formats - Confirm whether ICU (International Components for Unicode) Locale Formats are being utilized within the Salesforce Org.

  3. Determine Active Locales in the Salesforce Org - Identify the locales currently in use within the Salesforce Org. Check both Org-wide and User-specific locale settings.

  4. Audit API Versions Below v45 - Conduct an audit to identify components that are utilizing an API version earlier than v45. This includes:

    • APEX Triggers

    • APEX Classes

    • Visualforce Pages

  5. Generate a Report - Provide a detailed report listing all locations where updates to API versions are necessary.

  6. Review and Estimate- Review the report and provided an estimate.

  7. Update API Versions in Sandbox Environment - Implement API version updates for the identified components in a Salesforce Sandbox environment:

    • APEX Triggers

    • APEX Classes

    • Visualforce Pages

  8. Unit Testing - Perform unit testing on all updated components to ensure functionality is intact.

  9. Client Demonstration - Conduct a demonstration of the updated components to the client for feedback.

  10. Client QA Testing - Allow the client to perform QA testing to validate the changes in the sandbox environment.

  11. Production Deployment - Once QA is complete, proceed with the deployment of the updated components to the production environment.

This is to be completed in a Sandbox environment and thoroughly tested to ensure Manages Packages and other integrations are not impacted.

Note: Orgs created in Winter ’20 or later have ICU formats enabled and this is not needed.

Resources

Did you get this email?

Image
Contact Us