- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2025 05:56 PM
Dears,
Kindly could you provide your insights regarding what to expect on installation of a translations plugin (Arabic Language) when the instance already contains thousands of translation records across all localization tables (translated text, ui messages, documentation, choices, etc.) ?
Does the plugin installation overwrite pre-existing records, or does it preserve the current versions and skip conflicting entries from the package
Thanks in advance.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-24-2025 04:47 AM
Hello Mark,
It's simple actually, you can create a language record and create a choice for language selection.
So we applied this in our instance because the Arabic translations package hadn't been released yet back then.
https://www.servicenow.com/docs/bundle/yokohama-platform-administration/page/administer/localization...
https://www.servicenow.com/docs/bundle/yokohama-platform-administration/page/administer/localization...
Anyway, I reproduced the exact same case on a developer instance and found that i18n language plugins installation (for an existing language record) skips all conflicts keeping the old translations as they are.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2025 04:37 AM
That's because of the different sys_ids on the records. You will, however, have duplicate translations in the system and need to disable the ones you don't want, because otherwise the system is going to decide which key/translation to use.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
