In pre-Xanadu versions, translation records were incorrectly associated with parent tables instead of specific child tables. During upgrade to Xanadu or later, this causes duplicate entries in the sys_translated_text table. - Known Error

In pre-Xanadu versions, translation records were incorrectly associated with parent tables instead of specific child tables. During upgrade to Xanadu or later, this causes duplicate entries in the sys_translated_text table. Description Translations may become duplicated after an upgrade when they are defined for a parent table but used by its extended (child) tables. This typically occurs if the translation records are configured with the parent table name, leading to duplication during the upgrade process.

Steps to Reproduce

1. Log in to a pre-Xanadu version instance.

2. Activate any I18N language plugin (e.g., Japanese Translations plugin).

3. Verify translations are unique. Example: Use the following URL /sys_translated_text_list.do?sysparm_query=documentkey%3D88b7fa2a5323101034d1ddeeff7b12a5%5Efieldname%3Dname%5Elanguage%3Dja&sysparm_view=

4. Confirm there’s only one record per table

5. Upgrade the instance to Xanadu or a later version.

Expected Behavior:

No duplicate translation entries should be created during the upgrade.

Actual Behavior:

Duplicate entries appear in the sys_translated_text table for the same translation due to incorrect table association in earlier versions.

Workaround Duplicates can be removed using the fix script provided in the update set (PRB1807692_DuplicateTranslatedTextCleaner.xml).

To apply the fix:

1. Load the update set into the impacted instance.

2. Run the fix script named: DuplicateSysTranslatedTextCleanUp

The update set includes:

Fix Script: DuplicateSysTranslatedTextCleanUp Script Include: DuplicateTranslatedTextCleaner NOTE: Job status can be checked in the sys_trigger table (/sys_trigger_list.do?sysparm_query=nameSTARTSWITHCleanup%20Sys%20Translated%20Text%20-&sysparm_view=)