---
schema_version: "1"
id: 9cd0e899faa9a47ffa696c1d858fbbe9f578e571f3de78151ed1c1f16c73a840
title: Translating Freeform Text Attributes
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_translating_freeform_text_attributes.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_translating_freeform_text_attributes.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: ae156e8a23403379d1135a5e8de37f2487f4067257082962b28f4f33f9f1b1cc
description: As an administrator, you can use this feature to configure freeform text attributes as either translatable or not-translatable. This enables you to specify what product attributes are translated into other languages. In previous releases, all product attributes (string data-type attributes) were translated, regardless of whether they were freeform or picklist-enabled. As of Winter '19 release, you can configure freeform string attributes to specify if the string is translatable. For example, you might not want to translate email addresses, locations, or comments in freeform string attributes.
products:
  - Communications
  - Media
  - Energy and Utilities
release: "264"
---
# Translating Freeform Text Attributes

As an administrator, you can use this feature to configure freeform text attributes as either translatable or not-translatable. This enables you to specify what product attributes are translated into other languages. In previous releases, all product attributes (string data-type attributes) were translated, regardless of whether they were freeform or picklist-enabled. As of Winter '19 release, you can configure freeform string attributes to specify if the string is translatable. For example, you might not want to translate email addresses, locations, or comments in freeform string attributes.

To configure the text attributes as either translatable or not-translatable:

1. From App Launcher, click Vlocity Objects and Object Types.
2. Create or update an Object Type definition.
3. Assign an existing text attribute. Do not use a picklist.
4. Uncheck the flag to indicate the attribute is not translatable.
5. Ensure all the translation activities are performed for other attributes and fields. For more information, see the other topics in [Multi-language Support for Shared Catalog](https://help.salesforce.com/s/articleView?id=ind.comms_multi_language_support_for_shared_catalog.htm&release=264.0.0&type=5 "When communications service providers sell products in different regions, it’s important that you translate significant product details into multiple languages. Translation helps sales agents find the things they need easily by making all the relevant details, such as properties, cross-sell, or upsell suggestions, available to them in their preferred language.").
6. Log into your org with a non-English locale, such as French or Spanish.
7. Create an order with a product that contains the translatable attribute.
8. Enter values for the attribute in, for example, English and click **Save**.
9. Reopen the order and verify the attribute value. It should be in English, the original language in which the attribute value was entered.