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

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Suggested Answer

Solutions vs patches....

(0) ShareShare
ReportReport
Posted on by 197
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.
I have the same question (0)
  • Suggested answer
    ManoVerse Profile Picture
    617 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
    3 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,. 

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!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
ManoVerse Profile Picture

ManoVerse 109 Super User 2026 Season 1

#2
Jimmy Passeti Profile Picture

Jimmy Passeti 46 Most Valuable Professional

#3
NeerajPawar Profile Picture

NeerajPawar 39

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans