Dynamics Community Forum Thread Details

Can command bar customizations be packaged in a separate solution?

We have a Power Apps / Customer Insights setup where the main app is Customer Insights, and we maintain a separate solution for a custom campaign management module. This module includes its own table, form with PCF control, related views, and other components, and the goal is to deploy this solution across multiple environments that each use Customer Insights as the host app.learn.microsoft+1

The issue is that for command bar customization, including custom buttons, JavaScript actions, and formula-based behavior on existing buttons such as Save, I have only been able to configure it directly inside the Customer Insights app instead of fully inside the separate module solution. I also noticed that a component library object was created in the solution when using modern commanding / Power Fx, so I would like to understand whether that can help make the command bar customizations portable across environments.forwardforever+2

Is there a supported way to keep command bar customizations, including new commands and changes to existing commands, at the level of the separate solution so that the full module can be distributed to different Customer Insights environments without manually reapplying command bar changes in each app? From the documentation, it seems commands and the command component library created from one app cannot simply be added to different apps, which is exactly the limitation I am trying to overcome.

Is there a supported way to package and distribute the full command bar customization as part of the separate solution so that it does not need to be manually recreated in each target app?

Categories:

Dynamics 365 Customer Insights - Data

There is no supported way to fully package and reuse all command bar customizations inside your separate solution for Customer Insights, main reason is that modern commanding (Power Fx–based buttons) is tied to a specific app, not just the solution. So even if your module (tables, forms, PCF controls, etc.) is portable, the command bar changes are not.
command component library created with modern commanding does not make things reusable across apps. It only stores logic but still depends on the app where it was originally configured, so it cannot be easily reused in other Customer Insights apps.

Changes to existing buttons (like Save) and most command configurations must be set up again in each app when using modern commanding (Power Fx), because these customizations are app-specific by design.

The only option that works well across environments is classic command bar customization (RibbonDiffXml), which can be included in solutions and deployed consistently but it does not use modern Power Fx.
In practice, this means your solution can carry all core components, but you will still need manual or scripted steps per environment for command bar setup.

Quick Links

Subscribe to this forum!