#Translation Workbench0 debatiendo

[▶️]🔴🔥🎬 How to Implement Multi-Language Translation in Salesforce Flow

Translation in Salesforce involves localizing and adapting the platform to support multiple languages, making it easier for users around the world to interact with the system in their preferred language. Salesforce offers several features and tools to manage translations:

• Salesforce Translation Workbench
• Custom Labels
• Multi-Language Support in Knowledge Base
• Global Picklists
• Language Settings for Users
• Translation API

In this blog post, I will share the different ways how you can make your Salesforce Flow to support Multi Languages.

🎬 https://youtu.be/zIAF1-xb8Vc

📒 https://sudipta-deb.in/2024/07/how-to-implement-multi-language-translation-in-salesforce-flow.html

@The Blog Group

#Translation Workbench  #Flow

 Hello there

I was wondering if the content of the translation workbench could be also deployed as part of an unmanaged package.

As I have seen so far translation workbench can be deployed between diffent environment via import/export functionality, but this would be a manual step 

I would like to know your opinion/advice

#Unmanaged Package #Deployment #Translation Workbench

To reproduce issue with retrieve:

0. FSC package installed in an org.

1. Go to Setup -> Translation Workbench -> select Language and Setup Component = Global Value Set

2. Enter Value Label Translation for a 1+ Countries and/or Languages

3. Save the changes

4. Retrieve GlobalValueSetTranslation metadata components with API 55.0 (e.g. via package.xml and VS Code):

Finserv__Countries

Finserv__Languages

5. The components are retrieved, but don't contain the translation values (value in <translation></translation> is still commented as by default) that were entered in the Translation Worbench.

Expected result:

1. Changes done and saved in Translation Workbench are reflected in the .globalValueSetTranslation-meta.xml when retrieved

Current workaround:

1. Retrieve GlobalValueSetTranslation metadata components

2. Update translations as necessary in the .globalValueSetTranslation-meta.xml file(s)

3. Deploy the files into required orgs.

4. Changes done in xml files are deployed correctly.

Extra notes:

1. Translation entered via the workaround are retrievable, but translations entered via Translation Workbench are not.

#Metadata API #Global Value Sets #Translation Workbench

Okay so, I have an object called "Travel Fee"  I've added the translate button to the page layout, clicked it, entered the desired translated values, all is good until I switch language and it's not getting translated. Is this a bug or is there something I am missing?

#Salesforce CPQ & Billing  #Translation Workbench

Hi 

We have a use case where we want to predefine the Task subject from a Case for something like "Transfer". We also have a picklist value in the Task Subject for "Transfer".

Looking at Salesforce because the Subject field is a free text and picklist rolled into one then we have to set the predefined value as TEXT like "Transfer"

However, the org also has translations enabled so when our Slovak users are trying to use that quick action the subject field is still "Transfer" even though we have updated the translation in the translation workbench. If I update the predefined value to the Slovak for "Transfer" then that renders on everyone else's screen and negates the language setting of the user. We then want a flow to fire off that subject within the case so we can fire automation off the subject "Transfer". When the user selects the value from the picklist element of the subject the back end flow fires however if they leave the predefined value in there it doesn't presumably because the values are technically different. 

Any ideas on selecting picklist value for the predefined value on Task Subject or how to go about resolving this? We can obviously put in the flow decision to fire off the different languages but that is unmaintainable if we have 50+ languages and the predefined value is still wrong in the users view

Thanks in advance

#Translation Workbench  #Translations  #Quick Actions  #Task Quick Action  #Task Quick Actions  #Service Cloud  #Automation