Comparison Views are like List Views for Metadata deployments. They provide a personalized view of metadata designed to help identify specific types of metadata components to load and compare values between the source and destination. They can be created and modified for specific types of changes and can increase the performance of loading the metadata by focusing on just a few metadata component types. For example, Prodly provides a comparison view for “Objects, Flows and Workflow Rules” which would load and compare just these metadata component types, thus excluding large tables like Profiles or Email Templates.
View Available Comparison Views
- Navigate to the Comparison Views tab in App Navigator
- Create a new List View to show all Comparison Views. You should see the following Comparison Views:
- Objects, Flows and Workflow Rules
- Object, Flows, Workflow Rules, Permission Sets, and Profiles
- Objects, Permission Sets, and Profiles
Create a New Comparison View
- Click New.
- Add a descriptive Comparison View Name.
- Check the Active checkbox.
- Click Save.
Add Comparison View Rules to Filter Metadata Components
Comparison View Rule Logic applies “Or” conditions between different parent rules. For example, you might have one rule to include a Namespace and another rule to include all custom objects in the Org.
- Navigate to the Related tab on the Comparison Views detail page.
- Click New to create a new Comparison View Rule.
- Set Action to Include or Exclude.
- Select a Filter Type.
- Add a Filter Value. Filter values will vary by the Component Type. See examples below.
Filter Value Examples
This filter is used to select a metadata component type. For example, Custom Object, Flow, or Workflow Rules. To support all 3, one would create three rules in the comparison view, one for each metadata component type. The following are supported filter values:
This filter is used to select a specific component to be included. For example, Account or Quote. To use this type, a parent Rule with a Namespace or Component Type is required. For example, one could create a parent rule to filter Component Type and Filter Value CustomObject and a child Comparison View Rule with a filter of Component Name and Filter Value SBQQ__Quote__c.
This filter is used to narrow the components to just those in a specific application namespace. For example, a filter value of SBQQ would filter the metadata to just those components with this suffix.