Customer is the foundation of every business success. To build better relationship and understand their need, you want not only easy to use tools but also personalized experience. Salesforce completely understand importance of this and provides community with multilanguage support. You can enhance engagement with your customer & partners. This blog will assist you to setup community with multiple language and provide better experience to your customers.

    1. Translation Workbench:
      Translation workbench in Salesforce handle different artifact type to have their translation setup. This doesn’t just work for Salesforce Internal user but also for communities. You can locate translation workbench here:Setup -> Translation Workbench-> Translation Setting – you can configure various languages for which translation required.-> Translate – Here you can translate various artifact type for language you have configured in Translation setting.You can find more detail here:


    1. Custom Labels:
      There is a saying – “Don’t judge book by it’s cover”. “Labels” may sound un-related when it comes to translation. However, this is far more then what it is called. You can use Label to hold static text and translate it to languages set at org level.
      You can locate labels here:Setup -> Create -> Custom LabelsFind more detail here:


    1. Import Export Translated Content:
      This is a special feature which was introduced as part of community builder. Using this feature, you can import/export translated content for community pages in XML format. Once imported, you can check content translation in community builder for specific pages by switching language.Locate Import Export wizard here:Setup -> Communities -> Builder -> Setting -> LanguageFind more detail here:


  1. Record Translation:
    Unfortunately, there is no provision of record translation in Salesforce. With that, Salesforce display data in same language, it is stored in. However, sometime it is required to translate record’s data based on user’s language. To achieve that, you can use simple data model design:Step 1: Create self lookup field on object to define primary and translated record.Step 2: Create a global picklist for languages setup in org and then create a picklist on object to tag record with specific language.Step 3: Define Record type to distinguish primary and translated record.Step 4: Write apex to query record based on user’s language.