Custom Object Translations in source format omit help text, labels, etc. that mdapi format includes #2830
Labels
bug
Issue or pull request that identifies or fixes a bug
investigating
We're actively investigating this issue
validated
Version information for this issue has been validated
Summary
Custom Object Translations include help text, labels, picklist values, etc. as comments when retrieved via metadata API, but omit that info when retrieved in source format via
sf project retrieve start
. (Converting to source format viasf project convert mdapi
also strips out that info.)Is this behavior intentional or a bug? It's a problem because I want my source files to match what's retrieved by other tools using the metadata API such as Gearset.
Steps To Reproduce
sf project retrieve start --manifest package.xml --target-metadata-dir temp-mdapi --unzip
sf project retrieve start --manifest package.xml
Expected result
Content of Custom Object Translations matches, whether represented in mdapi format or source format.
Actual result
Unpackaged mdapi format file
temp-mdapi/unpackaged/unpackaged/objectTranslations/Contact-en_US.objectTranslation
includes help text, labels, picklist values, etc. as comments, like this:(The above matches what is retrieved by other tools like Workbench, Gearset, etc.)
Decomposed source file
force-app/main/default/objectTranslations/Contact-en_US/Example__c.fieldTranslation-meta.xml
omits the labels, help text, etc., like this:System Information
Shell: zsh
The text was updated successfully, but these errors were encountered: