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.
47 results found
-
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 votesYou can now exclude fields and other items in page layouts from being deployed using Gearset's new Precision deployments feature: https://docs.gearset.com/en/articles/6407322-getting-started-with-precision-layout-deployments
-
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 votesWe 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.
-
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 votesYou can now select the exact fields and other layout items for deployment using Gearset's new Precision deployments feature: https://docs.gearset.com/en/articles/6407322-getting-started-with-precision-layout-deployments
-
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 votesWe 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.
-
Unscramble order of <excludeButtons> tags in Layout metadata
Page Layouts use the <excludeButtons> element to indicate the presence or absence of standard buttons on a layout.
But this element appears in an arbitrary order when retrieved. Unlike other metadata which gets canonicalized by sorting alphabetically.
Gearset could sort these elements to avoid the random order causing random diffs to appear in metadata comparisons when in reality there is no difference.
4 votesWhen Gearset detects that the only differences in your Layout are the result of reordering, and so there aren't any real differences to show you, it will automatically consider this metadata to be unchanged. As a result, this Layout won't appear in the list of changed metadata and will no longer clutter up your comparison results.
If there are any material differences in your Layouts, they will still appear in your comparison results as normal.
And you'll be able to use the Hide reordering checkbox to filter out any immaterial differences, just as you would for other metadata types.
-
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 votesWhile not exactly one-to-one match, we think this UserVoice already delivers the desired outcome:
Thank you for upvoting this UserVoice request!
-
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 -
When exporting from the comparison reports page, the currently selected items should show in the export
Today when you are on a comparison results screen there is an export button that will export the entire list of comparison results to a csv. However the current export does not include a column indicating items that have been selected for the current deployment. Having this column would help in reviewing the list of data outside of gearset.
3 votes -
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 votesSorting by “Last used” column has now been fixed.
-
Stop Reordering Package.xml
We would like to keep our package.xml file in alphabetical/lexicographical order by the <type> element. Gearset appears to change the order so that datatypes that include all <members> elements (i.e. use an asterisk) are placed at the bottom of the file. This inconsistent sort order makes datatypes harder to find when viewing or amending the file.
2 votesThis is now done. Thanks for the suggestion.
-
Include ability to add inclusion/exclusion option for custom filters
For custom filters we need to exclude objects that are non-relevant. Most often these are managed packages (eg. fflib*, al, rstk__, etc). The only way to do this currently is to deselect all items and manually select each item individually. Not only is this a laborious process, this means that anytime any other new objects are created, these custom filters will ALWAYS need to be updated in order to include them. An inclusion/exclusion filter offers greater flexibility and is maintainable. The current approach is neither a manageable nor scalable process for a large development team. Alternatively, add…
2 votesGearset now supports regular expression in custom filters, so you can write these kinds of rules
-
Filter comparions by date since x
The current functionality for filtering by date is welcomed, but I would like to suggest the ability to filter by date range.
Just some examples:
Date >= x
Date <= x
Date >= x and <= y2 votesGearset now has the ability for custom data ranges using a date picker, which should allow you to filter to all the examples that you’ve shown.
-
Allow search-based excluding of metadata for templates
Sometimes we have individual metadata that must be excluded-- every time-- from releases, without excluding the entire metadata category.
For our organizatin, for example, we want to exclude "Search" every time due to an error-- but we don't want to exclude the "Settings" metadata item.
It would be great if we could add specific exclusions to the template so that a specific metadata item would not even pop under the Compare screen. Doesn't really matter how it's done (fuzzy searching or specifically excluding standard items) to me.
2 votesThis work has now been completed, and you can specifiy individual items on the metadata filter.
The doc is available from https://docs.gearset.com/feature-guides/comparisons-and-deployments/custom-metadata-filters
Thanks,
Kevin -
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 voteThis feature was released on December 1st, 2020. Thank you for the suggestion.
-
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 -
Deploy CMS/CRM Connection and and CMS Collections
We would like to be able to deploy CMS/CRM Connection and and CMS Collections. They are a part of Community Workspace.
1 vote -
Deployment screen to show which components were selected vs included
When you get to the summary page, often times you will be deploying with the need for sub-components to be included in the package despite them being actual changes.
When you're selecting those items inside the comparison page, it would be helpful to see that total be reflected in the deployment summary page. So if you picked 50 items to deploy but it needed an additional 1,000 components (despite them having No Difference) then we should see those breakdowns on the Deployment Summary
Gearset soft alrt message "Some components with difference type of No difference have been added to the…
1 vote -
Dependency Enhancement for App Menu metadata
Currently, when we compare App Menu metadata, the "Depends On" tree is empty, even though it definitely has dependencies on connectedApps and customApplications.
Please add dependency analysis for App Menu metadata,
1 vote -
Add Prompt metadata type
Please add the new Prompt metadata type
1 vote -
provide a verification that a metadata filter is to be deleted.
It's far too easy to delete a custom metadata filter. When deleted, there is no way to retrieve it. Currently, I create backups of the filter by storing them with the same filter name and datetime. It's in case someone or even myself accidentally deletes the filter.
1 vote
- Don't see your idea?