web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Unanswered

Managed solution import - Component library issue

(0) ShareShare
ReportReport
Posted on by 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:

Solution-History.png

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)
  • RodRodriguez Profile Picture
    on at

    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

  • EBMRay Profile Picture
    905 on at

    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.

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.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
Subra Profile Picture

Subra 144

#2
11manish Profile Picture

11manish 112

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 85 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans