CRM Analytics provides localization support for metadata such as field labels. However, the actual data values within datasets are not localized or translated. This is an expected limitation of how CRM Analytics handles locale and language settings.
How Localization Works in CRM Analytics
To see translated labels, both the locale and language settings must be configured for the Analytics Cloud Integration User. The locale set in the Integration User's metadata is applied to all users — individual users' own locale and language settings do not override it. This means that all users see the same date formats, time formats, number formats, and dimension label names, regardless of their personal locale preferences.
What Is and Is Not Localized
Field labels (metadata) are translated. For example, the label for the Opportunity "Stage Name" field is localized and appears translated.
However, the values within those fields (data) are not translated. For example, the picklist values within "Stage Name" — such as "Closed Won", "Closed Lost", and "Qualified" — are considered data within the CRM Analytics dataset and appear in English regardless of the user's language setting.
This is expected behavior and is a known limitation of CRM Analytics localization support.
This behavior — data values not being localized in CRM Analytics — is expected and by design. There is no configuration change that will cause data values within datasets to be translated, as CRM Analytics only localizes metadata (field labels), not actual data values.
If you require localized data values, the source Salesforce data itself must be stored in the desired language before it is synced into CRM Analytics.
For a complete list of CRM Analytics limitations, see CRM Analytics Limitations.
000383908

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.