Open baksale opened 4 years ago
Hi @clairebianchi Could you share reference for the problem with the other team?
Will they pick this ticket or will have a separate linked to the current one?
@baksale, I have sent this ticket to the PM and they should be taking a look and getting back to you
Hello @baksale I have also the same problem on CustomObjects also with my 2nd Gen package, when I Translate the Object name + Tab in french, and after that I create the package and install it to the target org, that translation will not appear on the CustomObject the installed with the package
Any Idea that could solve this problem, or this still an issue till now ?
This issue has been linked to a new work item: W-14424205
This is still an issue, but not an issue with CLI behavior or even packaging behavior. It's specific to the CustomObjectTranslation metadata type that is not being applied during package install. I've created a work item for the owning server side team to prioritize and fix.
Summary
Standard Object Translations are not applied through package installation
Steps To Reproduce:
Expected result
Account Tab is renamed to Client
Actual result
Account Tab is unchanged
Additional information
SFDX CLI Version(to find the version of the CLI engine run sfdx --version): sfdx-cli/7.27.0-714f62f9c1 win32-x64 node-v10.15.3 SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core) @oclif/plugin-commands 1.2.3 (core) @oclif/plugin-help 2.2.1 (core) @oclif/plugin-not-found 1.2.3 (core) @oclif/plugin-plugins 1.7.8 (core) @oclif/plugin-update 1.3.9 (core) @oclif/plugin-warn-if-update-available 1.7.0 (core) @oclif/plugin-which 1.0.3 (core) @salesforce/sfdx-trust 3.0.5 (core) analytics 1.2.1 (core) generator 1.1.1 (core) salesforcedx 46.17.0 (core) ├─ force-language-services 46.24.0 (core) └─ salesforce-alm 46.22.0 (core)
sfdx-cli 7.27.0 (core)
OS and version: Windows 7