Ryan Mccloskey
My feedback
15 results found
-
1 vote
-
35 votes
We're currently reviewing how we can facilitate deployments to multiple Salesforce instances simultaneously. Please let us know how you manage this currently, or how you would like to manage it - thanks!
An error occurred while saving the comment -
4 votes
An error occurred while saving the comment Hey it looks like we posted the same idea, can you upvote mine? https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/45190105-make-custom-filters-a-top-level-menu-item
-
5 votes
-
13 votes
-
70 votes
Thanks for the suggestion.
We have plans to improve the way the diff viewer handles changes and whitespace in the future, though it’s not currently under development.
Thanks,
Jason. -
82 votes
Merging differences between Apex classes and VisualForce pages is difficult to do automatically due to the understanding required by the developer. For differences between two orgs in other object types, Gearset helps you sidestep that with our granular comparison results. This blog post explains more: https://gearset.com/blog/merging-salesforce-metadata
-
107 votes
Hello. A large number of commenters requested the ability to carry out value replacements as part of metadata deployments.
Gearset now offers a feature called Environment Variables that lets you do just that!
It works with both manual and CI deployments and lets you target either a Salesforce org or a Git repo of your choice. And, for a number of key metadata types, you can even specify the exact 'field' where the replacement should take place.
If you have any feedback on the Environment Variables feature, please open a new feature request or simply let us know in the in-app chat.
Thank you for upvoting this feature request and we hope that you will find the Environment Variables feature useful.
Blog post: https://gearset.com/blog/environment-variables/
Support doc: https://docs.gearset.com/en/articles/5557015-using-environment-variables-in-gearset
-
17 votes
-
9 votes
-
14 votes
-
16 votes
-
12 votes
-
4 votes
-
26 votes
I definitely want this to be a feature.
But I worry that GearSet will have difficulty implementing this since their deployment package seems to be based on the diff between source and target. If you change the target during the compare process GearSet will actually throw an error that the target has changed and prompt you to rerun the comparison (while saving your selected items).
For now I use the "clone deployment package" feature, but it still requires you to wait while the comparison runs against the new target. Any items you selected in the original comparison while remain selected, but only if they are still registered as a difference.