Help us improve Gearset

Welcome to the Gearset feedback forum. We love getting feedback from our users on how we can make Gearset even better.

Post your ideas and vote for others – let us know what’s important to you. We’re keen to hear about product improvements, new features, and bug fixes alike. We check this forum regularly and will keep ideas updated with their current status. If you need any further support, please contact us at team@gearset.com.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Allow components to be added or removed from an data deployment template

    Currently when a data deployment template is created, there is no way to edit the template after it is saved so that components can be added or removed. It would be helpful if we could modify the components in the template without having to create the template from scratch again.

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Support user record migration from production to sandbox or scratch orgs

    New users are often created in the production org that need to be monitored and brought back to sandboxes as well. It would be great if the data deployment tool could support moving user records from prod to sandboxes or scratch orgs.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support Salesforce standard Country/State Picklist Mapping for Data Masking

    Right now, using the data masking feature for data deployments, the values for country and state are real values and random. There's no guarrantee that the country and state will be valid pairings.

    This causes issues for orgs that use the standard Country/State picklists from Salesforce.

    The goal would be that the masking feature would pull from the Saleforce default values and make sure that the state and country are valid pairings as opposed to randomizing both separately

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  4. Deploy data from local repository.

    It would be very helpful if we could deploy data from a local repository. We have different namespaces for internal packages and it would make data migration significantly easier if we could do it from a local machine where we'd switch the namespaces.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  5. Compare and Deploy Attachments and Files

    Please add the ability to use the "Compare and Deploy" for Attachments and Files. The ability to migrate PDFs, image files, word docs, and excel spreadsheets would be GREATLY appreciated! Thanks!

    16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add Support for Pre/Post Data Deployment Scripts

    Some of my more complex data objects require that I turn off Validation Rules during deployment, then back on again after deployment.

    Options that would work:

    • BEST: List of Validation rules under each object and and option to temporarily disable on a one-by-one basis during the deployment. A "Disable All Validation Rules During Deployment" option would be helpful if this feature is implemented.

    • BETTER: Ability to specify metadata xml to apply to each sobject pre and post deployment.

    • GOOD: Ability to specify anonymous Apex to execute pre and post deployment. This would involve a callout to the Metadata API, which…

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  7. Ability to update value of Reference field for a data deployment

    "Select reference fields to deploy"

    Ability to edit the value for the target deployment data for the reference field instead of searching for the match on the Target.

    Ex. Loading Opportunities from a Source to a Target that contains 5 different record types, but when uploaded to the Target we specify the recordtypeid to one that matches a recordtypeid on the Target for the entire data load.

    Similar to how the Owner reference can ignore the Target's users and default to the running user of the data deployment.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Allow complex filters and child relationships on filters for data loading

    Allow complex filters and child relationships on filters for data loading. For example, filter the Account to only load if the Owner is an Active user in the system.

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  9. Schedule data deployments

    The current data deployment functionality works fine for one-off deployments, but if you are trying to keep specific data in sync across multiple orgs, the ability to schedule data deployments for a given time in the future would let you deploy on a recurring basis automatically. Becomes especially helpful when combined with the current data filtering options.

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  10. Migrate audit fields during a data deployment

    When deploying data records, it would be helpful if audit fields values could be migrated

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  11. Preserve auto-number field values during a data deployment

    Staging environments typically exist with integrations with other systems that have references to auto-number fields
    Data deployment re-evaluates auto-number fields instead of keeping the values of the source.

    If data deployment jobs could automate the following it would probably work
    1. changing the type of the auto-number field to text in the target org
    2. potentially removing apex references to the field
    3. deploying the data
    4. rolling back metadata modifications in steps 1 and 2

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  12. Allow record id as the first criteria for matching lookup fields

    When deploying data records from production to sandbox, the default matching criteria for the owner field will not typically work...

    Gearset currently matches on email and profile, but the email addresses for users get modified in sandboxes. So, no match is found for users other than the one who created the sandbox.

    It would be great if the first check was: does the user record id match. If not, use email + profile, if not, use the current user.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  13. Add problem analyzers to the data deployment app

    Much like the problem analyzers for metadata deployments in Gearset, it would be great if you could add a problem analysis feature for data deployments after having configured what you want to deploy.

    Some scenarios will almost certainly cause the data deployment to either totally fail or only partially deploy some of the records and skip records it can't deploy. Providing automatic fixes (e.g. choosing not to include duplicates) would improve the number of deployments that work 100% of the time.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  14. Delete records from the target org during a data deployment

    Provide options to delete records from Target Org. This will help clean up of test data and reload from Source.

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  15. Select all objects in a data deployment

    It would be useful to select all objects in the data deploy screen to make it faster to select a large number of objects (even better would be the ability to group objects and select whole groups at once)

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  16. Trigger a data deployment from a CI job

    When we pull down a version between our local and staging environments. We would like to also automatically pull in the testing data from another project.

    As one of the things we are trying to setup is taking a version from Prod then running GhostInspector through our core flows. Ideally every 4 hours we take a backup from metadata + locked down actual data. Then run tests against it.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  17. Allow serial deployment instead of parallel

    When executing a data deployment, an 'Unable to lock row' error can occur if multiple transactions try to lock the same record in Salesforce.
    Because the batches are executed parallel, the chances of getting this error high, depending on the situation.
    For example the master record in a master:detail relationship will always get locked when a DML is executed on the child record.
    If two batches are executed at the same time and they both have at least 1 record that references the same parent, then a locking error will occur.

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
1 3 Next →
  • Don't see your idea?

Feedback and Knowledge Base