Paweł Woźniak
My feedback
16 results found
-
2 votesPaweł Woźniak supported this idea ·
-
2 votesPaweł Woźniak shared this idea ·
-
2 votesPaweł Woźniak shared this idea ·
-
14 votesPaweł Woźniak shared this idea ·
-
2 votesPaweł Woźniak shared this idea ·
-
13 votesPaweł Woźniak supported this idea ·
-
12 votesPaweł Woźniak supported this idea ·
-
21 votesPaweł Woźniak supported this idea ·
-
35 votes
We're currently reviewing how we can facilitate deployments to multiple Salesforce instances simultaneously. Please let us know how you manage this currently, or how you would like to manage it - thanks!
Paweł Woźniak 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.
Paweł Woźniak supported this idea · -
69 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.Paweł Woźniak 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
Paweł Woźniak supported this idea · -
11 votes
An error occurred while saving the comment Paweł Woźniak supported this idea · -
3 votesPaweł Woźniak supported this idea ·
-
2 votesPaweł Woźniak 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
An error occurred while saving the comment Paweł Woźniak commentedYes I would like to have this feature too for simple fixes.
Paweł Woźniak supported this idea ·
Yes, it would be useful to improve this.