With the recent release of Commanding V2, and the ability to make ribbon buttons within PowerApps the use of PowerFX as Show/Hide rules and some onSelect commands looks very useful.
To ensure these can be widely used components within a Library need to be merged when multiple solutions are deployed which add layers to a single Model Driven Application.
At the moment an Application can only have one Component Library for new commands that use Power FX. So if multiple providers/solutions were to add buttons for an Application then these individual Components should all be added to the library as merge behaviour (Similar to formXML/Sitemap or Option Set currently)
Comments
Layering of command buttons is handled as expected (= merged) until a Power Fx is added, and with that a default component library for the model-driven app is created. This component library has to follow the same approach to layering as the model-driven app it is supporting, for this to be a complete solution.
It is a really necessary one in the scenario where a product and product implementations by customers are separate solutions on separate environments, of which product is managed bottom layer and product implementation is top unmanaged layer.
Category: Unified Interface