function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
LSKozLSKoz 

Migrating package that references another package

I've got this problem of having a load of cls-meta files that reference another managed package. It won't install into the target organization because the "specified package version does not exist".

 

I do have the package installed in the target org, but a higher version. I would usually assume that this would be fine.

 

Does anyone have any ideas on this? It would be a pain to have to keep running through every cls-meta file and removing the reference to the other managed package.

 

Thanks

Ashish_SFDCAshish_SFDC

Hi LSKoz,

 

Please see the considerations that I can think of, 
How are the components in the Higher Version managed package different from the previous version?
Is the difference being tacked in the current managed package?

Regards,
Ashish, Salesforce.com