Locale Information in Company Settings defines the default regional experience for subscriber organizations in your Vertical Studio application. You can configure values that control how users see language and time-based behavior when they start using the application.
The Locale Information settings are:
- Language: Sets the default language used in the subscriber organization.
- Country locale: Sets regional formatting behavior, such as locale conventions.
- Time Zone: Sets the default time zone context for organization-level time references.
- Time Format: Sets how time is displayed, such as 12-hour or 24-hour format.
These defaults help you provide a localized starting point for subscribers at signup.
For instance, if your app is a Real Estate application for Australia, most subscribers may be from Australia. In that case, you can set Language, Country locale, Time Zone, and Time Format to Australian defaults.
- Log in to your Developer Console.
- Go to Build > Company Settings.
- Open Locale Information tab.
- Configure the default values for:
- Language
- Country
- Time Format
- Time Zone
- Save your changes.
Assume you configure these defaults in the Developer Console:
- Language: English (United States)
- Country : India
- Time Format: 12-hour
- Time Zone: (GMT 5:30 ) India Standard Time( Asia/Kolkata )
When a new subscriber signs up to a version containing this configuration, the subscriber organization starts with these locale defaults.
Publish and Version upgrade behavior
Packaged Locale Information settings are configured in the Developer Console and included in the published application version. Locale Information settings are non-upgradable for existing subscriber organizations. Changes made after a subscriber has already received a version do not deploy to that existing subscriber through upgrade. For existing subscribers, later locale changes from the developer are not applied during upgrade.
The following table explains the upgrade behavior of an existing packaged Location Information settings that are already deployed in the subscriber's organization.
Property | Upgrade Type | Subscriber Modify Access |
Language | Non-Upgradable | YES |
Country | Non-Upgradable | YES |
Time Format | Non-Upgradable | YES |
Time Zone | Non-Upgradable | YES |
Version scenarios
Case 1: Publish a version with Locale Information defaults
Locale Information is present by default in the application. When you publish an application version, new subscribers receive the locale values packaged in that version, whether you explicitly updated the settings or kept the default values.
Subscribers can update available locale preferences in their subscriber org. Those subscriber-side changes remain local and are not overwritten by the next version upgrade.
Case 2: Edit Locale Information defaults and publish
When you edit Language, Country locale, Time Zone, or Time Format and publish an upgraded version, new subscribers to that latest version receive the updated defaults. Existing subscribers keep their current values because edited Locale Information does not propagate through upgrade.
If subscribers have already changed their locale preferences in their org, those subscriber-side values continue to stay as-is after the version upgrade.
Consider the following two versions:
- V1 defaults
- Language: English (Australia)
- Country locale: Australia
- Time Zone: Australia/Sydney
- Time Format: 12-hour
- V2 defaults
- Language: English (United Kingdom)
- Country locale: United Kingdom
- Time Zone: Europe/London
- Time Format: 24-hour
After V2 is published, new subscribers who sign up to V2 gets the V2 default value for locale settings. Existing subscribers keep their current locale values, and the V2 upgrade will have no effect on their locale settings.
Case 3: Delete scenario
Delete is not applicable for Locale Information. Locale Information cannot be deleted as a standalone component and can only be updated.
Note
In the Subscriber Organization, Time Format and Language settings are located under Personal Settings. Subscribers can update these settings at any time as per their preference.
Since the changes in Location Information Settings cannot be deployed to existing subscribers through an upgrade, there will be no impacts in the Subscriber's organization.