Org Model is the general name for the application within Elements that holds and organizes your Salesforce Org's metadata. Org Model can support different 'views' of metadata. This article covers how to navigate the metadata dictionary, which is the default way metadata is organized within Elements.
Article outline
Prerequisites
Metadata dictionary high-level structure
Object structure
Managed packages structure
Prerequisites
In order to use this feature you will need:
A synced Org model
Metadata dictionary high-level structure
Metadata dictionary is a hierarchical list of metadata from your Salesforce Org. The hierarchy, for the most part, is very straightforward. The top-level of the tree are just the different 'types' of metadata that you have in your Org, as seen below.
If you do not have a specific type of metadata in your Org (e.g. apex classes or apex triggers in the example above), then those types will not be listed.
By clicking on the little triangle, you open the child components that belong to that type.
Object structure
Objects are grouped hierarchically into types and then listed alphabetically. The list of objects does not include managed package objects (scroll down to read about managed packages).
Metadata types that belong to an object (e.g. record types, fields, field sets, list views) or that are tied to a single object by design (e.g. approval process, process builder workflows etc.) are listed under a given object.
Managed package structure
Managed Packages installed in the Org can be found at the bottom of the metadata dictionary top-level list. All components, including objects, that come from a managed package are listed under a given managed package.
