Ethan Dunzer
My feedback
39 results found
-
1 voteEthan Dunzer
shared this idea
·
-
3 votesEthan Dunzer
supported this idea
·
-
17 votesEthan Dunzer
supported this idea
·
-
17 votesEthan Dunzer
supported this idea
·
-
21 votesEthan Dunzer
supported this idea
·
-
20 votesEthan Dunzer
supported this idea
·
-
21 votes2 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Ethan Dunzer
supported this idea
·
-
22 votesEthan Dunzer
supported this idea
·
-
25 votesEthan Dunzer
supported this idea
·
-
28 votes2 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Ethan Dunzer
supported this idea
·
-
31 votesEthan Dunzer
supported this idea
·
-
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!
Ethan Dunzer
supported this idea
·
-
41 votesEthan Dunzer
supported this idea
·
-
46 votes
EDIT:
Gearset now lets you select specific fields in layouts for a deployment.
Here's a quick article on getting started with precision deployments for layouts:
https://docs.gearset.com/en/articles/6407322-getting-started-with-precision-layout-deployments
We are working on adding support for more metadata types such as record types, value sets, Lightning pages and other XML types.
Ethan Dunzer
supported this idea
·
-
51 votesEthan Dunzer
supported this idea
·
-
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
Ethan Dunzer
supported this idea
·
-
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
Ethan Dunzer
supported this idea
·
-
5 votesEthan Dunzer
supported this idea
·
-
2 votesEthan Dunzer
shared this idea
·
