- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-12-2023 02:29 PM
In this article by @Mark Roethof we learn how to set up and use the new Multi-lingual notification support. I've got a need to be able to translate the Name of the notification in addition to the subject, body, etc. of the notification. Is there any guidance available on how you can have a localized version of that Name so that when someone looks at Notification Preferences, they can see the Name of the notification in their preferred language?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2023 01:41 AM
@Don Conley,
So ootb, indeed the notification names are not translatable, as can be seen when I look at the preferences modal you'll see there's no prefix:
This is indeed because as @Mark Roethof states, it's a string field:
But.... that doesn't mean it can't be translated. To make it so, you would need to change the field type - which yes would be a type of customization but one we're unlikely to do ootb (for various reasons),
You can change any "string" type field to "translated_text", which is another type of string field but has the benefit of being translatable. The translations for these would reside in the [sys_translated_text] table.
- To learn more about the 5 tables, check out my blog post here on them.
When done correctly, the field should look like this:
^ Note the attribute - this should be auto-applied if you save the change of the field type change.
If we now check back on the notifications preference, we can now see that they are translatable:
Many thanks,
kind regards
Director of Globalization Deployment, Internationalization

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-12-2023 09:08 PM
Hi there,
The name of a Notification is just a string field. It's not translatable. So I would say no go at this moment.
You could try raising a Support case for this to get an official answer, though most likely you will get a response like you can raise an enhancement request / idea on the idea portal.
Kind regards,
Mark
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
10x ServiceNow MVP
---
~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2023 01:41 AM
@Don Conley,
So ootb, indeed the notification names are not translatable, as can be seen when I look at the preferences modal you'll see there's no prefix:
This is indeed because as @Mark Roethof states, it's a string field:
But.... that doesn't mean it can't be translated. To make it so, you would need to change the field type - which yes would be a type of customization but one we're unlikely to do ootb (for various reasons),
You can change any "string" type field to "translated_text", which is another type of string field but has the benefit of being translatable. The translations for these would reside in the [sys_translated_text] table.
- To learn more about the 5 tables, check out my blog post here on them.
When done correctly, the field should look like this:
^ Note the attribute - this should be auto-applied if you save the change of the field type change.
If we now check back on the notifications preference, we can now see that they are translatable:
Many thanks,
kind regards
Director of Globalization Deployment, Internationalization
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2023 05:59 AM
Great information! Thank you @Alex Coope - SN