{"id":31644,"date":"2022-05-23T15:47:59","date_gmt":"2022-05-23T10:17:59","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=31644"},"modified":"2022-05-23T15:47:59","modified_gmt":"2022-05-23T10:17:59","slug":"command-checker-to-debug-ribbon-buttons","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2022\/05\/command-checker-to-debug-ribbon-buttons\/","title":{"rendered":"Command checker to debug ribbon buttons"},"content":{"rendered":"

Introduction:<\/h2>\n

Dynamics 365 CRM have added new features that are helpful for a developer to develop and deliver solutions to clients more quickly. The command checker is one of the features that is used to debug ribbon buttons. This is one of the best features because sometimes adding a button and getting it to work is more challenging work for the developer. When the ribbon button shows an error and does not show then it’s a time-consuming job for a developer to find the cause and resolve the issue. Now with the help of the command checker, the developer can debug the ribbon button customization and easily find the cause of the issue and find the resolution.<\/p>\n

To enable the command checker you need to append &ribbondebug=true<\/strong> in the CRM URL. Copy the CRM URL from the browser and append the &ribbondebug=true <\/strong>and paste the URL in the browser.<\/p>\n

The final CRM URL will look as shown below:<\/p>\n

https:\/\/org90bc3d01.crm.dynamics.com\/main.aspx?appid=a123f692-19c7-ec11-a7b6-000d3a36cee0&pagetype=entitylist&etn=account&ribbondebug=true<\/strong><\/a><\/p>\n

Once you paste the above CRM URL in the browser and hit \u2018Enter\u2019 then the command Checker button will start appearing on the Global Ribbon and Entities home page grid and entities form Ribbons.<\/p>\n

\"ribbon<\/p>\n

Command checker button from entity home page grid ribbon: <\/strong><\/h2>\n

When clicking on the Command checker button from the account home page grid ribbon the following window will open. In that window, it shows all OOB and custom ribbon buttons along with each ribbon button’s properties, and command properties (action, enable rule, display rule). Looking at any ribbon button properties we are able to identify and troubleshoot why the button is hidden because of which Enable rule\/Display rule button is hidden. We can check the rule or if any custom rule with JavaScript then we can debug that function and easily able to find the cause of it and resolve it.<\/p>\n

\"ribbon<\/p>\n

Also, we can get every ribbon button’s information so that anyone can get an idea about the ribbon button. In this way, anyone new to this ribbon button can easily get functionality, and if any issue arises then they can easily troubleshoot and resolve the issue.<\/p>\n

There is a \u2018Regenerate ribbon metadata\u2019 button at the top so that it displays the latest ribbons.<\/p>\n

\"ribbon<\/p>\n

When clicking on the button, it shows the below message and regenerates the metadata in the background.<\/p>\n

\"ribbon<\/p>\n

Global command checker:<\/p>\n

When clicking on the Command checker button, it displays the following window with all OOB ribbon buttons and any custom button that is added to the Global ribbon.<\/p>\n

\"ribbon<\/p>\n

As we can see in the above screenshot, Team Chat button is hidden and we are able to see them due to which the display rule button is hidden.<\/p>\n

Conclusion:<\/strong><\/h2>\n

In this way, with the help of the command checker, the developer is able to easily troubleshoot and resolve ribbon button issues.<\/p>\n

\"Kanban<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Introduction: Dynamics 365 CRM have added new features that are helpful for a developer to develop and deliver solutions to clients more quickly. The command checker is one of the features that is used to debug ribbon buttons. This is one of the best features because sometimes adding a button and getting it to work\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[16,2361],"tags":[1479],"class_list":["post-31644","post","type-post","status-publish","format-standard","hentry","category-dynamics-365","category-technical","tag-ribbon-button"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/31644","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=31644"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/31644\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=31644"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=31644"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=31644"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}