Loading...
Loading...
Translations [sys_translated_text] entries are not moving when importing customization changes from source control or via update sets. Steps to Reproduce 1) Create a record producer in scope Human Resources: Core. 2) Confirm the RP XML and the sys_translated_text table have entries for the RP name, Short Description and description. 3) Go to Studio - select Human Resources: Core - Source Control - Commit Changes o Select relevant ones and submit 4) Go to another instance 5) Go to studio - select Human Resources: Core - Apply remote changes to reset the app - Change branch to newest one (latest date) - Wait for the branch change to terminate. 6) Then go to sys_translated_text and try to find the records with the sysIDs in the highlighted section, for example f8cb4ddd93859a90b5b3f4ed1dba1087. Expected Outcome: A record is found and when viewing the Item of the portal in French, all text is displayed in French. Workaround 1. Workaround is to manually load the missing sys_translated_text records 2. In some cases it may be needed to add the "serializer=com.glide.script.TranslatedTextXMLSerializer" attribute to a custom translated html field in order for the translation to be captured as customization (sys_update_xml).
PRB1823337
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.