PL 400: Configure commands and buttons (Create model-driven apps)

In the earlier version Dynamics CRM, there was the concept of toolbar which helps in taking action against the record. In Dynamics CRM 2011, Microsoft introduced the ribbon bar which was similar to Microsoft Office.


In Dynamics CRM 2013, Microsoft changed the ribbon bar to a command bar that ran context sensitive commands. Adding a New and Remove button to the command bar is always daunting. Typically, developers use the Ribbon Workbench for these activities, because making changes to RibbonDiffXML is tantamount to solving a complex puzzle.

In the Dataverse, commands are displayed in different ways depending on the table on the client, but command bars are visible in most places. Both the Command Bar and the Ribbon use the same underlying XML data to define which commands are to be displayed, when the commands are enabled and what the commands do.

On July 2021, Microsoft announced new capability regarding Command Designer which have features of Power Fx for expressing powerful low code logic in Model-driven apps.


However, it is still the preview state that may be subject to change, in the command designer window, we can add a new custom button. It also provides the facility to edit/change labels, icons, tooltips and more.



As a new feature Command Designer is showing as promising features and it's preview status as well. With limited capabilities, it becomes much easier to customize command buttons with low-code or pro-code. It supports Power Fx for low code designer visibility and action logic as well as the advanced logic code capabilities of JavaScript. With the combined features of model driven and canvas apps, this is also part of the solution interface that  make more easier in ALM.

Right now, there are below four places we can edit in the command bar:
  • Main Grid
  • Main Form
  • Sub grid View
  • Associated View
Either Create a new model-driven app using modern app designer or Open an existing model-driven app using modern app designer.

Known limitations:
  • Pre-existing classic commands can't be customized within the command designer during this preview. 
  • Not all Power Fx functions are currently supported for commands. 
  • Sharing is currently handled differently in the command designer than with canvas apps.
  • Canvas-based resources such as component libraries must be shared with any user running or customizing the commands. 
  • Microsoft Dataverse is currently the only supported data source when using Power Fx.
  • When we write Power Fx formulas in the command designer, intellisense may sometimes provide recommendations for unsupported functions. It may not show an error for unsupported functions in commanding.
  • Commands and the command component library created from one app can't be added to different apps.
  • Split buttons and flyout menus aren't currently supported.
  • Dynamically populated buttons aren't supported. We don't plan to support these and recommend creating them declaratively.
  • Command checker may not show all relevant information in some scenarios.
Important web links:

Comments

Popular posts from this blog

PCF vs. Web Resources: Choosing the Right Extensibility Tool for Dataverse

Is Debt Prosperity or Trap?

Exam PL-400: Microsoft Power Platform Developer