Dashboards within folders are not retrieved from Dashboard node in Org Browser
See original GitHub issueSummary
Short summary of what is going on or to provide context. I do have an org with different dashboards organized thru folders: Executive, Sales, Deployment, Adoption, etc. If I want to retrieve all of them using Org Browser’s cloud-icon, I have to do it one by one (dashboard by dashboard) when ideally, I just want to click the cloud-icon at dashboard node level and retrieve all folders and dashboards.
I think the problem is related to an underlying cause with Org Browser when click over the dashboard node and it executes:
sfdx force:source:retrieve -m Dashboard
it returns:
=== Retrieved Source No results found
However, if I open the folder nodes and click on the cloud icon on single items it retrieves correctly:
sfdx force:source:retrieve -m Dashboard:EjecutivoNivel2/cIVVkXSlzqSBCKNXcUMXlSDkoqeBdW21
returns:
DashboardSalesforce/FdYlfQCcdVGBpMrJSMhZROdVyvFMbd Dashboard force-app/main/default/dashboards/DashboardSalesforce/FdYlfQCcdVGBpMrJSMhZROdVyvFMbd.dashboard-meta.xml
Steps To Reproduce:
- Using a DE org (or non scratch), create a Dashboard Folder: “sales”
- Create different dashboards within the “sales” folder.
- Connect VSCode to the org from first step
- Open Org Browser and click on cloud icon at “Dashboards” node
- No dashboard or folder is retrieved
Expected result
Describe what should have happened. The Org Browser should download the folder “sales” and all its dashboards to my local file system.
Actual result
No files are retrieved to local file system. A “No results found” message is displayed
Additional information
Feel free to attach a screenshot.
VS Code Version: 1.42.1 c47d83b293181d9be64f27ff093689e8e7aed054 Date: 2020-02-11T14:44:27.652Z
SFDX CLI Version: 7.48.0-a71f8c6899
OS and version: OSX Catalina 10.15.3
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:10 (2 by maintainers)
Top GitHub Comments
Same behavior with Reports
This issue has been automatically closed because there has been no response to our request for more information from the original author. Currently, there is not enough information provided for us to take action. Please reply and reopen this issue if you need additional assistance.