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

214 results found

  1. Add support for OverrideSettings for Vlocity datapacks

    It would be great if there is a way to set up OverrideSettings https://help.salesforce.com/s/articleView?id=sf.os_build_tool_override_datapack_settings.htm&type=5 for the deployment pipeline. For example, FilterFields can be specified, so those fields are removed from the datapack before being committed to the git repo.

    This should help to reduce the number of differences in the compare view when e.g. Salesforce IDs are different or empty attributes are added.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Add support for Vlocity managed package vlocity_cmt__ProductConfigurationProcedure__c object

    Add support for Vlocity managed package vlocity cmt ProductConfigurationProcedure c object. Currently it is not supported by Gearset Vlocity tab. Confirmed by Gearset. This limits the autonomy of products deployment for Vlocity projects.

    5 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Add to Flow Navigator the flow version description

    It would be very handy if the new Flow Navigator view was able to display flow version description. We update this frequently to describe new changes, so being able to read this documentation in the Flow Navigator would be helpful to understanding the flow.
    Adding this either as a banner along the top (like some flow xml views) or as an element in the navigator sidebar would be acceptable.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Add omni components to filters through metadata API

    Now that Salesforce has moved omnistudio into standard runtime (as opposed to managed package) and also added the omnistudio components to the metadata API, the following components:
    omniDataTransform
    omniIntegrationProcedure
    omniScript
    omniUiCard

    Since these components are in xml format, it is much easier to see differences in source control.
    It also removes the need to perform separate deployments for the Salesforce metadata API and the vlocity build tool.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Comparison of draft deployments

    Two teams who are supposed to be working on different parts of the sandbox org have created two draft deployments. I would like to compare these draft deployments to see if there is any overlap of selected items.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Configure the "Saved Comparison Pair" to always use a specific Comparison Filter

    When managing multiple orgs, and running comparisons, the Saved Comparison Pair saves a lot of time. However, sometimes we need to use different Comparison Filters, based on which environments we are comparing.

    Instead of first choosing the Comparison Pair, then manually selecting the Comparison Filter to use, it would be great to be able to (optionally) configure the Comparison Pair to use a specified Comparison Filter.

    Example Use Case:

    When committing work from our Dev org to BitBucket, we exclude Apex Classes & Triggers, and mainly commit declarative functionality (Apex code is committed separately from our dev team). All development…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Multiple sort columns for comparison results

    It would be helpful to be able to sort comparison results on multiple columns (e.g. first by Metadata type, then by Name). Currently it seems that the results can only be sorted by one column at a 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Show Created by and Created Date in Comparison view

    I'd like to see created by and created date in the comparison view. Sometimes we have multiple users working on items and I may not be the last to modify something but I am the one to deploy it and if I am the creator, I know what it is named but it makes it hard to sift down if I can only show modified by and modified date.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Add a date filtering mechanism on comparisons

    . Currently we can select individual dates on the dropdown list or select from a select few "Last X days". Would be a great option to be able to set something like "See changes from X to Y" or "Select since X", especially useful given we have the dropdown selection on a per minute step, so the list gets very large, very quikcly.

    For compliance checking, tracking who changes what when, periods of criticality (especially around new features coming in) or just for retrospectives.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. default repository

    Allow to set a default repository when you have multiple repositories.

    1. Navigate to Compate and Deploy
    2. Select Source Control and select a VCS(in our case Gitlab Self Managed)
    3. If you have dozens of repositories they all show up on the list
    4. Need ability to specific a default repo which will be auto selected
    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. exclude specific JSON keys when comparing Vlocity/Omnistudio metadata

    We are seeing Omniscripts showing as different on certain JSON keys. These keys always change and should be excluded from your comparison.
    The impact of this is Omniscript deployments require the LWCs to be compiled and if we deploy Omniscripts unintentionally, their LWCs are not recompiled and functionality breaks for the users.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Deploy Now and Validate Package Buttons

    Presently, the Deploy Now and Validate Package buttons are positioned adjacent to each other. Occasionally, there is a risk of unintentionally selecting the Deploy Now button before the package has been validated. This can result in potential issues arising. To address this, I recommend the following actions:

    1. Enable the Deploy Now button only after the Validate Package process is successfully completed.
    2. Consider repositioning the buttons within the User Interface if both buttons share the same screen.
    3. Alternatively, place the Deploy Now button after the Validate Package screen in the sequence.

    Thanks.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Allow download of XML files from the comparisons page

    In some instances, we have to use the Metadata API to download XML files for analysis. However, the Metadata API is a pain to use. Even Salesforce recognizes this and suggests using a migration tool like Gearset to extract these: https://developer.salesforce.com/docs/atlas.en-us.246.0.api_meta.meta/api_meta/file_based.htm

    Since Gearset retrieves these files during comparison, it would be great if there was an option to download them to a zip file directly.

    Note: There is already a "Download Package" feature on the deployment page. However, we obviously can't add items to this page if there is no change between the orgs. So, if a similar feature were…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Show Metadata API version used to retrieve metadata for comparison on comparison result page

    It would save time and give confidence if the specific Metadata API version number used to retrieve the metadata was displayed on the comparison results page.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Add the package Name to the page, when the package is Opened

    Currently when you Open a package like a draft deployment, the Name of the package does not appear. There is a message in top L-H 'Comparison finished' which is not very useful. Perhaps the package Name could go here. It will reduce confusion as you will be able to tell which package you have open. Thanks.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. distinguish between components of feature branch and what is syncing to main

    As a user of gearset deploying pull requests to multiple environments
    I want to be able to identify actual components of the feature branch vs. what is included for syncing to main/main branch for the org being deployed to
    So that there isn't the confusion of understanding what new/changes items are showing up in the commit information

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Please add Namespace/Package name as a column in the comparison view

    Currently , if I pull down metadata from managed packages (e.g. with the intention of committing the custom fields we've added to managed objects or committing the permissions we've updated) this means I get all the metadata in the comparison screen, with no way of filtering out the managed packages. An example of where this is a problem/cluttering the UI is Triggers/Classes - the contents of these is always hidden, so ideally i'd like to have a column to filter them out

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Integrate with Salesforce's Setup Audit Trail for Metadata Detection

    Many metadata types are referenced in Salesforce's Setup Audit Trail. An alternate way to detect changes to include could be querying Setup Audit Trail with a Start / End Date instead of asking user to select the necessary components.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Remove Site.com from the Default Experience Cloud Comparison filter

    The Default Experience Cloud Comparison filter include the Site.com component. This component seems to cause problems with Experience Bundle deployments. I recommend this should be removed from the Default filter.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 10 11
  • Don't see your idea?

Feedback and Knowledge Base