Karol Macak
My feedback
1 result found
-
82 votes
Merging differences between Apex classes and VisualForce pages is difficult to do automatically due to the understanding required by the developer. For differences between two orgs in other object types, Gearset helps you sidestep that with our granular comparison results. This blog post explains more: https://gearset.com/blog/merging-salesforce-metadata
An error occurred while saving the comment
I just started using Gearset, it have lots of great features, but this one missing for me is big drawback. It will push it to next level, I can imagine it can be based on some permission, so admins can control who can use it, but definitely needed.
I believe this is huge improvements for code, but also for configurations such as apps, lightning record pages, approval process etc.
Some use cases from last days:
I am working on approval process, done all stuff and ready for deployment. In comparison I can see there is some other change which I didn't made. It was work done by my colleague on another ticket and it is also already ready for deployment, so no problem I can deploy. But there can be ongoing work on components and then its almost impossible to deploy only my changes, which are ready for deployment.
Another issue is, that sometimes environments doesn't match same release and some "lines in metadata" are not supported anymore, so without this option again almost impossible.
As workaround I will try to edit metadata locally in VS Code and then compare with my local file, I hope it will work smoothly...