Skip to content

Help us improve Gearset

We love getting feedback from our users on how we can make Gearset even better. Post your ideas for improvements, new features, and bug fixes alike, and vote for others – let us know what’s important to you.

If you need any further support, please contact us at team@gearset.com.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

25 results found

  1. Option to exclude all custom fields during data deployment

    Hi, We are doing data deployment from one production org to another production org and we have completed the migration of all records of a particular custom object but after completion of record migration the client wanted to migrate the files and attachments present in the records.

    while doing so we do need to update all custom fields present in the records again as this could replace the updated records with old data from old production.

    So we have used the exclude fields option but there is no option to select exclude all fields at a time we have to…

    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

  2. Ability to activate / deactivate Flows / Processes as part of the meta data and/or data deployment process

    It should be possible to have gearset to deactivate flows and/or processes based on a selection. And to roll-back afterwards. Similar to what has been created here: https://sfswitch.herokuapp.com/

    10 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

    Hi, thank you for voting on this UserVoice. 

    Flows can now be deactivated in Gearset alongside validation rules and triggers before data deployments. 

    Click the View and disable rules... button in the bottom-right of the pre-deployment summary page (next to DEPLOY DATA) to prepare a special metadata comparison.

    To deactivate a flow, simply select & deploy its corresponding flow definition.

    https://docs.gearset.com/en/articles/4536761-disabling-validation-rules-triggers-and-flows

  3. Select the fields to deploy during a data deployment

    Hi we use the data deployment feature is it possible to only select some fields to deploy data from one org to another and not always all the fields on an object.

    19 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. Select individual fields in a Data deploy

    Having the option to move up only selected fields in a Data deployment is needed. If we are required to move up all fields in each deployment, there are scenarios where our work will get bottlenecked in a sandbox on the way to production and at that point all the deployments will be identical.

    4 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

    Completed  ·  1 comment  ·  Data deployment  ·  Admin →
  5. Search option when selecting a Data template

    When choosing a template in a Data deployment, an option to search all templates is needed. We will be updating/modifying/saving new templates often and a manual scroll will become inconvenient. Control F works to find a template, but a dedicated search option would be preferable

    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

  6. Allow renaming of data deployment templates.

    It would be very useful to be able to see the details behind data deployment templates and manage / rename them

    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

  7. Correctly create Price Book Entries records with different currencies and updated PBEs when they are out of sync (or delete+insert)

    1) Currently PBEs are incorrectly inserted with the company currency as apposed to the currency of the source record.

    2) PBE's currency cannot be updated once created (SF restriction) but because PBE's should not be referenced by Id, (that would be a terrible design decision). It is quite possible to delete and recreate any out of sync records.

    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

  8. Functionality to Data Deploy Active Orders

    Salesforce doesn't support the creation or update or standard Order records with a Status Category of Active. This means Gearset is unable to data deploy any active orders. It would be very useful if there was an option for Gearset to temporarily set active orders to a draft status for the deployment or the Order Records and related Order Records, and then set the status back to Active for the final step.

    4 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

  9. Cancel a running data deployment

    Currently I am trying to copy data from production into a sandbox and mask them, but I forgot to adjust the amount of records to create. Now Gearset tries to create thousands of records for each and also mask them with a lot of fields included. I would like to abort the process but don't see any option because this huge amount of data and background services consumes a lot of time and compute resources. Also, I can’t estimate how much time is still left to complete the data deployment. Also, just to see is also a huge improvement but…

    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

  10. Add support for Currency and Percent fields to be masked during a data deployment

    We have some custom objects that hold financial data so masking currency and Percent fields will help when doing data deployments

    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

    Completed  ·  1 comment  ·  Data deployment  ·  Admin →
  11. Include a Comparison for a Permission Set Group's Muting Permission Set

    Include a Comparison for a Permission Set Group's Muting Permission Set. Currently, you can deploy a Permission Set and/or a Permission Set Group. However, if that Permission Set Group contains a muting permission set, Gearset doesn't pull the data. Here is a link to the SF guide on the muting permission set: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_mutingpermissionset.htm?search_text=muting%20permission%20sets

    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

  12. Show start time, end time and duration of a data deployment

    This would be very helpful in order to communicate and set expectations with others on how long Data Deployments take as well as seeing how to improve the speed of longer running Data Deployments. If only one date/time can be displayed, then I think it would be better to see the End Time of the Data Deployment job. Currently, the Date column listed appears to be either (1) the start time of the Data Deployment job, or (2) the date/time when the Configure and deploy was clicked to start configuring the job. If it's #2, this isn't very useful.

    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

  13. Add batch size option to data deployment

    It would be great to be able to pick the batch size used when doing data deployments.

    We have to work with some orgs using poorly performing managed packages that are blowing up due to CPU limits.

    We don't have many option, so being able to reduce the batch size, and hence the CPU load would be really useful.

    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

  14. Migrate audit fields during a data deployment

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

    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

  15. Include logic operator choices in Data Deployments

    Currently Data Deployments only allow filtering on
    [FIELD] = [VALUE]

    It would be beneficial to be able to include other logic operators such as:
    NOT EQUALS
    LIKE
    IN
    GREATER THAN
    LESS THAN

    etc.

    14 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

    We’ve made lots of improvements to the data deployment filters over the past few months.

    The filters now include:
    - equals
    - not equal
    - greater than (or equal to) & less than (or equal to) for dates, datetimes and numbers
    - is empty & is not empty for nillable fields

    You can now specify multiple values (use OR logic) when using the equals filter.

    We’ve made it easier to input dates and times so that you don’t have to rely on knowing the exact format.

    There’s validation so that filters with invalid values aren’t possible. These invalid values would have caused the deployment to fail.

    If there’s still further improvements that you need, please could you create (or vote on) a new idea? This will help us identify which improvements are most valuable to you.

    Thanks,
    Tom

  16. Add the ability to export Success and Error logs for Data Deployments

    When I do a deployment it would be useful to download the success and error logs as a csv or excel document

    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

  17. Allow for the masking of data during a Data Deployment

    During a data deployment it should be possible to mask the data in specific fields. For example, if I were importing Account and Contact data from production into a sandbox I would want to be able to mask email address so that we can't erroneously send actual customers emails while we're testing

    4 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

  18. Add "is empty" operator to data deployment filters

    Add the empty operator or allow for '' or an equivalent to be considered a value for filtering while using the data loader, this would allow to use filters like where accountid='' or equivalent

    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

  19. Show source Org records count for each object so that we can decide on how much of it can be moved and how much of filter is needed

    Show source Org records count for each object so that we can decide on how much of it can be moved and how much of filter is needed. Moreover after all object are select with filters for movement, please show the total number of records that will be migrated across all selection and its related objects. This will tell us if we are exceeding the limit of 10000 and do we need to split.

    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

    Hi,

    When you select objects for a data deployment, you’ll now see how many records the source contains for that object. This will also take into account any filters you have on the object.

    We’d love to hear if this is useful or if there’s more you need – please get in touch via the in-app chat!

    Tom

  20. Ability to compare and migrate object data between Salesforce orgs

    The metadata compare and deploy is outstanding and works well. What would save configuration and release engineers even more time would be an object data compare / sync. Sometimes, salesforce releases may only require a data migration. Hopefully, this feature will get a few upvotes from the community as well.

    14 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

← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base