Closed nickwick76 closed 2 years ago
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.
Just chiming in to say that I've experienced a similar issue. I'm working on a project where some objects have a list view and record type with the same developer name. sfdx force:source:retrieve
puts the retrieved recordType-meta.xml
file in the object's listViews
directory.
This issue has been linked to a new work item: W-8907032
Seems the same issue as: #602
Check out the new beta source commands which should fix this issue!
@WillieRuemmele I am having this same issue; I am using the beta source commands as suggested:
$ sfdx which force:source:retrieve === force:source:retrieve plugin: @salesforce/plugin-source
I'm still getting my Opportunity RecordType metadata nested within BusinessProcesses. I am retrieving via package.xml
fixed for push
in the upcoming version.
Summary
Note, this one is similar to issue #579 , which I also experience.
If you have a business process on Opportunity or Case and also have record types with the same name as the business process, then the record types end up in the business process folder when retrieving it with the CLI. This has been verified with VSCode, IntelliJ and CLI standalone. If you make a change to the record type in the IDE and deploy it, then it gets correctly deployed to the org. But if you make a change in the org and retrieve, the updated recordtype is the one in the business process folder.
Steps To Reproduce:
Package.xml `<?xml version="1.0" encoding="UTF-8" standalone="yes"?>