I have a solution to which I created three patches, a patch for each change I am making.
Base Solution v1.0.0.1
Patch 1 v1.0.1.1
Patch 2 v1.0.2.1
Patch 3 v1.0.3.1
I deployed patch 3 first when it was ready. Now when I try to deploy patch 1 or 2, it fails with the following error: /Solution /Patch 2/ failed to import: Solution manifest import: FAILURE: Patch 'BaseSolution_Patch_b6f333ad' has a matching or higher version (1.0.3.1) than that of the patch being installed./.
Every information source I could find confirmed my knowledge that patches can be deployed out of order. Has anything changed in the platform, or am I missing something, please?
Thank you for sharing details about the mechanics of solution patching.
Indeed, I know the basic mechanics of it all. However, I have an issue with the ordering when importing into the target environment: I want to import out of order. To clarify, I want to import a newer patch (e.g. v1.0.3.1) and then an older one (v1.0.1.1) for the same base solution version on both environments.
If a solution has patches, subsequent patches must have a numerically higher version number than any existing patch for that solution.
I hope you can mark my answer verified if it is helpful! If you have any questions, please feel free to contact me. Regards, Leah
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.