Simon
My feedback
1 result found
-
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
An error occurred while saving the comment Simon
supported this idea
·
I had a situation where a salesforce bug replaced a lookupFilterFields name with an ID, which consequently made a deployment fail. As search layouts are packaged w/the object, there was no way to remove this reference. I eventually solved the problem by examining the xml file in eclipse and deleting the offending field from a search layout but this was potentially a showstopper that could have been solved quickly if I could have edited the object's xml representation.