Share
Report
2I'm facing an issue merging two deployable packages in D365 F&O and I need your advice on the best way to resolve it.
Here is the situation:
- NewPackage.zip → registered as Platform Update 70 (PU70)
- OldPackage.zip → registered as Platform Update 41 (PU41), however the models inside it actually have different platform versions (ranging from PU41 to PU65)
- OldPackage.zip → registered as Platform Update 41 (PU41), however the models inside it actually have different platform versions (ranging from PU41 to PU65)
When I try to merge them using AXMergeDeployablePackage.exe, I get this error:
"The package has different release version, which indicates the packages are of different release and will not be able to deploy correctly after merge."
"The package has different release version, which indicates the packages are of different release and will not be able to deploy correctly after merge."
Additional context:
- The OldPackage.zip contains custom models and I do not have the source code for them.
- I cannot ask the vendor to rebuild the package.
- My target environments are UAT and Production, both running PU70.
- Interestingly, the models inside OldPackage.zip are already deployed and working correctly in Production, which suggests the version mismatch in the XML metadata may not reflect the actual compatibility.
- The OldPackage.zip contains custom models and I do not have the source code for them.
- I cannot ask the vendor to rebuild the package.
- My target environments are UAT and Production, both running PU70.
- Interestingly, the models inside OldPackage.zip are already deployed and working correctly in Production, which suggests the version mismatch in the XML metadata may not reflect the actual compatibility.
Given this situation, what is the safest and most reliable way to merge or deploy both packages together on a PU70 environment?
Categories:
I have the same question (0)
All responses (
Answers (
