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

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Model Driven app - Rib...
Power Apps
Answered

Model Driven app - Ribbon customization using XRM Toolbox

(1) ShareShare
ReportReport
Posted on by 226
Hi Community,
I need some clarification on the correct way to move Ribbon Workbench (XrmToolBox) customizations to higher environments.
My Scenario
I need to hide a few command bar (ribbon) buttons in a Model‑Driven App.
I used XrmToolBox → Ribbon Workbench to customize the buttons.
When loading the solution in Ribbon Workbench, it asked me to select a solution that contains only the table + related components (not the main app solution with many objects).
So I created a separate solution that includes:
The specific table
I used this “minimal solution” inside Ribbon Workbench to apply to hide buttons.
My Question,
Now I need to move all the changes to a higher environment (UAT/Production).
I currently have:
Main App Solution:
Contains multiple tables
Forms, views
Business process flows
Model‑Driven App definition
Ribbon Workbench Solution:
Contains only the required table for command bar customization

Do I need to export & import BOTH solutions into the higher environment?
Or is there a better approach so I don't have to move two separate solutions every time?
Is it recommended to:
Keep ribbon customizations in a separate dedicated solution?
OR
Move the command bar changes into the main app solution before export?
Categories:
I have the same question (0)
  • Verified answer
    Sunil Kumar Pashikanti Profile Picture
    2,318 Moderator on at
     
    You do NOT need to move two separate solutions.
    The best practice is:
         Add the Ribbon Workbench customizations into your main app solution
         Then export and import one solution into higher environments.
    You should not keep Ribbon customizations isolated in a separate solution long‑term.

    1. Perform the Ribbon edits in a minimal solution (as you did).
    2. When finished, add the modified table to your main app solution.
    3. Export and import ONLY the main app solution to higher environments.

    Why putting ribbon customizations into the main solution is correct?
    Because Ribbon Workbench modifies:
         Table-level Ribbon (RibbonDiffXml)
         Command definitions
         Display rules & enable rules
    These changes belong to the table, so they naturally belong inside the main solution containing that table.
     
    What to do next:
         Open your Main App Solution in Dev.
         Add the same table you modified (the one with custom ribbon).
         This pulls the RibbonDiffXml into your main solution.
         Export only the Main App Solution as Managed → import into UAT/Prod.
     
    ✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
    👍 Feel free to Like the post if you found it useful.
     
     

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

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
Valantis Profile Picture

Valantis 424

#2
WarrenBelz Profile Picture

WarrenBelz 355 Most Valuable Professional

#3
11manish Profile Picture

11manish 290

Last 30 days Overall leaderboard