Managed solution import - Component library issue

(0) Share

Report

Posted on by EBMRay

905

Hello,

I have an unmanaged solution in a DEV environment where for some reason I have deleted the component library for the model-driven app. After that, I created a brand new component library from scratch, published the solution, exported the solution as managed to import it back into my PROD environment to apply the new upgraded version.

After waiting for 41 mins, I got that the solution had failed with the following error message:

I have already removed the old component library from my source environment, as we cannot have two component libraries for one model-driven app.

The solution is managed and I don't want to delete it in PROD because I have live data.

What will be the solution to this problem to force remove the component library from the production, and re-import the one exported from the DEV environment?

Do we have to investigate in the customizations.xml of the solution or a Web API that deletes the component library or a tool on xrmtoolbox that removes that from the prod environment?

Any help is greatly appreciated.

Thank you!

I have the same question (0)

All responses (2)

Answers (0)

RodRodriguez on at

Like (0)

Report

Have you tried bringing in the managed solution as an update instead of an upgrade?

Also, if you happen to have an unmanaged version of that solution with the old component library in it, you could bring that into the dev environment and use that in place of the one you rebuilt from scratch

Was this reply helpful? Yes No
EBMRay 905 on at

Like (0)

Report

RodRodriguez

The update operation will make it work as it will add the new component without deleting the old component. However, I don't want to keep on updating the solution because the components or anything else that is not needed should be removed.

In the DEV environment, I removed the old component library by using the Web API to delete it from the MOdel-driven app element table. This was successfully removed. I tried the same process in the production environment before importing the solution from the DEV environment but it failed with that error message 3 times.

Was this reply helpful? Yes No