The Org Browser displays the available metadata types and their corresponding components in your default org. This feature makes it easier and simpler to retrieve metadata source, without having to use a manifest file. The Org Browser is available only in non-scratch orgs such as sandboxes or dev orgs.
Opening the Org Browser
- Open Org Browser
- Refresh available metadata types in the org
- Default org
- Metadata type
- Metadata component
- Refresh components for metadata type
- Retrieve source for metadata component
To open the Org Browser, click the cloud icon in the side bar of the VS Code window (1). If you don’t see the icon, make sure your default org is set to a non-scratch org.
When you open the Org Browser, all the metadata for the default org is saved in your local project under the .sfdx directory to minimize the number of calls to the org.
Listing and Refreshing Metadata
The Org Browser lists all the metadata types (4) in your default org. To view the components (5), expand the metadata type. When you expand metadata types with folders such as Reports, Dashboards, Documents, and EmailTemplates, all the available folders are displayed. You can view the components in a folder by expanding it.
You can refresh metadata at org level, for a type, for folders in a type, and for components in a folder. Click refresh icon next to:
- Org Browser (2) to refresh available metadata types in the org
- metadata type (6) to get an updated list of components for the type
- folder metadata type to update the folders in the type, but not the components in the folder
- folder in a metadata type to refresh the components in it
You can retrieve a component to your local project by clicking the retrieve button (7) next to the component name. Currently, the component is retrieved into your default package directory, which is defined in the sfdx-project.json file.
You can also retrieve multiple components from the default org by clicking the retrieve button next to the metadata type. If retrieving a component overwrites it, you’ll be prompted to select how to proceed.
When you retrieve components for a metadata type, the Org Browser automatically refreshes the component list for the selected type and then retrieves them. This ensures that the extensions accurately check the local workspace for existing components.
Because of the asynchronous nature of the Metadata API calls, a simultaneous deploy and retrieve could potentially lead to a race condition. To prevent retrieving unexpected components, be mindful of using the Org Browser while a deploy operation is in progress.