The imported solution and the existing solution must both be managed for upgrade.

(0) Share

Report

Posted on by San2019

Brief History:

In Dev, I created a solution, exported it as managed and deployed to PROD

In Dev, in same solution I made some changes, I did clone a patch and added my changes in the patch also, exported the Patch as managed and imported it to Prod

In Dev, I then did Clone a solution, which merged the previous patch and solution into one new solution. I then did Clone a patch and did my changes ONLY in that (as I assumed the Clone a Solution later will merge my changes on one full solution later) and exported the patch as managed solution.

In PROD, as I don't see the option to Clone a solution, I have one main solution, the previous patch solution already. Now when I try to import the latest patch, I get the message: "The imported solution and the existing solution must both be managed for upgrade," but all the solutions in the target environment as managed solutions.

When I check the history, I see the exception: Solution manifest import: FAILURE: Patch version 1.1.1.3 is invalid for parent version 1.0.0.3

How do I resolve this?

Errorcode points to urll: https://learn.microsoft.com/en-US/troubleshoot/dynamics-365/sales/error-code-80048539-when-importing-solution-patch

But neither Symptom 1 nor Symptom 2 in that matches my issue. Symptom 1 does not match, because my patch version is higer than the solution

Categories:

Building Power Apps

All responses (4)

Answers (0)

Sort by

hjaf 487 on at

Like
a
(1)

Report
Copy link

Link copied!

Errors in the Power Platform UI are not reliable and fall back to some default often non-related error.
I got the same error at import, with an option to download the error log file (xml) which says something completely different.
Rajath_mk 95 on at

Like
a
(1)

Report
Copy link

Link copied!

Agree with @hjaf .
I got an error while updating my managed solution. "The imported solution and the existing solution must both be managed for upgrade."

I broke my head for an how. Turns out the Xml doc had a different error - "Attribute rj_so is a Integer, but a String type was specified."

Turns out that deleting a column and creating the same column details but with different data type isnt allowed.
damian_green23 276 on at

Like
a
(0)

Report
Copy link

Link copied!

So, if I deleted a column from the Tasks table called "Category" and then added a column called "Category" in the Tasks table but based it on my Choices, would that be a similar example to the issue you ran into?
If so, how did you resolve it?
Rajath_mk 95 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @damian_green23 ,
I would first make sure there aren't any multiple solution layers in the managed solution as this happened for me. Then i would delete the Category column first and then import to managed. Once it has been deleted in the managed solution successfully, i would add the new category choice column and import the solution once more.

This might have issues if you are trying to do it at once as PowerApps might be confused why there are values within the Category column which should have choices has text values within it.

Make sure you backup the data if you need to reimport it back later into choice columns. Let me know if you have issues.