Anyone have experience with long running solution imports?

(0) Share

Report

Posted on by mazma

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

All responses (1)

Answers (0)

Suggested answer

RodRodriguez on at

Like (0)

Report

RE: Anyone have experience with long running solution imports?

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.