Please enable JavaScript.

Coggle requires JavaScript to display documents.

Solution Containers for customizations (apps, flows, tables, etc.). …

- - - - use a managed solution with a custom publisher
- - - - Digit 4 = Revision
        Name = Cloned Patch
        Every clone of patch
        1.1.1.1
        
        Controlled by System
    - - Controlled by System
- - - - ex: Default tables like Account, Contact
- - - - Go to Power Apps.
      - Select the correct environment.
      - Navigate to Solutions in the left navigation pane.
      - Click on + New Solution.
      - Provide a name, publisher, and version for your solution, and click Create.
- - - - Export as managed (for production) or keep as unmanaged
        
        Import
        
        when importing a managed solution upgrade into an environment (e.g., from UAT to Production).
        
        Stage for Upgrade
        
        Stage for Upgrade" = Safety Net: It allows you to test the new solution in the live environment before permanently deleting the old version, giving you a rollback option.
        Phase 1 – Stage: New version added on top, old version still present.
        Phase 2 – Apply: Old version and patches removed once confirmed.
        Why: Enables rollback if issues arise post-import.
        Overwrite Customizations" = Cleanliness: It ensures your imported solution is the authoritative source, removing any direct, unmanaged changes made in the target environment that might conflict.
        For managed solution upgrades to UAT or Production, always use "Stage for Upgrade" + "Overwrite Customizations.
        
        Import into test/prod, layering on top of existing solutions
        
        After importing a Managed solution (in UAT/Prod).
        
        This typically refers to initial post-deployment setup steps that cannot be fully automated or packaged within the solution itself.
        
        Set values like connection references to be linked to the actual connections,
        unique keys to be entered for external service integration, or variables to be mapped to values, that can’t be hardcoded. this makes the newly deployed "Managed Solution Layer" fully functional in its new environment.
        
        3 more items...
        
        during solution import** (especially managed solutions)
        Merge vs. Top-Wins Behavior
        especially when troubleshooting unexpected behavior after an import and whenever Dataverse is trying to resolve conflicts between components defined in different layers. It's how the Runtime Layer is ultimately determined.
        
        Top-Wins Behavior
        
        Top layer completely replaces lower ones.
        
        Applies to: Tables, fields, views, canvas apps, business rules, workflows, plugins, Power Automate flows, etc.
        
        Merge Behavior
        
        Combines changes from multiple layers.
        
        Applies to: Model-driven apps, Forms, Sitemaps.
      - Before exporting your unmanaged solution for deployment (especially for patches or minor version updates).
        
        Solution Segmentation
        
        Export only updated components (not full tables/entities).
        
        Smaller files, faster imports, avoids overwriting unrelated customizations. fever sideeffects.