Dynamics has a new tool to define and configure commands throughout your app, and it's called Command Designer. This tool aims to replace the old "ribbon" button design, now called "classic commands." This was very difficult to customize with code and impossible to customize without. Customizing the ribbon was prone to errors and required development experience to do. Even with development experience, you were quite limited on the functionality of your buttons; what they can do, and where they can navigate a user to. Now, modifying buttons is easy and out of the box, using the new Model Driven App Command Designer.
What are Model Driven App Commands?
Commands are buttons visible throughout a model driven app that users interact with to perform a specific action. These buttons are grouped together in a command bar, which is visible within most areas of an app. For example, in order to Save changes to a record, a user would select the save button in the form's command bar. Command bars are located in the following areas:
- Main Grid: Page showing a list of records when using the left-hand navigation in an App
- Main Form: The form displayed when a record is opened
- Subgrid view: List of records displayed within another record's Main Form
- Associated View: List of records displayed when selecting the Related tab from any record's Form
Classic vs Modern Commands
Because of the challenges with the classic ribbon commands mentioned above, Microsoft decided to rebuild the Command infrastructure. Some key differences in capabilities between classic and modern commands are... (