Patrick
My feedback
8 results found
-
1 votePatrick
supported this idea
·
-
4 votesPatrick
supported this idea
·
-
26 votesPatrick
supported this idea
·
-
82 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
Patrick
supported this idea
·
-
17 votes
An error occurred while saving the comment Patrick
supported this idea
·
-
46 votes
EDIT:
Gearset now lets you select specific fields in layouts for a deployment.
Here's a quick article on getting started with precision deployments for layouts:
https://docs.gearset.com/en/articles/6407322-getting-started-with-precision-layout-deployments
We are working on adding support for more metadata types such as record types, value sets, Lightning pages and other XML types.
An error occurred while saving the comment Patrick
commented
This would make deploying multiple work streams much easier.
Patrick
supported this idea
·
-
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
Patrick
supported this idea
·
-
2 votesPatrick
shared this idea
·
Being able to ignore specific metadata elements would greatly reduce the noise we have to review during deploys. Ideally, I'd be able to setup a minimal list of ignores that list zero differences between production and a new sandbox. Yes, I could ignore the entire metadata type or component, but that might miss other changes that I do want to deploy. Some examples include:
Connect app: <consumerKey>
Settings: DevHub: <enablePackaging2> and <enableScratchOrgManagementPref?
Settings: EmailAdministration: <enableSendViaExchangePref> and <enableSendViaGmailPref>
Settings: Security: <identityConfirmationOnEmailChange> and <enableSamlLogin>