Hello.
I found an issue with you might not be aware but since most of the implementations are multi-language (i18n) I would like to highlight this topic to save time for the next one.
The ServiceNow platform supports multiple languages, using UTF-8 for international characters. Language support is available when at least one language plugin has been activated, as described in Activate a language.
According to ServiceNow,
"When a user logs in, the language for the instance session is determined by the following logic:
- If the language selection at login is enabled, that language is used.
- If not, the language preference selected using the language picker in the header bar is used.
- If not, the language setting in the User [sys_user] table is used.
- If none of the above are true, the system default language is used.
Some areas of the system are not translated, including journal fields, report titles, and any field that stores free-form text. These fields remain in the language used to create them. When creating a custom field, you must add the labels in the Field Label table because they are not added automatically."
But.. the translation is not as black and white as it is being presented.
I found that the Risk Criteria field (out of the box its a translated field) lost his sorting capability on a list view or on a list report when we have more than one language set on the system. By checking the dictionary entry, I was able to check only the English label has been created for the field and said so, you are only able to sort the column if your user language is in English.
As you can notice, the order of the records is not affected when I try to sort the column by ASC or DESC:
To solve the issue,
- Go to System Localization > Translated Name/Fields.
- Create an entry for each Risk Criteria (sn_risk_criteria) available according to your language.
- Voila, problem solved - try to use the sorting again, now you should be able to sort your columns.
Many thanks,
Raf
