Justin Slagle
My feedback
15 results found
-
2 votes
An error occurred while saving the comment -
1 vote
An error occurred while saving the comment Adding to this idea -
Maybe when you navigate back to the comparison from a failed validation screen, a new "Error" tab would show up at the top (next to All, New, Change, Delete). Then, only those items/components that related to the validation errors would appear on that tab. -
14 votes
An error occurred while saving the comment This would save me so much time and manual hassle of working through those errors. I also added a similar idea (almost 2 years ago now). I'd love to be able to go from the failed validation screen, back to the comparison, and just have it highlight those individual components that corresponded to the validation errors.
Better yet, when you navigate back to the comparison, maybe there'd be a new "Error" tab at the top (next to All, New, Change, Delete), with just those components.
https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/47653520-highlight-failed-validation-components -
2 votes
-
2 votes
-
32 votes
An error occurred while saving the comment This is probably my biggest complaint for every single deployment. It's hard to make sure you're deploying everything you're supposed to, when there's a lot of extra "noise" like this that shows up.
You can click the "Simplify Differences" to hide them on a line-by-line basis, but it'd be great if that option could be globally applied to the whole comparison. "Simplify Differences" to omit reordering should be a filter option on the Comparison Filters configuration.
-
36 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!
-
2 votes
-
14 votes
An error occurred while saving the comment Yes! This would make things so much cleaner.
Allow the "Simplify Differences" toggle to be defaulted to "On" for the entire comparison, not just on a file-by-file basis. Then, if the file has no discrepancies other than those, just omit it from that group altogether, and don't flag it as being different.
This would save so much time in having to sift through those files every time they come up.
-
2 votes
-
4 votes
-
10 votes
An error occurred while saving the comment Experiencing the same thing - getting the following in comparisons, even though I don't have Person Account activated in the org:
<personAccountDefault>true</personAccountDefault>
Not sure what is causing this attribute to show up, but I'd love to know what the fix is for this.
-
1 vote
-
4 votes
-
2 votes
This is something that can make that list of changes look a whole lot bigger than it needs to be.
I also found this suggestion from a few years ago:
See also: https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/36870055-stop-the-reordering-of-xml-when-deploying-to-git