FAQ: Migrating Translations
- How do I know which migratable Implementation Types contain translatable fields?
- You can view these reports:
- The tenantedObject Transporter Supported Objects (OX)report in Workday.It includes information about translatable and migratable fields. To view the report, you must have access to theOX for Non Implementersdomain in the Implementation functional area.
- TheTranslatable Tenant Classes and Ref ID Indexesreport in the Translations Hub.It includes information about what you can translate in your tenant. To view the report, you must have access to theData Translationdomain in the System functional area.
- Why don’t I see translations included in my migration?
- You might be migrating a nontranslatable object. Not all objects in Workday are available for translation. To verify that your object is translatable, access theObject Transporter Supported Objects (OX) reportin Workday.
- Why are some translation values for my object missing from the Attribute Diff report?
- You might not have enabled the relevant languages in your target tenant. Object Transporter only migrates translated values for languages that you enable in the target tenant. Access theEdit Tenant Setup - Globalreport to verify that the correct languages are enabled for your target tenant. To view the report, you must have access to theSet Up: Tenant Setup - Globaldomain in the System functional area.
- How do I prevent translations from migrating?
- There are several ways to prevent Object Transporter from migrating translation values:
- During a migration workflow, clear the Include Translations? check box.
- To stop Object Transporter from migrating translations for a particular language, disable the language in your target tenant. You must have access to theSet Up: Tenant Setup - Globaldomain in the System functional area.
- Why aren't my translation-only updates applying to an existing object in the target tenant?
- Object Transporter doesn’t apply updates if a translation is the only modification made to an already existing object.If you encounter this issue, we recommend that you manually update the translated values directly in the target tenant