Search
-
Gearset to do Sanbox Refresh by copying metadata and data from production
-
extend the GearSet public API to include Data deployments between Sandboxes and Scratch Orgs
-
Ability to filter records on field "ischanged" when doing a data backup comparison.
-
Add option to make picklist fields non-restricted before performing a data deployment
-
Resolve "Data Owner" User metadata from difference comparisons (always exclude or compare, then exclude) · Completed
-
Enhance XML meta data comparison to ignore changes in XML order · Completed
-
Ignore changes deployed to orgs from Gearset in Data Monitoring jobs
-
Add the ability to export Success and Error logs for Data Deployments · Completed
-
Create a Data Deployment Template for migrating Territory Management (1.0 & 2.0)
-
have functionality to show how big a data deployment is going to be when deploying, as some Salesforce sandboxes have a limit of 1GB
-
When an Installed Package is installed via GS permission sets with View/Edit All Data system permission don't automatically get updated
-
Allow retention policies to be set on individual core objects
-
Modify the "Changed On" drop down filter groupings to round to the nearest day, rather than the exact time the change was made.
-
A count of differences could be grouped by type
-
Summary pages should always include ALL changed files
-
backup expiration
-
Combine multiple daily monitoring results into a single deployment
-
Integrate with Salesforce's Setup Audit Trail for Metadata Detection
-
Ability to turn rules/processes off as needed with ability to rollback
-
Expand the options for "Run job" times on the continuous integration job setup.