Nick
My feedback
32 results found
-
13 votesNick
supported this idea
·
-
3 votes0 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Nick
supported this idea
·
-
20 votes
An error occurred while saving the comment Nick
supported this idea
·
-
1 voteNick
shared this idea
·
-
17 votesNick
supported this idea
·
-
1 voteNick
shared this idea
·
-
5 votesNick
supported this idea
·
-
10 votesNick
supported this idea
·
-
25 votesNick
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
Nick
supported this idea
·
-
2 votes
An error occurred while saving the comment Nick
commented
This is important because deployments will fail without having this ability making this unusable for us. Ideally this should also include Processes/Flows as they also fail due to salesforce limits being reached
Nick
supported this idea
·
-
7 votesNick
supported this idea
·
Yes this is desperately needed. If you need to add any components there is a lot of going back and fourth to create a new template and it would be much easier if you could re-save it and overwrite the original.