Ribbon button/flyout deletion using unmanaged solution import is failing to delete the component

(5) Share

Report

Posted on by Kaushik Kaul

All,

Just a heads-up to D365 community forum members - due to a recent change in the Ribbon/Commanding infrastructure, ribbon button/flyout deletion using unmanaged solution import is failing.

Issue:

Exporting a ribbon button/flyout as unmanaged solution , deleting the button/flyout and re-importing it will not remove the customization

Mitigation:

Export unmanaged solution
Open customizations.xml
Find the button/flyout you want to hide. Instead of removing the button/flyout, go to the definition of the command for the button/flyout
In the command definition, under Enable Rules, add
<EnableRule Id="Mscrm.Disabled" />

We ,on D365 side, have a fix in place for this issue. While the fix is getting deployed worldwide, use the above mitigation to remove the ribbon button/flyout from UI

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

ScottDurow 21 on at

Like (1)

Report

Thank you for posting this update - it’s really appreciated.
Community Member on at

Like (0)

Report

Are the Commands affected by this Bug as well? I have several Commands and i am not able to delete them. If i delete them and publish the Solution, the Commands are "back".

Thank you!
Kaushik Kaul on at

Like (0)

Report

Yes, commands should be affected as well. The fix should be deployed to production now. Can you please confirm if you are still seeing this issue
Community Member on at

Like (0)

Report

Hello Scott,

I am having similar issue, i manually deleted duplicate buttons using ribbon workbench and published. Below is the error it gave when i tried to publish. Now it is saying there are 2 tabs with same name , but i am not able to do anything with tabs.

Tab names are displaying one below other , when i try to select anyone , nothing it is showing. Can you please help me. Below is the error i got when i tried to publish. Thank you .

There are validation errors: 1. Duplicate Group ID detected and removed 'exp.Experlogix.quote.form.MainGroup.CustomAction' 2. Duplicate Group ID detected and removed 'exp.Experlogix.quote.grid.MainGroup.CustomAction' 3. Duplicate Group ID detected and removed 'fei.Experlogix.quote.form.MainGroup.CustomAction' 4. Duplicate Group ID detected and removed 'fei.Experlogix.quote.grid.MainGroup.CustomAction' 5. Duplicate Button ID detected and removed 'fei.Mscrm.Form.quote.Assign.CustomAction' 6. Duplicate Button ID detected and removed 'fei.Mscrm.Form.quote.Delete.CustomAction' 7. Duplicate Button ID detected and removed 'fei.Mscrm.HomepageGrid.quote.DesignView.CustomAction' 8. Duplicate Button ID detected and removed 'fei.Mscrm.SubGrid.quote.AddExistingAssoc.CustomAction' 9. Duplicate Button ID detected and removed 'fei.Mscrm.SubGrid.quote.AddExistingStandard.CustomAction' 10. Duplicate Button ID detected and removed 'fei.Mscrm.SubGrid.quote.AddNewStandard.CustomAction' 11. Duplicate Button ID detected and removed 'fei.quote.ActivateQuote.Button.CustomAction' 12. Duplicate Button ID detected and removed 'fei.quote.Button1.Button.CustomAction' 13. Duplicate Button ID detected and removed 'fei.quote.Button2.Button.CustomAction' 14. Duplicate Button ID detected and removed 'fei.quote.Button3.Button.CustomAction' 15. Duplicate Button ID detected and removed 'fei.quote.Button4.Button.CustomAction' 16. Duplicate Button ID detected and removed 'fei.quote.Button5.Button.CustomAction' 17. Duplicate Button ID detected and removed 'fei.quote.Button7.Button.CustomAction' 18. Duplicate Button ID detected and removed 'fei.quote.Button8.Button.CustomAction' 19. Duplicate Button ID detected and removed 'fei.quote.CreateOrderEntity.Button.CustomAction' 20. There were 2 tabs with the ID 'Mscrm.Isv.quote.Form'. Rename them to be unique. Check the messages tab for the quote entity
Justin Wilkinson 1,338 on at

Like (0)

Report

I am having the exact issue, it has duplicated my ribbon commands and display rules- when I try to remove them it errors> any thoughts?