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 / Customer experience | Sales, Customer Insights,... / Solutions vs patches....
Customer experience | Sales, Customer Insights,...
Answered

Solutions vs patches....

(1) ShareShare
ReportReport
Posted on by CU31101219-0 217
Hello All,
 
I heard the other day that Microsoft is starting to recommend not using patches, instead just update the main solution and keep moving that form one environment to the other.
 
I would like know the following:
 
If I don't use a patch and just update our core solution and move that to prod, then we notice a big issue in PRD and have to roll back our changes, how do we do that without removing all customizations that are in that core solution?
 
Wouldn't a patch be better to use for this, so that if you push a patch in prd, and notice and issue and need to roll back, you can just delete the patch and it would only remove those changes and nothing else?
 
Please let me know, thank you.
Categories:
Microsoft Dynamics CRM
I have the same question (0)
  • Suggested answer
    ManoVerse Profile Picture
    ManoVerse 1,026 Super User 2026 Season 1 on at
    Microsoft now recommends avoiding patches and instead using solution versioning + full solution updates because patches complicate ALM, layering, and long‑term maintenance.
     
    To answer
    If I don't use a patch and just update our core solution and move that to prod, then we notice a big issue in PRD and have to roll back our changes, how do we do that without removing all customizations that are in that core solution?
     
    you cannot roll back just the change because a managed solution replaces layers, not individual components.
    Your rollback options would be:
    • Re‑import the previous stable managed solution version (the version before your change).
    • This overwrites the updated components and restores PROD to the earlier state.
    This is the standard rollback method in modern Power Platform ALM.
    Patches creates extra layers , create dependency chains which make long term cleanup harder, also patchs does not fully support some newer ALM scenarios (e.g., pipelines). They were useful earlier, but now solution versioning with full updates is cleaner and simpler.
     
    "Wouldn't a patch be better to use for this, so that if you push a patch in prd, and notice and issue and need to roll back, you can just delete the patch and it would only remove those changes and nothing else?"
    Yes, technically. If you push a patch and delete it in PROD, only the patch changes are removed but microsoft is pushing standardized ALM via full solution versions not patch-based layering because it’s more predictable and easier to automate

    Microsoft provides this guidance directly in their ALM documentation. The key statement is here

     

    Using clone a patch and clone solution to update a solution isn't recommended because it limits team development and increases complexity when storing your solution in a source control system

    Create patches to simplify solution updates with Microsoft Dataverse - Power Platform | Microsoft Learn

    Hope this clarify.
     
    Regards,
    Manoj
    ✅If this answer helped you, please consider marking it as Verified, it really helps others in community
  • Upen Waghela Profile Picture
    Upen Waghela 9 on at
    And on top of that, importing full solurtion is taking hour+ time on complex projects. 
    But I still follow MS suggestion to avoid patch imports and so far so good,. 
  • CU31101219-0 Profile Picture
    CU31101219-0 217 on at
    If I push our main solution into prod and then there is an issue, you are saying that I would need to reimport the older package version that I know works back into prod so that would overwrite what is there, correct?  If yes, wouldn't it error out, as it is a lower version of what is there in PRD now, because the new version just got imported?
  • Verified answer
    ManoVerse Profile Picture
    ManoVerse 1,026 Super User 2026 Season 1 on at
    re‑import the previous stable managed version using the Upgrade process , this does not cause a version‑number error because managed upgrades allow restoring an older version by replacing the newer one. This is exactly why Microsoft recommends full solution versioning instead of patches, it keeps ALM clean, avoids extra layering, and lets you roll back safely by importing the last good solution version.

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!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
11manish Profile Picture

11manish 176

#2
ManoVerse Profile Picture

ManoVerse 158 Super User 2026 Season 1

#3
Jimmy Passeti Profile Picture

Jimmy Passeti 57 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans