Kris Goncalves
My feedback
60 results found
-
7 votesKris Goncalves
supported this idea
·
-
4 votesKris Goncalves
supported this idea
·
An error occurred while saving the comment -
12 votesKris Goncalves
supported this idea
·
-
7 votes
An error occurred while saving the comment Kris Goncalves
commented
This would be super helpful instead of having saved regex in a text file to copy and paste or share between team members. The main use case is to remove the managed package metadata that gearset cannot exclude (managed package custom field on a standard object).
Likewise, if it's easier, it'd be cool to have the regex in the comparison filter saved and tied to a given metadata filter. As I mentioned above, I'm always including the regex at the column level to at least remove managed package metadata.
Kris Goncalves
supported this idea
·
-
9 votesKris Goncalves
supported this idea
·
-
15 votesKris Goncalves
supported this idea
·
-
2 votesKris Goncalves
shared this idea
·
-
1 vote
Gearset will now only use US states and “United States” for the country, meaning that the pairings are always valid.
Kris Goncalves
shared this idea
·
-
11 votesKris Goncalves
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
Kris Goncalves
supported this idea
·
-
25 votesKris Goncalves
supported this idea
·
-
1 voteKris Goncalves
shared this idea
·
-
4 votesKris Goncalves
shared this idea
·
-
2 votesKris Goncalves
shared this idea
·
-
6 votesKris Goncalves
shared this idea
·
-
5 votesKris Goncalves
supported this idea
·
-
5 votesKris Goncalves
shared this idea
·
-
10 votes
An error occurred while saving the comment Kris Goncalves
commented
It'd be nice to also just hear back if this is feasible as it would be nice to be able to trust the diff to make sure we know what is actually changing when deploying layouts/profiles.
Kris Goncalves
supported this idea
·
-
4 votes
An error occurred while saving the comment Kris Goncalves
commented
A cool idea. Would help collaboration between team members in creating a "final package" easier. Not to mention you could validate them separately before combining to figure out issues as well.
Kris Goncalves
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!
An error occurred while saving the comment Kris Goncalves
commented
This would be really interesting to have. We have many sandboxes related to different tracks of the business that need to be backfilled with changes from production. Instead of having to clone the package several times, it would be helpful to have an ability to push from a source to multiple targets at once.
This would be great (considering how many profiles a given org could have).
If this couldn't be done, it'd at least be helpful to have an "expand all" button specifically for this scenario (expand all components on all profiles) so that we can then search successfully.