How to handle Translations changes in Upgrade
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi everyone,
I wanted to know for a developer who do the upgrade servcienow is there a way to handle Translations changes and not accept the Upgrade changes in the translation before it applies? in a best and good way using servicenow, our problem last year for Zurich is that we did the upgrade and we checked Translation differences by using excel files after uplaoding raw files of all trad tables and apps and modules tables to compare is there a way to do that before hands like when servicenow ask us if we skip or retain some scripts or widgets etc for Translation he never asks if we keep our translation or if he change it and that make us do lots of works that seems for me dumb
Thanks if you have a goob methods best practices for that or a link to offical documentation for this matter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
The best practice is to manage translations outside the upgrade process—use the Update Set mechanism or Scoped Apps to preserve your custom translations, then re‑import them after the upgrade. ServiceNow doesn’t prompt for translation conflicts like it does for scripts, so maintaining a controlled export/import process or using the Localization Framework is the recommended way to avoid manual Excel comparisons.
