Troy Hoshor
My feedback
-
3 votesTroy Hoshor
supported this idea
·
-
14 votesTroy Hoshor
supported this idea
·
An error occurred while saving the comment -
15 votes
An error occurred while saving the comment Troy Hoshor
commented
Just tested Data Deploy and this feature would definitely be useful for our organization.
Troy Hoshor
supported this idea
·
-
12 votes
An error occurred while saving the comment Troy Hoshor
commented
Just tested Data Deploy and this feature would definitely be useful for our organization.
Troy Hoshor
supported this idea
·
-
64 votes8 comments · Help us improve Gearset » Comparisons and difference visualization · Flag idea as inappropriate… · Admin →
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.An error occurred while saving the comment Troy Hoshor
commented
Jodie, please chime in on the case I submitted here on the BusinessOwnerUser topic... I had exactly the same issue as you!
Troy Hoshor
supported this idea
·
-
1 vote0 comments · Help us improve Gearset » Team and account management · Flag idea as inappropriate… · Admin →Troy Hoshor
shared this idea
·
-
36 votes7 comments · Help us improve Gearset » Comparisons and difference visualization · Flag idea as inappropriate… · Admin →
The work has now started on providing support for Page Layouts. The general idea is to allow individual fields/buttons/etc. to be selected/de-selected for deployment.
Troy Hoshor
supported this idea
·
-
2 votes2 comments · Help us improve Gearset » Monitoring and reporting · Flag idea as inappropriate… · Admin →Troy Hoshor
supported this idea
·
-
3 votes0 comments · Help us improve Gearset » Problem analysis and deployment failures · Flag idea as inappropriate… · Admin →Troy Hoshor
supported this idea
·
-
2 votes0 comments · Help us improve Gearset » Problem analysis and deployment failures · Flag idea as inappropriate… · Admin →Troy Hoshor
supported this idea
·
-
2 votes0 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Flag idea as inappropriate… · Admin →Troy Hoshor
shared this idea
·
-
46 votes7 comments · Help us improve Gearset » Deployment automation · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Troy Hoshor
commented
A temporary cache of recent comparisons (and their subsequent configuration) for, say, an hour might be enough for me personally. I predominately use the save draft feature as a precaution if I lose my browser session rather than as an actual draft feature.
Troy Hoshor
supported this idea
·
-
71 votes14 comments · Help us improve Gearset » Comparisons and difference visualization · Flag idea as inappropriate… · Admin →
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
Troy Hoshor
supported this idea
·
An error occurred while saving the comment Troy Hoshor
commented
Another scenario where this is a problem are things that are commonly shared between features such as Page Layouts. 2 configurators are working on separate changes with fields on on a Contact Page Layout; one finishes their work, the other doesn't. If the person who finishes deploys the Layout before the other is ready, we're now in a situation where we have to rollback or they are both blocked from deployment until both are finished.
It would be great to be able to pick and choose which "chunks" of metadata to include in a Gearset deployment so that you could avoid this scenario. The complete feature would be selected to move forward while the incomplete one would not.
There's no good way to handle this scenario outside of manual release management & human review, so if Gearset added this it'd be a huge help!
-
99 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
Troy Hoshor
supported this idea
·
-
7 votes2 comments · Help us improve Gearset » Comparisons and difference visualization · Flag idea as inappropriate… · Admin →
Thanks for the suggestion Celio.
We think this should be possible to do and are doing some background work into how to manage and display this. More details to come soon.
Thanks,
Jason.Troy Hoshor
supported this idea
·
-
4 votesTroy Hoshor
supported this idea
·
-
3 votes1 comment · Help us improve Gearset » Monitoring and reporting · Flag idea as inappropriate… · Admin →Troy Hoshor
supported this idea
·
-
14 votes
An error occurred while saving the comment Troy Hoshor
commented
There definitely could benefit to being more pre-validation for Profiles. We've been unable to delete profiles due to dependencies in particular.
Maybe a prompt on that "Warnings/Fixes" screen for potential Profile problems?
Troy Hoshor
supported this idea
·
-
1 vote0 comments · Help us improve Gearset » Problem analysis and deployment failures · Flag idea as inappropriate… · Admin →Troy Hoshor
shared this idea
·
This is INCREDIBLY needed. Creating templates is time-intensive, and if you need to make a minor change after a template has been run, you have to create it from scratch. Even assuming you were OK clicking through to create the template from scratch again, there's no way to even view how a previous template was built! So unless you've taken meticulous notes the first time through, you're SOL.
There definitely needs to be a template editing feature-- or at the VERY LEAST, allow us to select a template and then 'go back one step' to the initial configuration of that template, so that we can adjust it & save a new copy.