Workaround for translation overwritten by store apps Description This article provides an overview of how to troubleshoot a store app translation overwriting the equivalent language plugin entry. Since store apps contain their own translations, their translations may overwrite pre-existing translations. Resolution Workaround #1 - Repair language plugins to overwrite the translation tables with OOB. Workaround #2 – You can modify a particular translation to suit your specific need. When editing a small number of translations, you can do so directly in the translation tables by opening the records and updating the translation to your desired term/phrase. For multiple translations, you may want to accomplish this using an import set. Modifying a translation will create a corresponding record in the sys_update_xml table which will preserve the translation from being overwritten by a future plugin install or upgrade. Please refer the following link for how to customize the translations using an import set; https://docs.servicenow.com/bundle/washingtondc-platform-administration/page/administer/localization/task/t_TranslateTheInterface.html If you prefer to rely on the Out of the box translations delivered as part of a language plugin or store app and have previously modified a translation, you will need to remove the record which tracks the customization, from the sys_update_xml table before the version that should fix the text gets installed. This would overwrite the customized translation with the latest OOTB translation. Please also make sure to raise a case ticket in case you see an unexpected translation so that we will implement the fix to the upcoming release. Note: any updates made on sys_translated_text records preserve all the changes in one update history in sys_update_xml. If one is deleted to apply fixed OOTB, the other changes might need to be implemented again.