Dafydd Johns
My feedback
8 results found
-
25 votes
An error occurred while saving the comment -
16 votes
-
6 votes
An error occurred while saving the comment As a Salesforce partner, we use gearset across a number of different clients. Given there is a bug in how a deleted field's permission to not appear at top level in a comparison (but do when you expand a profile or permission set), getting other dependencies to be delted is tricky or time consuming. Repo cleaner had been a bit problematic in the past (a bit like the problem analyzer can CAUSE problems for CI jobs), so either having a way to accept actions or to enable this on a per project level would be great.
-
7 votes
-
9 votes
-
1 vote
-
1 vote
-
1 vote
The Knowledge Article about custom object permissions begins to explain well what the issue is, but I just thought I was missing something. Why can't Gearset, with knowledge that certain permissions are not returned when set to false, just explicitly set them. The article seems to suggest that it just isn't possible.
Because we typically work with a selective scope of metadata in source control, we don't deploy deletions, but annoyingly any second deployment sees these as deletions (rather than a change) so never go through (even though Gearset knows that the lack of existence of a tag means it is false)