{"id":93156,"date":"2023-02-14T07:23:37","date_gmt":"2023-02-14T12:23:37","guid":{"rendered":"https:\/\/www.beringer.net\/?p=93156"},"modified":"2023-12-18T10:03:20","modified_gmt":"2023-12-18T10:03:20","slug":"goodbye-ribbons-hello-command-designer","status":"publish","type":"post","link":"https:\/\/www.beringer.net\/beringerblog\/goodbye-ribbons-hello-command-designer\/","title":{"rendered":"Goodbye Ribbons, hello Command Designer!"},"content":{"rendered":"

Dynamics has a new tool to define and configure commands throughout your app, and it’s called Command Designer.\u00a0 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.\u00a0 Customizing the ribbon was prone to errors and required development experience to do.\u00a0 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.\u00a0 Now, modifying buttons is easy and out of the box, using the new Model Driven App Command Designer.<\/p>\n

\"App<\/p>\n

What are Model Driven App Commands?<\/h2>\n

Commands are buttons visible throughout a model driven app that users interact with to perform a specific action.\u00a0 These buttons are grouped together in a command bar, which is visible within most areas of an app.\u00a0 For example, in order to Save changes to a record, a user would select the save button in the form’s command bar.\u00a0 Command bars are located in the following areas:<\/p>\n