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.
369 results found
-
Allow users with owner role to modify and start backups
Allow designated users the ability to modify and start backups without being the owner of the connected org or the person who created the backup.
5 votesYou can now specify other team members to have permissions to manage and start backup jobs they don’t own.
The current owner of the backup job will need to edit the current job settings, go to the new ‘Permissions’ tab and choose the team member and level of access that you’d like to grant them to manage your backup job.
-
6 votes
You can now add your on-prem GitLab instance to Gearset and set up validate pull requests with it. Thanks for your suggestion.
-
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 votesAdded on the 5th of October 2020.
-
Allow "View Errors" in CI Job History page to be opened in a new tab
It would be great if the button allowed to be opened in a new tab (essentially allow buttons and links to act like regular HTML elements that allow opening in a new tab via Cmd/Ctrl+click or via right click)
Example right clicking the "View Errors" shows no open to open in a new tab https://d.pr/i/m5CNIG
Right clicking "View comparison" allows for it https://d.pr/i/WpCfFF
This is similar to https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/35538631-make-clone-package-openable-in-a-new-tab
1 vote -
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 -
Export subset of data in data backup
I would like to be able to filter what I want to export from a data backup, since I probably won't need everything from the database. This would make the downloading more manageable.
Ex: Export only ContactID and Email fields from Contact object from a specific backup.
(Restore data seems to allow this, but in this specific case I needed to run some checks in Excel since I couldn't just update everything with the old data)
3 votesYou can now select the object(s) to export for a particular backup run.
Simply go to the backup history for a job, and for a backup run, choose the ‘Download data’ option in the context menu to choose the subset of data that you’d like to export.
-
Support flow deletion at V44+
if the target flow is deactivated; and all prior versions are deleted, you can't delete the last remaining flow version in the target org. The error you get is "Insufficient access rights on cross-reference id".
Copado provides a solution (https://docs.copado.com/article/8l069zes9f-destructive-changes-in-copado-doesn-t-support-flow-and-process-builder) wherein the user can specify the contents of the destructive-changes.xml file (enumerating the versions to delete) but Gearset has no way to inject such a file into a compare/deploy (esp a CI deploy)
with SFDC pushing more and more dev into Lightning Flow, deletions are inevitable in many orgs as things get refactored/renamed
2 votesWe have added a problem analyzer that will detect when you are deleting a flow, and update the destructive changes xml to include all the versions automatically.
Thanks for the suggestion!
-
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.
-
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 voteWe have now added support for this metadata type.
-
Remove botUser from Einstein Bot metadata
The metadata for EInstein Bots includes a tag called "botUser" that contains the username of the user you've specified to run the bot as. Because it contains a username, the deployment fails unless you have the exact same username in both environments.
My current workaround is to deactivate the bot, remove the running user (which removes the botUser tag), deploy, then reset the changes that I made.
Can we get a problem analyser that will detect and remove this botUser tag so that the deployment will complete?
1 voteHi. We have implemented a PA for this now, which will remove the BotUser field if needed to prevent Gearset from trying to overwrite the user with one from the source.
-
Upgrade to PMD 6.17.0
Current version is 6.11.0.
We should be consistent with newer version. We are having issues with older version in Gearset regarding the ApexDoc rule.
The issue was described and discussed with Valerio in the chat.
Thanks
7 votesWe upgraded to 6.21.0 today. Thanks for the suggestion.
-
Add support for CMS Connect Sources
Please add support for CMS Connect Sources in the comparison filters as well as the deployments and CI jobs.
We're working with CMS Connect in our current developments of a customer community and we'd like to deploy this metadata as well.
See the metadata api documentation: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_cmsconnectsource.htm2 votesWe have now added support for the CMS Connect Source metadata type.
-
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
-
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 -
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 votesHi 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.
-
Test Run results
Test Run results show duration in Seconds but I believe the results are actually in Milliseconds
2 votes -
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 votesThe data deployment history page now shows the start time, duration and end time (on hover) of a data deployment. The start time is the start of the deployment (option 1 that’s listed here).
-
Deploy permissions for Lightning Record Pages
provide a means of deploying the profile/recordtype/app permissions for lightning record pages without having to deploy the whole app.
4 votesGearset now has precision deployments for Custom Applications, so you can select and deploy individual lightning page assignments.
-
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.
21 votesThis has now been added. You can update an existing data deployment template by deploying from it and clicking on the save template modal on the data deployment summary screen.
-
Introduce 'ListView' as an option in 'Metadata filter' tab
When navigating to the 'Metadata filter' tab to select filters, there are currently 122 options, however 'List View' is not one of them.
When navigating 'Metadata Types & Components' in Workbench, 'ListView' is described independently, and I have used it previously when deploying via ANT. Therefore I would imagine there is a way to identify List Views independently of 'Custom Objects'.
This would be a huge help with a Production monitoring job, as I do not mind if List Views are updated by certain users in Production, but currently they are flagged as differences. Basically, I want to ignore them…27 votesThis is now released, you will need to update the metadata filter for any jobs set up already to take effect.
You can now exclude list views as well as other subcomponents of custom object.
(Note: named items is not populated for subcomponent metadata types.)
- Don't see your idea?