With the Comparison date range option, you can choose how far back Gearset retrieves metadata changes from Salesforce.
By default, Gearset retrieves both recent and historical metadata changes.
Reducing the amount of historical metadata Gearset has to retrieve from Salesforce can significantly speed up comparison times.
You'll also end up with cleaner and more focused comparison results that will be quicker and easier to review.
Comparisons with date ranges applied will now only download and compare items within the selected date range, reducing comparison times.
How to set the comparison date range option
You can use the date range option with both comparison filters or On-demand comparison.
There are two place where you can set a comparison date range in Gearset.
1. On the Compare and deploy configuration page
Choose the last 7, 14 or 30 days worth of changes, or specify your own custom date range.
Select a custom or one of the default comparison filters, or On-demand comparison, and hit
Compare now
.
2. On the comparison results page
Set your date range first before choosing a comparison filter or comparing types manually.
Note: Make sure to set the date range first before starting your comparison. Otherwise, Gearset will use the "All time" setting by default, which will retrieve and compare both historic and recent changes.
Modifying date range in an existing comparison
You can modify the date range in an existing comparison. If you do, Gearset will start retrieving and comparing metadata for the updated date range.
If the comparison was run before today, Gearset will ask you if you'd like to extend the date range to "Today" or "All time".
Current limitations
The date range feature is only available with manual comparisons (run via Compare and deploy page), not CI jobs.
Gearset relies on the "Changed On" date from Salesforce being populated.
If an item is missing a "Changed On" date, which can occasionally happen for some metadata types, Gearset will retrieve and compare that item anyway. Read more on this here.Dependencies that were modified outside of your chosen date range won't typically be included.
Use the "All time" option to make sure all dependencies are also compared
Some deletions may not appear.
Deletions of items that were last modified outside of the date range may not always appear. This is because Gearset tracks when items are created and modified, but not deleted.
Again, we recommend switching to "All time" to view all deletions.