Customer experience | Sales, Customer Insights,...

Error on importing a patch out of order

(0) Share

Report

Posted on by Yagasoft

240

Hello,

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?

All responses (3)

Answers (0)

Sort by

Suggested answer

Leah Ju Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi Partner,

Based on the following Microsoft documentation:

https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/use-segmented-solutions-patches-simplify-updates?view=op-9-1#create-a-patch-for-an-unmanaged-solution

Each subsequent patch has a higher build or revision number than the preceding patch.

This documentation also said:

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
Yagasoft 240 on at

Like (0)

Report
Copy link

Link copied!

Hello, Leah,

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.
Suggested answer

Leah Ju Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi,

The version number: <major>.<minor>.<build>.<revision>

As the documentation said:
Each subsequent patch has a higher build or revision number than the preceding patch.

So you need import patch(v1.0.1.1) before importing patch (v1.0.3.1),because the latter is a higher build number.

Join the conversation

Community site session details

Error on importing a patch out of order

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Women in Power Builds Momentum

Congratulations to the September Top 10 Community Leaders

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates

Community site session details

Error on importing a patch out of order

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Women in Power Builds Momentum

Congratulations to the September Top 10 Community Leaders

Subscribe to this forum!

Select categories

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates