Skip to content

Ben Nightingale

My feedback

1 result found

  1. 107 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    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  

    Ben Nightingale supported this idea  · 
    An error occurred while saving the comment
    Ben Nightingale commented  · 

    I agree this is needed . In our case we have outbound messages ans for the differemnt environment they use different URLs. idealy, rather than just being able edit manaully we would like to be able to set a variable for the environment that we could then permentantly set for that piece of metadata so that whenever we depoly to that envrioment the variable is used in place of the data from the source org.

Feedback and Knowledge Base