Carl
My feedback
13 results found
-
2 votes
An error occurred while saving the comment Carl
shared this idea
·
-
14 votesCarl
supported this idea
·
-
13 votesCarl
supported this idea
·
-
41 votesCarl
supported this idea
·
-
13 votes
If we implemented this and it was only able to search metadata from that point in time onwards, would that be useful or would it be confusing to communicate in the UI?
An error occurred while saving the comment Carl
commented
+1 Surprised Gearset doesn't offer this when Copado does, though I guess Copado does require a connection to a version control system
Carl
supported this idea
·
-
6 votes
An error occurred while saving the comment Carl
commented
Can probably merge the idea into either: https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/45637060-precision-deployments-available-for-layouts-for or https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/38424808-allow-individual-lines-to-be-selected-for-inclusio
Carl
shared this idea
·
-
19 votes
All - please let us known in the comments which metadata types you would like us to support next with precision deployments. Thanks
Carl
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.Carl
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
Carl
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.
Carl
supported this idea
·
-
30 votesCarl
supported this idea
·
-
28 votesCarl
supported this idea
·
-
17 votesCarl
supported this idea
·
I know the simple solution is to make sure to only select the components needed when selecting the Lightning page metadata type. But when combining deployments together Gearset doesn't default to this behavior it seems or it only takes one deployment that didn't to cause Gearset to try and compare all the components of that type.