Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

How to disable content from getting translated in service portal

Singh3
Tera Contributor

Hi,
I have a scenario in which we are pulling the value of the connected content from backend and retrieving the values in a widget. These however are getting auto translated which we do not want. Is there a way by which we can stop this auto translations from happening?

The coding lines are as follows:

if(grTopic.next()){
                var result;
                if(data.contentype =="featured")
                {
                    result = {
                        name:grTopic.getDisplayValue(),
                        sysId:grTopic.getUniqueValue(),
                        connectedContents: _getFeaturedContents(grTopic.getUniqueValue(),grTopic.getDisplayValue())
                    }
                }
                else if(data.contentype == "connected")
                {
                    result = {
                        name:grTopic.getDisplayValue(),
                        sysId:grTopic.getUniqueValue(),
                        connectedContents: _getConnContent(grTopic.getUniqueValue(),grTopic.getDisplayValue())
                    }
                }
                topicData.push(result);
            }
        }
1 REPLY 1

Community Alums
Not applicable

Hi @Singh3 ,

there's a few things to unpack here:

  1. Is it technically possible - yes, you would need to find the translations in the [sys_translated] and [sys_translated_text] tables respectively, which won't be a small task. 
  2. It would not be in-line with our best-practice, because this would by definition create a "mixed language experience" leading to a sub-optimal User-Experience (UX).

If users who have their language set to the language in question and want to navigate around where they don't understand English, they would struggle - hence the bad UX comment.

 it is not advisable to do this as it wouldn't be in the best interest of the end-user and defeats the objective of having a translated UI,