Skip to main content
hamburger menu Created with Sketch.
PHP2Shell - PHP Vulnerability Announcement || EU Holiday: Oct 23rd - Limited staff, please plan accordingly

Search the Knowledge Base

Preparing Your Org for ICU Locale Formats in Summer ‘25

  • Updated

Question:

How will Veeva orgs be impacted by the enablement of ICU Local Formats with the Salesforce Summer '25 release?

Answer:

This article outlines important information regarding the automatic enablement of ICU (International Components for Unicode) Locale Formats in your Salesforce organization (org) as part of the Summer ‘25 release. It also provides guidance on how to address potential issues that may arise during this process.

Background:

As part of ongoing platform enhancements, Salesforce is transitioning orgs from the legacy JDK Locale Format to the more robust and globally consistent ICU Locale Format. For orgs currently on the JDK Locale Format, Salesforce will attempt to automatically enable ICU Locale Formats during the Summer ‘25 release window.

Potential Issue: Failure Due to Older API Versions

In some cases, the automatic enablement of ICU Locale Formats may fail. If this occurs, you may receive an email notification from Salesforce stating that the enablement failed because your org contains Apex Classes, Apex Triggers, and/or Visualforce Pages utilizing API versions earlier than 45.0.

Important Note: Even if the automatic enablement fails due to older API versions, you still have the option to manually enable ICU Locale Formats.

Recommended Action: Investigate Older API Versions

To ensure a smooth transition and prevent potential compatibility issues, we recommend that you investigate any custom Apex Classes, Apex Triggers, and Visualforce Pages in your org that are using API versions prior to 45.0. Identifying and potentially updating these customizations is a proactive step towards maintaining a stable Salesforce environment.

Veeva and ICU Locale Formats:

Veeva is committed to ensuring compatibility with the latest Salesforce platform updates. With our upcoming 25R1 release, all current Veeva code will be updated to API version 45.0 or later.

We understand that some orgs may still contain older, deprecated Veeva files with API versions earlier than 45.0. Please be aware that Veeva is no longer able to remediate these deprecated files directly.

Steps to Take:

  1. Identify Custom Code: Review your org for any custom Apex Classes, Apex Triggers, and Visualforce Pages with API versions older than 45.0.
  2. Assess Dependencies: Determine whether any of your custom code references the older, deprecated Veeva files.
  3. Manual Enablement: If you confirm that no custom code relies on these deprecated Veeva files, you can safely proceed with manually enabling ICU Locale Formats. Refer to Salesforce documentation for instructions on manual enablement.
  4. Optional File Deletion: If you wish to remove the deprecated Veeva files for better org maintenance and have confirmed no custom code dependencies, you can request their deletion by contacting Veeva Product Support.

If you encounter any issues or have further questions regarding this update, please do not hesitate to contact Veeva Product Support for assistance.

 

Related Documentation:

 

Powered by Zendesk