Monica Thornton
My feedback
10 results found
-
1 voteMonica Thornton
shared this idea
·
-
1 voteMonica Thornton
shared this idea
·
-
2 votesMonica Thornton
supported this idea
·
-
6 votesMonica Thornton
supported this idea
·
-
4 votesMonica Thornton
supported this idea
·
-
5 votesMonica Thornton
shared this idea
·
-
4 votesMonica Thornton
shared this idea
·
-
4 votes
An error occurred while saving the comment Monica Thornton
supported this idea
·
-
1 voteMonica Thornton
shared this idea
·
-
2 votesMonica Thornton
supported this idea
·
I'm not sure if this feature has evolved over time but we are able to deploy if managed package versions are different, however if "Installed Packages" type is included with the namespace and the versions are different, the comparison ignores any objects in that namespace. This is currently the most common training issue and troubleshooting issue the teams I'm working with currently encounter when using Gearset. The fix is simple for us, we have to upgrade the packages to match versions, which is internally a recommended pre-deployment step, however it takes time and is easily missed as our Product team is continuously upgrading Production orgs.
It would be ideal to have some sort of package version detection or intelligence in the Compare step as the batches come in and are displayed, or during the Problem Analysis step, that states 'x Package versions are different, not all metadata may be available in your comparison.' or something similar.