Eric Kintzer
My feedback
170 results found
-
2 votes
-
4 votes
Thanks Mike for submitting your idea.
Gearset's Environment Variables feature already supports partial string replacements, which means you can get Gearset to replace 'sandbox1' bit of the <user> tag value with 'sandbox2', as follows:
Target: Sandbox2
Metadata Type: Platform Event Subscriber Configuration
Item: Any item
Find: sandbox1
Replace with: sandbox2
-
4 votes
-
2 votes
-
1 vote
-
2 votes
-
12 votes
An error occurred while saving the comment -
2 votes
An error occurred while saving the comment More specifically, if metadata filter includes: CustomObject+Profiles+Perm Sets and, in the Comparison results page, user selects only Fieldsets ...
- The Analyzer detects missing Custom Fields
- The Analyzer does not then recurse and detect the missing FLS for those fields -
2 votes
-
9 votes
An error occurred while saving the comment the generalization of this is metadata whose apiName changes
-
13 votes
All - please let us known in the comments which metadata types you would like us to support next with precision deployments. Thanks
An error occurred while saving the comment agree w/ the other suggestions + CustomApplication - especially profileActionOverrides
-
4 votes
-
6 votes
-
2 votes
An error occurred while saving the comment PermComparator can do this job for you - see https://perm-comparator.herokuapp.com/
-
5 votes
An error occurred while saving the comment This issue also occurs during validation runs in Pipelines. I'd be happy if I could a) specify the log levels (apex info, db info, etc) + b) enumeration of the failing tests so I could rerun the validation and capture just the debug logs I care about.
Turning debug logs on unconditionally for the unit test or validation jobs is not desired as they can cause the runs to exceed CPU time.
Even cleverer would be for Gearset to identify the failing tests and rerun those with pre-configured debug logging so results would be available for inspection
-
4 votesUnder review · 2 comments · Help us improve Gearset » Comparisons and difference visualization · Admin →
An error occurred while saving the comment this idea was written before PB was deprecated by SFDC;
-
4 votes
An error occurred while saving the comment There's another use case for this -- sometime in the future, hopefully, Gearset will enable scratch orgs to be created pre-populated with metadata AND test data. (see sfdx force:data:tree) If we can populate VCS with sample test data from a dev org then this enables the scratch orgs to be easily constructed fuly-formed and ready-to-go
-
8 votes
An error occurred while saving the comment "reminder to activate a flow" is a great idea; same for adjust custom metadata records or edit various other Settings
-
5 votes
-
12 votes
and where such dedicated page allowed for mass deletion (via check boxes) of filters you no longer care about. Right now, we have to do this 1x1