Hello community,
I'm working on translating the screen components of our flow in a sandbox using translation workbench.
When we deploy the latest active flow version from sandbox to Production all the translations for different countries are lost.
In the sandbox we have a bigger version number, e.g. version 20 (due to many adaptions) -> in Production we only have flow version 4.
Do the version numbers of flow in sandbox and production have to be the same that the translation metadata gets also deployed to production?
My question would be: How can we enforce best that all the flow translations from sandbox can be deployed to production?
Thank you for your help!
Best Regards
Morten
Hi @Morten Stockey! I faced the same issue with Flow translation and deployment via SFDX. And I see similar discussion about deployment via ChangeSet: https://trailblazer.salesforce.com/issues_view?id=a1p3A000000BNJ0QAO
Workaround 1. Replace all flow messages with Custom Labels. Labels have no version, so translation for them can be exported/imported successfully. But I'm not sure if it fits Field Service.
Workaround 2. Replace flow versions in exported XLIFF files to make them the same as versions of active flow in production. It can be done with some script or manually.
Flow deployed via SFDX doesn't inherit translations from the previous flow version, at least for now (Summer 21, API version 52). The surprising thing is the different behavior in Flow Builder: flow edited in Flow Builder inherits translation from the previous version.
