Closed JodieM closed 11 months 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.
This issue has been linked to a new work item: W-13948754
Is there any update or workaround for this issue please? I really need to be able to retrieve something from a scratch org. I am currently setting up my third demo scratch org from scratch due to this issue.
I can tell you that the flow you describe absolutely works from the CLI. We have many tests that prove this basic functionality before any changes are made to the CLI plugins and libraries. That said, the video you linked (thank you for that) is mostly from VS Code, so you may want to uninstall VS Code and reinstall. Before you do that though, what you are seeing may be due to targeting the wrong org. If you make changes in a different org then pull (or retrieve) it won't find anything. You can explicitly target the org you want to retrieve from using the CLI (--target-org
flag). If the SourceMember query you are running works, then the pull should also work since it runs that same query to build the manifest that it uses for the retrieve.
It might be worth doing your flow only using the CLI from a shell to see if it reproduces. If it doesn't, then I'd suspect something is messed up in VS Code extensions.
OK explicitly setting the org worked and I was able to retrieve, however, I've always created my scratch orgs as the default, only usually have one scratch org on the go, and it's showing in the bottom left hand corner of VSCode as the default. I've followed the steps here https://trailhead.salesforce.com/content/learn/projects/quick-start-salesforce-dx/create-and-test-our-scratch-org and their deploy command doesn't set an org explicitly so I wonder what has changed in the new SF commands that you have to set the org?
If you're creating multiple scratch orgs and defaults, it might be replacing 1 default with another. You can check the default (from the CLI) with sf config list
. It appears that the mix of VS Code actions and CLI commands with multiple scratch orgs might be causing some confusion. New sf CLI commands work the same way as sfdx CLI commands w.r.t how default orgs are applied.
Here is your problem: https://github.com/SFDO-Community/Salesforce-Indicators/blob/main/.forceignore#L22
You can't forceignore **/unpackaged/**
or everything from a retrieve will be ignored because that's the directory within the retrieved zip file that all unpackaged metadata goes. E.g., unpackaged/flexipages/Lead_Record_Page
If you comment that entry or remove it, then do your retrieve it works.
Maybe we can add a warning when parsing the .forceignore file if we see something like that.
Summary
running sf retrieve start does not retrieve anything. downloading anything from the org browser does not download anything, but no errors.
Steps To Reproduce
See Video here https://www.loom.com/share/97391521912641a39875a21272162f9f?sid=cf8e0d08-ffc1-4d64-8e7b-a6be12ae47a8 Basic steps
Expected result
I expect any changes made in the org will be retrieved from the org
Actual result
nothing is retrieved.
Troubleshooting:
sf project retrieve start --source-dir force-app --target-metadata-dir output --unzip
Select Id, MemberIdOrName, MemberName, MemberType, RevisionNum from SourceMember
works and retrieves the following (edited for clarity)System Information
Powershell Windows 11
Additional information
doctor command output