Solution management: Patches vs Segmented Solutions

(0) Share

Report

Posted on by leonnz

I'd like to get an understanding of the scenarios for when you would use Segmented Solutions vs Solution Patches for small updates e.g. small changes to existing fields.

This may depend on the environment setup, so this is ours:

1x DEV (unmanaged)
2x TEST (managed)
1x PROD (managed)

My initial thoughts are Segmented Solutions in general should be used to introduce new components especially new entities, changes to those entities can then be further patched if needed.

However with Segmented Solutions I could also add existing components then make my small changes, similar to using a patch.

So both can be used to implement minor changes, but what is the best practice?

I have the same question (0)

All responses (1)

Answers (1)

Verified answer

Ankit Sabharwal on at

Like (0)

Report

RE: Solution management: Patches vs Segmented Solutions

Hello,

Your initial thoughts are correct. When you need to add the new components or modifications are large than you can go with segmented solutions. Patches are used when modifications are small. For eg. You need to change the attribute length or you need to add any new value in option set.

This is the article which can illustrate the best practices : https://www.beringer.net/beringerblog/dynamics-365-solutions-patches-best-practices/

Hope this helps.

Best regards,

Ankit

Please mark as verified if the answer is helpful. Welcome to join hot discussions in Dynamics 365 Forums.

Was this reply helpful? Yes No