Anonymous
My feedback
9 results found
-
16 votesAnonymous
supported this idea
·
-
9 votes4 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Anonymous
supported this idea
·
An error occurred while saving the comment -
38 votesAnonymous
supported this idea
·
-
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
Anonymous
supported this idea
·
-
33 votesAnonymous
supported this idea
·
-
79 votes
Merging differences between Apex classes and VisualForce pages is difficult to do automatically due to the understanding required by the developer. For differences between two orgs in other object types, Gearset helps you sidestep that with our granular comparison results. This blog post explains more: https://gearset.com/blog/merging-salesforce-metadata
An error occurred while saving the comment Anonymous
commented
This is a must have feature for developer. Having built into Gearset will save us tremendous amount of time and make our lives a lot easier.
Allow me to post merging feature from a competitive product:
https://bluecanvas.io/blog/how-to-solve-merge-conflicts-in-salesforceAlso, this feature has been under review since March 2016. We need this feature so badly.
Anonymous
supported this idea
·
-
11 votesAnonymous
supported this idea
·
-
68 votes
Thanks for the suggestion.
We have plans to improve the way the diff viewer handles changes and whitespace in the future, though it’s not currently under development.
Thanks,
Jason.Anonymous
supported this idea
·
-
49 votesAnonymous
supported this idea
·
This is a must-have feature. If we work on multiple projects that have different release schedules and in these projects, they share some common components/metadata, this will allow us to select specific commit based on the commit ID to make the deployment.
Without this, we will have to create a separate org environment, break out the integrated codes, and deploy from that org instead from the VCS (as VCS is our source of truth).