This extension consists of a tree view in the explorer to navigate through your sandbox metadata. There are several actions that can be applied to any given piece of metadata in order to read & modify the metadata in your sandbox.
This extension provides Sales Force Comerce Cloud (SFCC) developers with an alternate method for manipulating the metadata for system objects defined on a SFCC instance. There are several additional features in the works at this time, but this extension is still a bit rough around the edges.
If you find bugs, please log them to the github repository and I will do my best to fix. Issues on Github.com
Requirements for Use
Open Commerce API Access Setup
In order to make OCAPI calls to a SFCC instance you need to setup access to the desired API calls in Business Manager > Application > Site Development > Open Commerce API Settings. Currently this extension only uses the Data API, and access does not need to be setup for the Meta, or Shop APIs. The included example allows access to all resources, but could be modified only allow the calls that are needed.
Example OCAPI Access Config
Sandbox Connection Setup
SFCC Metadata Explorer requires that you have a dw.json file in the root of your SFCC workspace wich contains the connection information for your sandbox.
Example dw.json Config
The extension is currently setup to use the default OCAPI application ID & password:
A configuration option to use specific credentials could be added in the future.
Basic Tree View - View System Object Information
Context Menu : System Object : Implemented CRUD Operations
Context Menu : System Object : Implemented XML Operations
 dwupload: An npm package used to upload files to a SFCC sandbox from the command line.
The Icon for this extension is taken from the the Wikimedia Commons page here: File:Pictograms-nps-misc-scenic viewpoint.svg
This is a list of known issues that are results of incompatabilities, or limited scope of work. Issues / Bugs relating to the expected functionality of the extension can be foundon the github repository issues page.