Phil Spenceley
My feedback
12 results found
-
12 votesPhil Spenceley supported this idea ·
-
2 votesPhil Spenceley supported this idea ·
-
17 votesPhil Spenceley supported this idea ·
-
9 votesPhil Spenceley supported this idea ·
-
3 votesPhil Spenceley supported this idea ·
-
3 votesPhil Spenceley supported this idea ·
-
5 votesPhil Spenceley supported this idea ·
-
17 votes
An error occurred while saving the comment Phil Spenceley supported this idea · -
7 votes
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.An error occurred while saving the comment Phil Spenceley commentedI've noticed that some Metadata files have different XML between orgs while the content is actually the same (the XML just has elements in a different sequence). Because the Metadata API doesn't always enforce a sequence for some metadata types, perhaps you could implement an XML sort before a compare to ensure elements are always in the same sequence?
Phil Spenceley 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
Phil Spenceley supported this idea · -
70 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.Phil Spenceley supported this idea · -
9 votesPhil Spenceley supported this idea ·
Another example, we have some fields with formula Hyperlinks that reference different ids as the org changes. Also, site.com settings have a checksum which is always different. Being able to always ignore these would be great.