Skip to content

Nathanael Schmolze

My feedback

6 results found

  1. 10 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)
    An error occurred while saving the comment
    Nathanael Schmolze commented  · 

    Agreed, this would be great!

    One common area where I often wish for this is when I'm filtering for custom metadata. I might filter by name to reduce the selection to a single type of custom metadata, which then may have several hundred records under it. I'd have to go one by one to check all of them, so at this point I don't bother filtering custom metadata, and just run a comparison on all of them. But we're making enough use of custom metadata that it's starting to "feel" like our large number of CM records is slowing down the comparison, and it would be nice to filter it down to just what we need to compare.

    Nathanael Schmolze supported this idea  · 
  2. 3 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)
    Nathanael Schmolze shared this idea  · 
  3. 2 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)
    Nathanael Schmolze shared this idea  · 
  4. 1 vote

    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)
    Nathanael Schmolze shared this idea  · 
  5. 100 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  

    Nathanael Schmolze supported this idea  · 
  6. 104 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)
    Nathanael Schmolze supported this idea  · 

Feedback and Knowledge Base