Anonymous

My feedback

  1. 8 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)
    Anonymous supported this idea  · 
  2. 6 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)
    Anonymous supported this idea  · 
  3. 99 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

    19 comments  ·  Help us improve Gearset » New feature  ·  Flag idea as inappropriate…  ·  Admin →

    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  

    An error occurred while saving the comment
    Anonymous commented  · 

    This is a great idea, and we recently ran into a use case where we had to migrate from a new Summer 17 Release, to an old Spring 17 release (in sandboxes). This resulted in some errors since some settings and metadata just didnt exist in the Spring 17 box, preventing us from moving things like Search Settings, OrgPreference settings, and even a lightning record page. Being able to edit the XML directly in Gearset and rip out things in the deployment to the target org, instead of manually doing it with ANT. +1 to this feature.

    Anonymous supported this idea  · 

Feedback and Knowledge Base