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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics 365 | Integration, Dataverse... / Anyone have experience...
Microsoft Dynamics 365 | Integration, Dataverse...
Suggested Answer

Anyone have experience with long running solution imports?

(0) ShareShare
ReportReport
Posted on by mazma 10

This is more of a general question and whether anyone else has had a similar experience and what they did to remedy. We have currently split our customisations into multiple managed solutions for deploy. Like the below:

1. PCF controls

2. Webresources (js & images)

3. Customisations ( entity's, fields, forms, views, business rules)

4. Processes (flows, workflows, plugins)

However we have now got to the stage where our customisations solution (3) takes over an hour to import and upgrade. 

Any suggestions or things to look out for?

Thanks

I have the same question (0)
  • Suggested answer
    RodRodriguez Profile Picture
    RodRodriguez on at

    Howdy Mazma,

    As solutions become more complex they can take more and more time during import.  One thing to consider is what *kind* of import you are doing.  If the import you are bringing in is only ADDING or CHANGING elements in the solution, consider doing an "update" instead of an "upgrade" on solution import.

    Upgrades are the only way to delete or remove elements in a solution.  Because of that, upgrades are very expensive given that the system executes a full install of the new version and a full deprecation of the old version (more details: docs.microsoft.com/.../solution-concepts-alm).  Those operations can take time if the affected entities/tables are under use, given that the system will take longer to acquire schema locks, resulting in higher deployment times.

    If you are not deleting anything, try using an update instead. Compared to upgrades, updates are lightweight and result in an "append only" behavior. In other words, the system will only apply what changed. The only "problem" with updates that the system cannot deprecate components via Update operations. For such cases, customer can schedule a single Upgrade for deprecation, then keep a consistent Update mechanism for the rest.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

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

#1
Pallavi Phade Profile Picture

Pallavi Phade 102 Super User 2026 Season 1

#2
ManoVerse Profile Picture

ManoVerse 58 Super User 2026 Season 1

#3
Abhilash Warrier Profile Picture

Abhilash Warrier 55 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Welcome to the Microsoft Dynamics 365 forum!
Identifying an Org as CDS or Dynamics
Get batch job history log from D365 FO to Power Automate
Gross and Net Weight of Shipments feeding back into Sales Order (from External Source)

Product updates

Dynamics 365 release plans