Anonymous
My feedback
2 results found
-
105 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
An error occurred while saving the comment Anonymous
supported this idea
·
-
15 votesAnonymous
shared this idea
·
Allow cached metadata to be changed during target deployment after seeing the difference. This will help us to fix environment specific item. This will specifically allow us to fix report folder, dashboard folder etc where the user in source org is not destination org. This will help us fix deployment issue with this tool rather than going back to Ant to fix such metadata during deployment.