Jeff Baldwin
My feedback
15 results found
-
17 votesJeff Baldwin supported this idea ·
-
20 votesJeff Baldwin supported this idea ·
-
16 votesJeff Baldwin supported this idea ·
-
3 votesJeff Baldwin shared this idea ·
-
2 votes1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Jeff Baldwin supported this idea ·
-
2 votesJeff Baldwin supported this idea ·
-
4 votesJeff Baldwin supported this idea ·
-
13 votesJeff Baldwin supported this idea ·
-
14 votesJeff Baldwin supported this idea ·
-
5 votesJeff Baldwin supported this idea ·
-
14 votesJeff Baldwin supported this idea ·
-
5 votesJeff Baldwin shared this idea ·
-
41 votesJeff Baldwin 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
Jeff Baldwin supported this idea · -
69 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.Jeff Baldwin supported this idea ·