Anonymous
My feedback
-
30 votesAnonymous
supported this idea
·
-
36 votes9 comments · Help us improve Gearset » Deployment automation · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
-
99 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
Anonymous
supported this idea
·
-
71 votes14 comments · Help us improve Gearset » Comparisons and difference visualization · Flag idea as inappropriate… · Admin →
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
Anonymous
supported this idea
·
-
46 votes7 comments · Help us improve Gearset » Deployment automation · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
-
95 votes18 comments · Help us improve Gearset » Comparisons and difference visualization · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
-
1 voteAnonymous
shared this idea
·
