Richard Scott
My feedback
7 results found
-
1 vote
An error occurred while saving the comment Richard Scott
shared this idea
·
-
4 votesRichard Scott
shared 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.An error occurred while saving the comment Richard Scott
commented
I think this improvement would be similar in nature so I wanted to append my comment here. It would also be nice to have a selection to ignore case in compare results.
Thanks!
Richard
Richard Scott
supported this idea
·
-
3 votesRichard Scott
shared this idea
·
-
2 votes
An error occurred while saving the comment Richard Scott
commented
You're welcome.
I apologize for the delay as I have been out of the office for a bit. Yes, this matches my experience pertaining to shared reports. It is the actual folder where the permissions are located. However, I will need to validate that creating the folder in the target ORG will make the reports push through. I will let you know how that goes for me within a day or two.
Thanks!
Richard
Richard Scott
shared 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
An error occurred while saving the comment Richard Scott
commented
I agree that this would be a great feature. Instead of updating the metadata directly, maybe something similar to that of token replacement would be a good way to achieve this. There could be a list of configuration variables / values for each ORG that for replacement that is leveraged just before validation.
Richard Scott
supported this idea
·
-
14 votesRichard Scott
shared this idea
·
Thanks for getting back to me on this. I am curious why these folders are not returning. If we move the templates inside to a folder (other than public) that is visible, they can be deployed.
I have been looking into what the difference between the custom folders are that we can and can't see and i am not seeing any differences yet. I'll let you know if i find something is up on our end.
Thanks.
Richard