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

47 results found

  1. 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

  2. Refresh Comparison enhancements

    When doing a "Refresh Comparison", allow only refreshing the source. Or to only refresh the selected items from the source and/or target.
    Example, deploying from a git branch to a sandbox, refreshing the metadata takes a few seconds from git, several minutes from the sandbox (target).

    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

  3. Allow page layout field additions and removals to be selectable

    As a user, when selecting page layout changes to include in my deployment, I would like to include only the fields I have added that are different from my destination environment.

    Dev environments can be worked on by different people. There are times when a solution requires adding an existing field to a page layout to solve your user story.
    At the same time, another user story may also be making changes to that page layout using different fields (removing or adding).

    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

  4. Add an option to ignore package version differences in Apex classes

    I see many differences between apex classes where the only difference is the package version(s), no difference in the code itself. It would be nice to have an option to filter these out so that only the apex classes are shown where the code is different.

    17 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

  5. re-add "re-authorize" link on compare view

    After refreshing a sandbox, you have to re-authorize the sandbox-org. A while ago, there was a link to do so. Now we have to navigate to the list of orgs to re-authorize there.

    Please give us back the re-authorize shortcut :)

    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

    We have now added a 'Re-authorize' button to the access token expiry warning message that will typically appear when selecting Salesforce orgs with an expired token on the initial 'Compare and deploy' page.

  6. Option to sort Custom Application XML

    While this can be done with VSC custom plugins for SFDX, I think it would be really beneficial if Gearset offered the ability to sort Custom App XML in comparisons in order to see what's actually changing between a source and target for lightning page activations. Due to the way SFDC generates this XML, the way page activations are ordered is very difficult to follow, and I think it's an opportunity to make that easier especially for declarative config users of Salesforce.

    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

  7. Add an option to ignore location changes for Flow

    Hi, when reviewing changes for flows that are being deployed, it would be great to have a toggle option to hide or alternately color location changes which are just the location of elements on the flow canvas editor.
    <locationX>1353</locationX>
    <locationY>1305</locationY>

    Sometimes there are hundreds of location changes and it obscures the important information about what else changed.

    21 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

    The "simply differences" toggle in the comparison grid now hides location changes in flows to make it easier to identify important changes. The location changes are still included when deploying changes to the flow.

  8. Identify that metadata is the same, even if ordered differently by metadata API

    There are a lot of instances where the comparison will identify metadata as different, but the only difference is the way the API is ordering the XML. I've seen it happen a lot with picklist values on multi-select picklist fields. It would be nice to be able to turn this on/off somehow so that metadata that isn't truly different won't show up in the difference compare.

    13 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. Refresh specific item in comparison through context menu

    It would be great to refresh a specific item within a comparison that I know has changed since the last comparison.

    107 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

    Gearset now supports:

    - Refreshing a single item - available either from the context menu (by right-clicking an item in the comparison results table) or by using the "Refresh item" button in the XML preview window

    - Refreshing selected items - available from the context menu once one or more items are selected


    Thank you for commenting on and upvoting this request. We hope this new Gearset feature is going to speed up your workflow!

    If anyone has feedback or suggestions, please contact us via the in-app widget.

  10. Option to group and show all selected items while creating new custom filters

    Option to group and show all selected items while creating new custom filters

    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

  11. Change default sort order of Saved Comparison Pairs to use 'Friendly Name' (or last used sort column)

    The new Saved Comparison Pairs feature is great! However, the page appears to load connections in a seemingly 'random' order on each use.

    Confirmed with Gearset Support the default sort order is by create date of each connection pair. However, if feature is used with multiple connection pairs spanning multiple individual instances this requires manual re-sorting of connections every time page is loaded if you want to view pairs logically by naming convention (e.g. Alpha 1->2, Alpha 2->3, Bravo 1-> 2 , Bravo 2 -> 3 etc.) or something other than system create 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

  12. Add a way to "Save" or "Save As" updated filters when in the Refresh Comparison window (like you can in the Compare and Deploy window)

    When in the Refresh Comparison window, it seems there's no way to "Save" or "Save As" the updated filters. Looks like you can only access that feature via Manage Custom Filters from the Compare and Deploy screen

    Any chance we could get that added? It would be super useful!

    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

  13. Exclude LWC Jest files from validation and deployment

    We introduced LWC - Jest tests for our project, which seems to cause validation errors with Gearset.

    As per Salesforce recommendations it is recommended to keep jest tests only locally and in VCS and avoid trying to push them to SF as they would cause validation errors.

    Is there an forward path that allows us to tell Gearset to exclude LWC - Jest files from validation/deployment?

    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

  14. Add "Show selected" button to the Custom Filter editor

    This button needs to be in the type and items columns. This way the developer will see the already selected components and be able to check faster if everything required is selected

    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

  15. Add support for the WorkSkillRouting metadata type

    WorkSkillRouting is a key object in the configuration of Skills-based Routing for omni-channel (using Attribute Setup, not apex class), please add support for this object to enable comparison and deployment.

    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

  16. Include support for new metadata type 'PermissionSetGroup' (Winter '20)

    As feature has moved from pilot to beta in Winter '20 release, looking for support in differencing and deploying the new 'PermissionSetGroup' metadata type.

    20 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

    You can now deploy permission set groups in Gearset!

    PermissionSetGroup isn’t included in the default metadata filter, so you’ll need to include it in any comparison filters you’re using.

    Please get in touch if you spot any problems.

    Thanks,
    Tom

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

    Salesforce has begun adding User metadata to fields. One good example right now is the "Data Owner" field that appears on all custom fields now (in XML this field is labelled as "BusinessOwnerUser"). The field does not link via a Salesforce ID; it instead displays the Salesforce Username of the user.

    Naturally, this field in 99.9% of Salesforce environment comparisons is going to be different. "user@domain.com.sandbox" won't ever match to "user@domain.com" in production-- and it definitely won't ever match to any other Sandbox, either.

    This leads to a nightmare scenario where if this field has been…

    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

    We have added a problem analyzer to detect and fix the issue with ‘businessOwnerUser’, as follows.

    Problem: custom fields referencing a specific user will fail if that user doesn’t exist in the target.

    Solution: this will replace the source ‘businessOwnerUser’ reference with the value from the target’s custom field.

  18. Allow users to discard chunks/certain changes before deploying to target

    For example I'm on the diff screen and I see my page layout has 5 changes/chunks of changes, but I only want to commit/deploy the first one - please add functionality so that I can discard/ignore the other 4 changes in the file and only deploy the one change I want.

    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

  19. Treat "New" FLS entries that don't grant any access as "Not Different" in Profiles and Permission Sets

    Due to a recent change in the SF API, Permission sets now display every field in the org as a "New" FLS item, with Readable and Editable both set to False. This is leading to two distinctly negative results.

    1) For every "Permissions for FieldNameXXX" item, every permission set in the org is modified. If two projects on two different sandboxes each add a field, they will both modify modify all the same files, and require manual XML merge. for our org thats almost 70 files that need manual merge with every new field.

    2) When you dig into a…

    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

  20. Optimize "Refresh Comparison" to only pull metadata that has been changed since the last comparison

    Currently, clicking Refresh Comparison does not optimize the comparison in any way, it just allows you to skip selecting some of the configuration steps from running a new comparison.

    This means that it takes the same amount of time actually comparing the orgs.

    It would be nice if on clicking of "refresh comparison" the logic didn't run a full compare and instead just looked at metadata that had been changed since the last compare in order to reduce the comparison time.

    21 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 everyone

    We have now shipped the three key improvements to refreshing a comparison. 

    You are now able to:

    • refresh a single item (right-click an item in the grid or use Refresh Item button in the Diff viewer)
    • refreshing selected items (right-click a selected item in the grid)
    • refresh only additional types in the filter (via Refresh comparison -> Filter dialog)


    We hope these enhancements will greatly reduce the comparison time for you. 

← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base