Adjust dependancy on managed package versions for Apex[Class|Page]
We've found when developing classes against managed packages the class ...meta.xml includes the package version numbers. Problem is these are fixed to the exact version installed (e.g. 9.4, 9.3 etc. example below)
But then if the managed package is upgraded Salesforce, in its infinite wisdom, doesn't update these so when you come to deploy next time you have to go and manually update all the version numbers - or if you have a different version in another sandbox (to test the newer one) same thing.
Seems like something a cool deployment tool could handle and offer to fix up on deployment.
<ApexClass xmlns="http://soap.sforce.com/2006/04/metadata">
<apiVersion>41.0</apiVersion>
<packageVersions>
<majorNumber>9</majorNumber>
<minorNumber>4</minorNumber>
<namespace>foo</namespace>
</packageVersions>
<status>Active</status>
</ApexClass>
Nigel
shared this idea
-
Bob Hatcher commented
There are several ideas along these lines in this site. This is one of the most frustrating things about deployments and one that Gearset is well positioned to address. PLEASE let me change the metadata for managed package versions, or otherwise smooth over this very annoying blocker.