Rules and guidelines for managing multilingual assets

Configuring multilingual attributes

• •Before you set an attribute as multilingual, remove all rule associations configured for the attribute.
• •After you enable the multilingual property and save the asset, you can't disable the property or add rule associations to the attribute.
• •You can set only string attributes as multilingual, such as Name and Description. You can't set the Code attributes as multilingual.
• •You can't set default values for multilingual attributes. When you set an attribute as multilingual, Reference 360 clears the default value that you previously set for the attribute.
• •Don't use the reserved words _language and _localizedContent as attribute names. For a complete list of reserved keywords, see Reserved keywords.
• •After you set attributes in a code list as multilingual, complete all the export and import model updates for the code list. You can then reindex the code list so that search results include the localized data. To reindex the code list, contact Informatica Global Customer Support.
• •After you optimize assets in your organization, you can't enable the multilingual property on any reference data assets in Reference 360. For more information about asset optimization, see asset optimization modelling and Enhancing Reference 360 UI Performance for Large Data Sets.

Managing display languages in a code list

• •You can't remove an additional language for a code list if a code value contains data in that language. To remove the language, first purge or clear the values in the code list. You can then remove the language and reimport the data. Therefore, when you configure the code list, select the additional languages based on your anticipated business needs.
• •Reference 360 uses the browser language preferences to determine which language displays picklist values in the business application. To display picklist values in a specific language, move that language to the top of the language preferences in your browser, add the corresponding BCP 47 language code to the Localization Languages code list, and maintain values for it.
• •In MDM SaaS business applications, multilingual assets appear as picklist field values in your browser locale language. If a value is not available in that language, the business application displays it in the default language of the reference data. MDM SaaS business applications use the following rules to match languages:
• - A browser language matches any language code that starts with it. For example, de matches de, de-LI, and de-AT, but de-LI matches only de-LI and doesn’t match de. If your browser languages are de-IN and then de, and the code list contains de-LI but not de-IN or de, Reference 360 shows values in de-LI.
• - When you select a regional language in your browser, the browser also checks its base language. For example,if you select de-LI and the code list contains de but not de-LI, Reference 360 shows values in de. If the code list contains both de-LI and de, Reference 360 shows values in de-LI.
To show values in a specific regional language, add the regional language BCP 47 code to the Localization Languages code list and maintain values for it.
• •When you view an attribute value in a language for which no value exists, Reference 360 displays an empty value for that language. For example, you set the Status attribute as multilingual and store values in English (en-US) and French (fr-FR). When you choose to view the value in Japanese (ja-JP), Reference 360 returns an empty value because Reference 360 stores no Japanese value for the attribute.
• •When you configure a combination of display attributes, such as a concatenation of the Name, Code, and Description, to represent code values in other assets, and if a multilingual attribute has no stored value, Reference 360 shows an empty string for each field that has no value in the preferred language. For example, you might want the Code, Name, and Description attributes to represent code values in the Country Codes code list. You might have a code value with the Name as Canada, the Code as 124, and no stored value for the Description attribute in the preferred language. When the code value appears in other assets, it appears as 124-Canada-. For more information about configuring display attributes, see Configuring display attributes.

Viewing code values and history

• •You can't sort code values based on multilingual attributes on the Values tab of a multilingual code list.
• •The change history of a code value with multilingual attributes shows values in the browser language you used when you created or updated the code value. If you change your browser language later, earlier history events continue to show values in the original language. For example, if you update a code value while your browser uses Japanese, the history event continues to show Japanese values after you switch to English.
• •When you create a code value in a multilingual code list, the default value for a required reference attribute isn’t displayed. Reference 360 skips validation and saves the code value even though the attribute appears empty. However, the default value shows up after you save the code value.

Exporting and importing multilingual data

• •When you export a code list at a point in time that precedes localization, the export file contains only the Code attributes, and you can't export localized attributes, such as Name and Description.
• •When you enable the multilingual property for one or more attributes and save the code list, the data in those attributes is deleted, so back up the attribute data before you enable the property. Export the code values to a CSV file that is prepared for localization, so that you don't have to add language rows manually. Edit the export file, add multilingual code values, and then use it as the source file for import after you enable the property.
For more information about exporting and reimporting code values, see Exporting code values and Import multilingual code values into code lists.
• •In the exported CSV file, the number of rows is based on the number of target languages, and the file includes the _language and _localizedContent fields. During import, the import process automatically maps the _language and _localizedContent fields.
The following table describes a sample exported CSV file that includes _language and _localizedContent fields:

_language	_localizedContent.Name	Code	Description	status.status.key	effectiveDate
en-US	Female	F	Identifies a person as female.		18-06-2025
pt-BR	Feminino	F			18-06-2025
en-US	Male	M	Identifies a person as male.		18-06-2025
pt-BR	Masculino	M			18-06-2025
en-US	Unknown	U	Indicates that the gender is unknown or not specified.		18-06-2025
pt-BR	Ignorado	U			18-06-2025

• •When you export a code list that contains multilingual attributes, Reference 360 ignores sort filters applied to multilingual attribute columns. The exported data doesn’t reflect the specified order.
• •During file import, you can import data for a language code that isn't in the Localization Languages code list. The import doesn't require a value for the default language. The import lets you skip the value for the default language though a value for the default language is required. For example, you import a code value with the language code fr-FR, which isn't in the Localization Languages code list but is a valid BCP 47 code. If en-US is the default language, Reference 360 requires a value for the Name (en-US) attribute. However, the import doesn't require it, and the import completes successfully because the language code is valid.
• •When you use the import version 2 or version 3 REST API to import code values into a multilingual code list, the import fails if the import settings include field mappings for localized fields, such as _language, _localizedContent.Name, or _localizedContent.Description. To import localized code values, omit the mappings object from the import settings.
Match the column headers in the CSV file to the field names in the code list. Add the _localizedContent. prefix to the field name for localized fields, such as _localizedContent.Name or _localizedContent.Description. In the _language column header, enter the BCP 47 language code for the language of the localized content.

Using multilingual picklist values in MDM SaaS business applications

• •When you change a multilingual picklist field value, the history event displays the Code attribute value instead of the Name attribute value of the reference data.
• •When you filter search results, the Filters panel displays values in your browser locale or in the default language of the picklist if not localized for your browser locale. For example, if a field is localized into German with English as the default language, a French-locale browser displays the English values.
• •When you sort records, use auto-suggest, or view the search results, picklist values appear in the default language configured for the field, regardless of browser locale.
• •When you export records that have localized picklist fields, the exported data contains only the codes for those fields, not their values.
• •After you localize reference data, reindex the records in each business entity that uses the reference data so that you can search for records by using the localized data in picklist fields.
For more information about searching for records with localized picklist values, see Searching for records with localized picklist values.
For more information about generating search indexes, see Defining generate search indexes or match keys job in Business 360 Console help.
• •When you retrieve business entity records through the Business 360 REST APIs, use the optional Accept-Language request header to get picklist values in your preferred language. If you don't specify the language in the header, or if no value exists in the requested language, the APIs return values in the default language of the reference data.
For more information about retrieving localized picklist field values using Business 360 REST APIs, see Business 360 REST API Reference in Business 360 Console help.