You can use Elements org model to slice and dice your Salesforce metadata however you want. You can create custom, configurable, and pre-filtered list views with ability to take mass-actions on selected metadata.
How to create a list view?
You will need:
Paid Elements License:
This capability is not supported on legacy PRO license
Consultants have access to the capability as part of their consulting license
How to create a list view?
As a user with edit rights on the org model, click on the 'Metadata dictionary' dropdown.
Click to create a new list view. Give it a name and select which metadata types you want to include in the view (this will impact what attributes are available to choose)
Select attributes you want to see as columns by dragging and dropping them from the left column to the right column. You can re-order the attributes in the right column from top to bottom which will impact the order of columns from left to right in the view.
Select filters to apply across all metadata of the selected types. You can only choose to filter metadata by attributes that will be used as columns. Confirm choice.
List view access
There can be up to 15 custom views of metadata present in an Org model at a time. If you want more, you will need to delete one of the existing views.
List views are shared by everyone in the Org model. The view you create will be visible to other users with access to the Org model.
What attributes are supported for columns and filters?
The following attributes are currently supported to be used as columns and filters. However which of these will appear as selectable columns will depend on which metadata types were chosen to be included. For instance, if you want a view with just Flows, you will not see attributes specific to Objects or Fields, available in the column selection.
Full API name (correct Developer name)
Full path (Elements-specific attribute which specifies the path to the component in the Org model tree)
Type (Salesforce metadata type)
Active: true or false
Flow fault coverage
Subtype (used for flows and fields)
Trigger type (used for flows and apex triggers)
Asynchronous run: true or false
Immediate run: true or false
Apex test coverage
Status (status of the component since last sync, can be 'New', 'Updated', 'Deleted', or 'Proposed')
Last report run date
Last modified record date (date when record was last updated on an object)
Last created record date (date when record was last created on an object)
Created date (when metadata component was created)
Last modified date
Last modified by
Record count for objects
Assigned users: number (for Profiles, Permission sets and groups, Roles, Queues, Groups)
Base object for report type
For objects: number of:
Buttons, Links and Actions
Total complexity (for Flows and Apex classes)
Complexity score level (for Flows and Apex classes)
For fields only:
Length (integer) - cannot filter by it yet, only display
Data sensitivity (string)
Compliance group (string)
Data owner (string)
Business status (string)
Encryption scheme (string)
Also, the following attributes can be used in filtering:
Parent managed package
You can multi-select/bulk-select components in a custom view and perform bulk operations. You need to right-click on the grid to open the context menu.
Mass-replace tags: replaces all existing tags with new tags
Mass-add tags: adds selected tags to new tags
Mass-add to story
Create story per node
You can click on the download icon and choose 'Listed metadata' option. This will generate a CSV file with the selected columns and a full set of metadata matching your filter criteria that can download.
Any user with view edit rights to the Org model can download the CSV file of the generated view.
In order to edit any aspect of the generated view or delete it, the user with org model edit rights just needs to hover over the view from the dropdown and choose one of the available options.
By selecting "Edit sorting" you can change the sorting order of the columns in your grid view. This can be changed at any time. We allow you to sort columns by number, date, or alphabetical order, according to the data type.