Transcript
When you run a comparison, Gearset will show you the metadata differences between your source and target. Along the top bar, you'll see what changes have been made, when they were made, and by who.
Here are a few ways to explore the comparisons.
First, you can search for specific metadata types and pick from this sidebar. If you forget to add a metadata type, just search for it and Giset will retrieve it from your orgs.
Along the top of your screen, you'll see a few options to help refine your comparison even further. You can choose new items to pick out changes that are in your source environment but not in your target.
Changed, this will show you items that are in both source and target, but there are differences between them. And deleted, This will show you items that are present in your target environment, but not in your source.
By using the global search bar, you can hone in and look for specific changes.
Once you've selected an item, you'll see a breakdown of the XML in both your source and target at the bottom of the page.
Next to each item, there's a little chevron. Clicking this will open a drop down menu for you to see dependencies, items it's used by, and any related profiles and permissions.
It can be easy to miss this, so Gearset has a safeguard in place to help you here, providing you've selected these metadata types as part of your filter. So let's say you forget to include one or all of these nested items. And as you move through your deployment steps, GearSets problem analyzers will flag them to you in issues and automatic fixes.
Here, you can select to include all of the nested dependencies and associated profiles and permissions.
If you'd like to learn more about exploring comparison results, click on this link.
