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

Post a Comment

Popular posts from this blog

Exploring the Differences: Managed vs. Unmanaged Solutions in Dynamics CRM/Dataverse

Image
In Dynamics CRM/Dataverse, solutions are central to Application Lifecycle Management (ALM) , providing a structured way to manage, package, and distribute customizations across environments. Microsoft uses solutions to transfer apps and customizations by exporting them from one Dataverse environment and importing them into another.  Each solution is authored and maintained by a publisher and includes components like Power Apps (canvas and model-driven), flows, entities, forms, connectors, web resources, and configurations—excluding business data. Solutions streamline ALM practices within Microsoft Power Platform. In Dynamics CRM/Dataverse, there are two types of solutions: Managed and Unmanaged . When planning an implementation, it’s important to understand the advantages and disadvantages of each to make an informed decision. Let’s explore both types to determine the best approach for development and deployment. In Dynamics 365 CRM, a managed solution is a fully packaged solution ...
Read more

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

Image
Extensibility refers to the ability to be extended or augmented beyond the default capabilities of the platform. This involves customization but also includes more advanced techniques, such as coding, integration with external services, and the use of custom components. In the context of Power Platform and Dynamics CRM, the term "extend behavior" refers to the ability to customize and extend the functionality of the platform to meet specific business needs. Extensibility often requires technical skills, such as coding in JavaScript, C#, or using tools like Azure Logic Apps and Power Automate for complex integrations. Customization  is a subset of extensibility. Customization involves configuring and modifying existing elements within the platform to suit specific business needs. Extensibility, on the other hand, covers a wide range of functions and techniques, including customization and more advanced development and integration tasks, to extend the capabilities of the Power ...
Read more

Effective Strategies for Debugging Plugins in Dynamics CRM

Image
In a recent interview, I was asked about debugging plugins in Dynamics CRM. The interviewer specifically wanted to know my approach to plugin debugging. In response, I mentioned using the Plugin Registration Tool profiler. However, I later realized there are multiple methods to debug plugins in Dynamics CRM/Dataverse, each essential for efficient troubleshooting. Debugging plays a crucial role in development, and having a solid understanding of various debugging approaches can help streamline issue resolution in Dynamics 365. Here, I'll explore different techniques for debugging plugin code. There are below options to use in the plugin in Dynamics CRM/Dataverse ITracingService : In Dynamics CRM plugin development, ITracingService is a service provided within the plugin's execution context that logs information for tracing and debugging. It allows developers to capture real-time. Plugin Profiler : A plugin profiler in Dynamics CRM (or Dataverse) is a debugging tool in the Plugi...
Read more