Search
-
extend the GearSet public API to include Data deployments between Sandboxes and Scratch Orgs
-
Download Salesforce customer master data changes for a custom time period in a single file
-
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
-
Allow OR operator at the top-level of object data filtering
-
Ignore changes deployed to orgs from Gearset in Data Monitoring jobs
-
Allow to export the data of an object or multiple objects for a specified time period
-
Enable use of multiple parent filters under 'Filter using parent object' in data deploys
-
Don't mark data deployment as successful if some records were excluded due to invalid picklist values
-
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)
-
Show how big a data deployment is going to be when deploying, as some Salesforce sandboxes have a limit of 1GB
-
During Data Deployments, allow us to relate records to the User using an External ID instead of the Email and Profile.Name.
-
When an Installed Package is installed via GS permission sets with View/Edit All Data system permission don't automatically get updated
-
Ability it use SOQL to provide complex filters on Vlocity and Salesforce Metadata types to create custom Compare & Deploy Filters
-
Integrate with Salesforce's Setup Audit Trail for Metadata Detection
-
Audit changes to the "Require issue tracking" setting
-
Ability to turn rules/processes off as needed with ability to rollback
-
Audit changes to the "Require issue tracking" setting