sys_translated values moved in update set not working after being committed

[CCPhilStone]

Created some translated text values for choices on a record producer variable, which were captured in an update set and which work in the DEV environment. As the record producer is in the 'Employee Centre Core' scope, so are the translated values.

The update set was moved to the TEST environment and successfully committed. However after changing the language the choice values still appear in English, rather than the preferred language.

Any ideas why the translated values are not showing?
 

This is on Australia patch2-04-17-2026

[Ankur Bawiskar]

@CCPhilStone 

did you try to clear instance cache using cache.do and then logout and login again?

could be due to this

Translations [sys_translated_text] entries are not moving when importing customization changes from ... 

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[boteeuwen]

I would check sys_translated_text in both DEV and TEST and filter on table = question_choice. Then compare the records for the required language and make sure the translated labels are present in TEST.

If the records exist in DEV but are missing in TEST, then they were likely not moved correctly with the update set. If they are present in both, compare the Field, Language and value to make sure they match.

That should help narrow down whether this is a deployment issue or an issue with the translation records themselves.

[sachinvic]

@CCPhilStone 

Hi,

The two checks mentioned above are worth trying. I would check them in this order:

1. First, compare the translated value in DEV vs TEST under Translated Text [sys_translated_text]. For a Question Choice, verify the Language, Table Name (question_choice), Field Name (text), Document, and Value.
2. If the translation record is present in TEST, run cache.do and test the Record Producer again using the target language.
3. If the record is missing in TEST, check the update set preview/XML to confirm whether the translation was included. If it wasn't, move the required translation record separately rather than changing the sys_translated_text dictionary configuration.

This will quickly tell you whether the issue is translation data not being migrated or simply cached translation data.

ServiceNow documents sys_translated_text as the table used for translated text values, and Question Choice translations specifically use this mechanism.

FYR:

https://www.servicenow.com/docs/r/platform-administration/system-localization/c_UseTranslatedText.ht...