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

[sachinvic]

@CCPhilStone 

Thanks for confirming. Since the translations are stored in sys_translated and you have already cleared the cache and retested, raising a ServiceNow case makes sense here.

The DEV/TEST behavior can then be investigated to determine why the translated values are not being picked up after the update set migration.

[Ankur Bawiskar]

@CCPhilStone 

were those captured in your update sets?

if not then did you migrate those via XML?

if yes and still not working then better raise case with ServiceNow

[CCPhilStone · Accepted solution]

Turned out to be poor documentation. An update set with a fix for a Client Catalog Script had been missed from the list of update sets to apply.

Once that update was moved to TEST and committed it all worked.