Translate a field value

RSSG
Tera Contributor

I want to change field value language from english to other language. Already installed plugins for language translation i.e Internationalization language pack and individual language pack like Japanese,Swedish.

Tried to follow the procedure given on ServiceNow Product Document-Translate a field value, but it is not clearly understood, Steps are not clear to me.

Can anyone help to explain in simple way?

thanks

2 ACCEPTED SOLUTIONS

@RSSG 

 

Here is my solution. The field Capability on u_ot_floc should be a translated text field instead of string. Also, I am assuming that this is a normal string field and not choice field.

 

RSSG_4-1680635184898.png

 

I tried to replicate the exact same scenario like yours and translation work perfectly in my case.

Here is my table structure.

Screenshot 2023-04-05 at 1.35.21 PM.png

Screenshot 2023-04-05 at 1.27.17 PM.png

This is the sample data in English language. Please note all the capabilities are in English here

 

Screenshot 2023-04-05 at 1.25.12 PM.png

 

 

 

Screenshot 2023-04-05 at 1.24.52 PM.png

 

Now in order to provide translation in Portuguese, I changed the language from preference and moved back to my table. 

Here I initially see Capability in English, here I change the values of each capability field and add their translation in Portuguese

Screenshot 2023-04-05 at 1.24.06 PM.png

 

This is how the entire table looks after providing the translation in Portuguese Language.

Screenshot 2023-04-05 at 1.26.19 PM.png

Now when I change the language again back to English from preference, this is how my table looks in English.

 

Screenshot 2023-04-05 at 1.25.12 PM.png

Hope this helps. In case if the capability is a choice field then the translation would be provided in a different way. Please let me know if your capability field is a choice field or not.

View solution in original post

Glad finally the solution worked 🙂

 

Here is the solution for the choice field. 

In the following example the field is of type choice

 

Screenshot 2023-04-05 at 8.03.42 PM.png

 

Open the dictionary entry, scroll to the bottom and find the choice related list.

 

Screenshot 2023-04-05 at 8.08.35 PM.png

Click New button and add a choice in English first

 

Screenshot 2023-04-05 at 8.04.44 PM.png

Now add the same choice with a different language code and translated label. Please note that value should remain same for both the translation.

Screenshot 2023-04-05 at 8.12.19 PM.png

Finally your choice list should look like the following.

 

Screenshot 2023-04-05 at 8.05.10 PM.png

Hope this helps.

View solution in original post

22 REPLIES 22

Yes, you get this right. I am giving illustrations here of interconnected tables and I want to know where to put translated text as you mention and how the record producer example get be replicated here. I tried few things but did not work. I also tried through sys_translated_text table ,changing 'string' to 'Translated text' etc. as seen in other discussion forums but no success.

 

Pic-1 is the Conf. dictionary entries ( cmdb table) where Column Label Capibility refers to custom table X.

Pic-2 is the custom table X

Pic-3 is list of custom table having all values for capibility.

Now where to put translated text for these values?

RSSG_0-1680634142629.png

 

RSSG_4-1680635184898.png

 

RSSG_2-1680634627500.png

 

 

@RSSG 

 

Here is my solution. The field Capability on u_ot_floc should be a translated text field instead of string. Also, I am assuming that this is a normal string field and not choice field.

 

RSSG_4-1680635184898.png

 

I tried to replicate the exact same scenario like yours and translation work perfectly in my case.

Here is my table structure.

Screenshot 2023-04-05 at 1.35.21 PM.png

Screenshot 2023-04-05 at 1.27.17 PM.png

This is the sample data in English language. Please note all the capabilities are in English here

 

Screenshot 2023-04-05 at 1.25.12 PM.png

 

 

 

Screenshot 2023-04-05 at 1.24.52 PM.png

 

Now in order to provide translation in Portuguese, I changed the language from preference and moved back to my table. 

Here I initially see Capability in English, here I change the values of each capability field and add their translation in Portuguese

Screenshot 2023-04-05 at 1.24.06 PM.png

 

This is how the entire table looks after providing the translation in Portuguese Language.

Screenshot 2023-04-05 at 1.26.19 PM.png

Now when I change the language again back to English from preference, this is how my table looks in English.

 

Screenshot 2023-04-05 at 1.25.12 PM.png

Hope this helps. In case if the capability is a choice field then the translation would be provided in a different way. Please let me know if your capability field is a choice field or not.

And this worked finally!! 😀 Thank you so much @Sandeep Rajput . You explained it very well, I know it was small task but I was skipping few steps which got cleared at last. Thank you for continuous efforts. 

Ok so what would be a procedure for choice field ? , the capability column in a table here is a string but few other columns will have a choice as well so I would like to know.

I know the procedure when reference is not to any table but simply few options under choice list.

Glad finally the solution worked 🙂

 

Here is the solution for the choice field. 

In the following example the field is of type choice

 

Screenshot 2023-04-05 at 8.03.42 PM.png

 

Open the dictionary entry, scroll to the bottom and find the choice related list.

 

Screenshot 2023-04-05 at 8.08.35 PM.png

Click New button and add a choice in English first

 

Screenshot 2023-04-05 at 8.04.44 PM.png

Now add the same choice with a different language code and translated label. Please note that value should remain same for both the translation.

Screenshot 2023-04-05 at 8.12.19 PM.png

Finally your choice list should look like the following.

 

Screenshot 2023-04-05 at 8.05.10 PM.png

Hope this helps.

Awesome! Thanks . Will try this and I am sure it will work as this is pretty straightforward.

Hope to catch up soon on this forum with some other brainstorming topic 🙂