-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sfdx force:source:retrieve into a new project fails to convert object translation #1233
Comments
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support. |
Hello, we get this issue with AccountContactRelation and OpportunityTeamMember as well as with one Vlocity object. |
This issue has been linked to a new work item: W-10028547 |
Hi @uwe-voellger @svenfinitiv this should be fixed in the |
@WillieRuemmele just updated to v7.125.0 and still getting the same error |
Updating to 7.126.0 does not help either: |
Same with 7.127.0 |
@WillieRuemmele still experiencing this as of |
Hi @frankpeleato what's the output of |
|
The fix is in the latest CLI release published today. sfdx version 7.133.0 |
Summary
We delete the source directory before retrieving to notice deleted artifacts. This never was an issue until recently, now an error is thrown.
Steps To Reproduce:
Repository to reproduce:
package.xml
custom field CallDate__c
Expected result
The custom field and its translation should have been retrieved into the force-app directory.
Actual result
An error message is displayed:
ERROR running force:source:retrieve: Metadata API request failed: Component conversion failed: Unexpected child metadata [.../test/force-app/main/default/objectTranslations/Activity-en_US/CallDate__c.fieldTranslation-meta.xml] found for parent type [CustomObjectTranslation]
System Information
Additional information
Noticed this behaviour in 7.121.8, tried rc to check if already fixed.
The text was updated successfully, but these errors were encountered: