---
schema_version: "1"
id: da5b9b64b4922cf29036bbc92bc51be6d535dc7417e2df03a92f6c10d87f5871
title: Custom Code and Locale Format Changes
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/admin_locales_code.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.admin_locales_code.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: d301e3776d74e20c2ff858c76981055b8d45ef870aa099a668a52a6b472c8bd3
description: Address, currency, date, datetime, integer, name, and time formats can change when a user changes locales. These formats can also change when the locale format standard changes or formats are updated. Learn how to avoid errors by using locale-neutral methods in your code and review examples. Then understand how to verify that your integrations work with new or changed formats.
products:
  - Salesforce Platform
  - Cross Cloud
release: "264"
---
# Custom Code and Locale Format Changes

Address, currency, date, datetime, integer, name, and time formats can change when a user changes locales. These formats can also change when the locale format standard changes or formats are updated. Learn how to avoid errors by using locale-neutral methods in your code and review examples. Then understand how to verify that your integrations work with new or changed formats.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: all editions</td></tr></tbody></table>

- **[Use Locale-Neutral Methods in Code](https://help.salesforce.com/s/articleView?id=xcloud.admin_locales_code_methods.htm&release=264.0.0&type=5)**  
    Data formats can change based on the user’s locale, adoption of new standards, or updates to the standard locale formats. To avoid errors when a locale format changes, use standard methods to handle this data in your code. If your code formats the data using the user’s locale, apply the format after all other processing is complete.
- **[Example Code with Locale-Formatted Data](https://help.salesforce.com/s/articleView?id=xcloud.admin_locales_code_examples.htm&release=264.0.0&type=5)**  
    Review examples of code that handles data that can be formatted based on the user’s locale. See how code can break when it relies on a specific format for dates, times, and currencies. And review examples of how to fix these issues by using standard methods for handling these types of data.
- **[Update Your Integrations for New Locale Formats](https://help.salesforce.com/s/articleView?id=xcloud.admin_locales_code_integrations.htm&release=264.0.0&type=5)**  
    If you integrate data from external systems into Salesforce or if you send Salesforce data to external third parties, use locale-neutral formats whenever possible in the related code. When locale formats change, review the code that handles the affected formats.

#### See Also

- [Adopt the ICU Locale Formats](https://help.salesforce.com/s/articleView?id=xcloud.icu_migration_how.htm&release=264.0.0&type=5 "The ICU locale format release update is available for all orgs. Review the high-level process to successfully migrate to the new International Components for Unicode (ICU) locale formats. Some of the formats differ from the ones provided by Oracle’s Java Development Kit (JDK). Understand how to determine the impact of changes on your org, and learn about the updates required to support the new formats.")
- [API Versions for Apex Classes, Apex Triggers, and Visualforce Pages](https://help.salesforce.com/s/articleView?id=xcloud.admin_locales_update_api.htm&release=264.0.0&type=5 "The International Components for Unicode (ICU) locale formats are available with API version 45.0 and later. To use the ICU locale formats in your customizations, all Apex classes, Apex triggers, and Visualforce pages must use API version 45.0 or higher..")