Skip to content

Search

← Gearset
(thinking…)
Reset
  • All (353)
  • Articles (0)
  • Ideas (353)

    1. extend the GearSet public API to include Data deployments between Sandboxes and Scratch Orgs

    2. Download Salesforce customer master data changes for a custom time period in a single file

    3. Add option to make picklist fields non-restricted before performing a data deployment

    4. Resolve "Data Owner" User metadata from difference comparisons (always exclude or compare, then exclude)  ·  Completed

    5. Enhance XML meta data comparison to ignore changes in XML order  ·  Completed

    6. Allow OR operator at the top-level of object data filtering

    7. Allow to export the data of an object or multiple objects for a specified time period

    8. Ignore changes deployed to orgs from Gearset in Data Monitoring jobs

    9. Enable use of multiple parent filters under 'Filter using parent object' in data deploys

    10. Don't mark data deployment as successful if some records were excluded due to invalid picklist values

    11. Add the ability to export Success and Error logs for Data Deployments  ·  Completed

    12. Create a Data Deployment Template for migrating Territory Management (1.0 & 2.0)

    13. Show how big a data deployment is going to be when deploying, as some Salesforce sandboxes have a limit of 1GB

    14. During Data Deployments, allow us to relate records to the User using an External ID instead of the Email and Profile.Name.

    15. When an Installed Package is installed via GS permission sets with View/Edit All Data system permission don't automatically get updated

    16. Ability it use SOQL to provide complex filters on Vlocity and Salesforce Metadata types to create custom Compare & Deploy Filters

    17. Allow retention policies to be set on individual core objects

    18. Make the commit hash clickable in Pipeline PR Commits tab

    19. Modify the "Changed On" drop down filter groupings to round to the nearest day, rather than the exact time the change was made.

    20. Summary pages should always include ALL changed files

    1 2 … 5 7 9 … 17 18