Unanswered

Managing Solution Layering

(0) Share

Report

Posted on by MinotaurGB

Hi,

I have taken on a role with D365 that has been developed by multiple 3rd party suppliers. Over the past few years certain features and customisations have taken place leading to multiple solutions, currently we have around 45-50 solutions using varying objects. It seems that each time a piece of dev work is done a new solution is created.

I wanted to get opinions on what is considered the best way to manage solutions and adding dev work over time. Is it best to have one solution layer or is it ok to have 45+ solution layers ? I think that MS said that keeping the same objects in one layer is the best approach to reduce solution layer dependencies.

Any thoughts and discussion welcome.

Categories:

Building Power Apps

I have the same question (0)

All responses (2)

Answers (0)

Devvj 1,132 Super User 2024 Season 1 on at

Like (0)

Report

Hi @MinotaurGB
I would say that it's preferred to have as little solutions as possible to handle, from a pure ALM standpoint it fast become really hard to manage if you have tons of solutions, which sometimes do crossovers to the same tables/fields etc, resulting in conflicts and what not.
However to have absolutely everything in 1 solution can be pretty heavy as well... End of the day it is a matter of preference.

Was this reply helpful? Yes No
MinotaurGB 8 on at

Like (0)

Report

Thanks for the reply. My thoughts are similar with regards to reducing the number of solutions, it will be a matter assessing how we merge the solutions and deal with any runtime issues and conflicting layers.

Was this reply helpful? Yes No