If a field is identified as missing from the deployment and the user agrees to include it, the corresponding field's permission should also be added.2 votes
We did a deployment last week and noticed that as part of the deployment report that went out that it stated the Tests Run was zero. We did a pre-validation the day before where we ran all tests with all passing.
Could this test section on the deployment report again include/include the pre-validation tests that were run for the deployment?1 vote
If you have a piece of metadata that was changed on a comparison then a subsequent comparison using the 'Refresh Comparison' button. The selected item is still selected and unable to be deselected.1 vote
I am not sure if this is an actual issue or not but I will ask the question to see if I am missing something :)
When comparing email templates, the compare will return both email templates and folders. I have noticed that in my case, email templates that are part of a managed folder do not return. We can see the folder and sync the folder settings, but no templates. If we move the templates to a non-managed folder we can see the templates. Has anybody encountered anything similar?
When I remove a page layout from my Git repository (the file and the package.xml entry) and then do a comparison to an org that it still exists in, Gearset fails to detect a deletion. It doesn't even show up in the All objects tab. It happened to me yesterday and then I just reproduced it now.1 vote
CustomObject 'Order' Page layouts from orgs created from orgs prior to V39 may have in the layout metadata <excludebuttons>Activate</excludeButtons>
For V39 (and possibly earlier) orgs, 'Activate' is no longer the OOTB API name for the button with label 'Activate'. The button API name is ActivateOrder. Hence, deployment fails with error "In field: excludeButtons, no such standard action:Activate"
There is no workaround except to exclude the Order layout from the Gearset Selected Objects. This is not a good workaround for a commonly-used OOTB SFDC Standard object.1 vote
However, the number of differences does appear when viewing the same Apex class in APEX view mode.2 votes
When I enable comparing managed packages (e.g. when I have added a field to a managed custom object), I get lots of false positives saying that there are differences in apex code.
On the source org, the code is show as "(hidden)"; on the target it is shown as empty. And Gearset lists this as a change.
Obviously, I know it's not a change, but it adds a lot of clutter to the comparison view.2 votes
We have no way of knowing when the files were last changed on the source control side. Tried only with BitBucket though.2 votes
That is something we should definitely show. We’ve added it to our investigation list to see if it can be added into the app.
- Don't see your idea?