{"id":93,"date":"2021-03-17T14:15:24","date_gmt":"2021-03-17T13:15:24","guid":{"rendered":"https:\/\/transferttexei.wordpress.com\/2021\/08\/09\/tips-tricks-4-quickly-translate-custom-labels-from-excel-to-salesforce-using-sfdx\/"},"modified":"2024-04-17T16:45:45","modified_gmt":"2024-04-17T14:45:45","slug":"tips-tricks-4-quickly-translate-custom-labels-from-excel-to-salesforce-using-sfdx","status":"publish","type":"post","link":"https:\/\/texei.com\/en\/advices\/tips-tricks-4-quickly-translate-custom-labels-from-excel-to-salesforce-using-sfdx\/","title":{"rendered":"Tips & Tricks #4\u00a0: Quickly translate custom labels from Excel to Salesforce using SFDX"},"content":{"rendered":"\r\n

Hello everyone, today we will continue our \u201cTips & Tricks<\/em><\/strong>\u201d series. We will evoke a very painful point for me\u00a0: TRANSLATIONS<\/strong>.<\/p>\r\n\r\n\r\n\r\n

For everyone who has already worked on that, you know that is an endless journey to translate using Salesforce UI. It\u2019s repetitive, it\u2019s long and maybe boring.<\/p>\r\n\r\n\r\n\r\n

So I\u2019m going to share you a trick to go faster in the translation of custom labels using a Excel file and metadata file and a bit of SFDX.<\/p>\r\n\r\n\r\n\r\n

\"Love<\/figure>\r\n\r\n\r\n\r\n

STEP 1\u200a\u2014\u200aGenerate a CSV\u00a0template<\/h2>\r\n\r\n\r\n\r\n

Just before starting on this topic, I advise you to create all labels before translating them, it\u2019s easier to update a file every time you create a new one, instead of trying to get all at the end of your tasks or project.<\/p>\r\n\r\n\r\n\r\n

So we will see one of Excel template file you can use to do so.<\/p>\r\n\r\n\r\n\r\n

Let\u2019s create 3 columns\u00a0:<\/p>\r\n\r\n\r\n\r\n

1<\/strong>\u2014\u200a<\/strong>Custom Label Name<\/strong>\u00a0:<\/h3>\r\n

Use it to store the custom label\u2019s name.<\/strong><\/p>\r\n\r\n\r\n\r\n

I like to use this naming convention starting with the object name the label refers to, followed by if it\u2019s a button or a checkbox label\u2026, and give an explicit name, for example\u00a0: CONTRACT_BUTTON_ACCEPT<\/em><\/p>\r\n\r\n\r\n\r\n

2\u200a\u2014\u200aThe native language value<\/strong>\u00a0:<\/h3>\r\n

In my example I used English, it will be easier for the person who will translate and you can use this file as a unique repository for the English texts.<\/p>\r\n\r\n\r\n\r\n

3\u200a\u2014\u200aThe translated value\u00a0: <\/strong><\/h3>\r\n

Insert here the translated text.<\/p>\r\n\r\n\r\n\r\n

\"Excel<\/figure>\r\n\r\n\r\n\r\n

First step is now completed and you are wondering how this can be uploaded to Salesforce.<\/p>\r\n\r\n\r\n\r\n

\"That's<\/figure>\r\n\r\n\r\n\r\n

\u00a0<\/h2>\r\n

STEP 2\u200a\u2014\u200aConvert to Salesforce language<\/h2>\r\n\r\n\r\n\r\n

This part will be, I think, the trickiest part. We are going to use the concatenation of two cells in Excel.<\/p>\r\n\r\n\r\n\r\n

You can find here<\/a> the link to the Office documentation about concatenating two cells.<\/p>\r\n\r\n\r\n\r\n

Our goal is to have something similar to this XML sample\u00a0:<\/p>\r\n\r\n\r\n\r\n

<customLabels>\r\n<label>Veuillez accepter les conditions du contrat<\/strong><\/label>                <name>CONTRACT_ACCEPT_TERMS<\/strong><\/name>\r\n<\/customLabels><\/code><\/pre>\r\n\r\n\r\n\r\n
As you can see, where are using column 1 and 3 from our Excel file in our concatenation formula.<\/p>\r\n\r\n\r\n\r\n
To reach that sample you have to use this formula for line 2 of our file\u00a0: \u201c<customLabels><label>\u201d & C2 & \u201c<\/label><name>\u201d & A2 & \u201c<\/name><\/customLabels>\u201d<\/strong><\/p>\r\n\r\n\r\n\r\n
Copy the formula for all the lines concerned.<\/p>\r\n\r\n\r\n\r\n
Step 2 is now completed, Good Job\u00a0!<\/p>\r\n\r\n\r\n\r\n
\"Well<\/figure>\r\n\r\n\r\n\r\n
\u00a0<\/h2>\r\n
STEP 3\u200a\u2014\u200aConvert to Salesforce file<\/h2>\r\n\r\n\r\n\r\n
At this point we have all the data ready to be inserted in Salesforce.<\/p>\r\n\r\n\r\n\r\n
Let\u2019s create another file for Salesforce. The name has to be\u00a0: languagecode.translation. <\/em><\/strong>For our example \u201cfr.translation\u201d.<\/p>\r\n\r\n\r\n\r\n
Open your file and add this in your file\u00a0:<\/p>\r\n\r\n\r\n\r\n
<?xml version=\"1.0\" encoding=\"UTF-8\"?>\r\n<Translations xmlns=\"http:\/\/soap.sforce.com\/2006\/04\/metadata\">\r\n\/\/ INSERT YOUR CODE HERE\r\n<\/Translations><\/code><\/pre>\r\n\r\n\r\n\r\n
After that go back to your translation file and copy all the content of you column E and replace the \u201c\/\/ INSERT YOUR CODE HERE\u201d part with the content you just copied.<\/p>\r\n\r\n\r\n\r\n
After that you should have something like this\u00a0:<\/p>\r\n\r\n\r\n\r\n
\"\"<\/figure>\r\n\r\n\r\n\r\n
The file extension has to be\u00a0.translation not\u00a0.xml or\u00a0.txt. For that verify that the file extension file is visible.<\/strong><\/p>\r\n\r\n\r\n\r\n
\u00a0<\/h3>\r\n
STEP 4\u200a\u2014\u200aAdd translation file to\u00a0metadata<\/h2>\r\n\r\n\r\n\r\n
Go to your project sources folder, by default it\u2019s\u00a0: \u201cforce-app\\main\\default\u201d<\/em><\/p>\r\n\r\n\r\n\r\n
Find the folder \u201ctranslations\u201d, <\/em><\/strong>if you don\u2019t find it just create it.<\/p>\r\n\r\n\r\n\r\n
Finally add the \u201cfr.translation\u201d in it.<\/p>\r\n\r\n\r\n\r\n
And voila everything it\u2019s ready, here we go to the last part\u00a0!<\/p>\r\n\r\n\r\n\r\n
\u00a0<\/h3>\r\n
STEP 5\u200a\u2014\u200aDeploy file to Salesforce<\/h2>\r\n\r\n\r\n\r\n
If you are using Visual Studio Code, you can use the SFDX: Deploy Source to Org.<\/p>\r\n\r\n\r\n\r\n
\"Use<\/figure>\r\n\r\n\r\n\r\n
Similarly, if you are using SFDX commands use\u00a0: \u201csfdx force:source:deploy -p \u201cpath\/to\/translations\u201d<\/em><\/strong> \u201c.<\/p>\r\n\r\n\r\n\r\n
\u00a0<\/h2>\r\n
To conclude\u00a0!<\/h2>\r\n\r\n\r\n\r\n
I hope you enjoy this little trick. I really think it\u2019s important to ask for the translations at the end of your development. If I have too resume why\u00a0:<\/p>\r\n\r\n\r\n\r\n