[Background]

In Dynamics 365 (model-driven apps), you can't directly customize standard buttons using the built-in features, so we use Ribbon Workbench to make customizations.

This time, we needed to hide the standard button 'Add Product', so we set it to be hidden using HideCustomAction.

[The content of the problem]

We applied the above settings and tried exporting/importing them to another environment as a solution, but we found that the hidden settings weren't applied in the destination environment. 

After looking into it, we think the issue comes from the following points:

• The 'Add Product' button is internally displayed twice

• There might be multiple buttons with the same ID

• It's unclear which button HideCustomAction is applied to

Because of this, the customization doesn't get applied to the intended button, and as a result, hiding it fails.

[Current workaround]

At this point, the following actions are needed:  

• Directly edit the XML of the exported solution  

• Delete unnecessary CustomAction attributes from duplicate button definitions  

However, this approach has the following issues:  

• Manual XML editing is required, which is a heavy operational load  

• There's a risk of accidental edits  

It's an unnatural workaround as far as standard product behavior goes.

[Improvement request]

I strongly hope for one or more of the following improvements:  

• I want the product side to ensure that there aren't multiple buttons with the same ID.  

• I want HideCustomAction to reliably apply to the intended targets.  

• I want the logic for determining which buttons to render on the command bar to be clarified.  

I also want customizations to consistently reproduce even when moving between environments.