You’re offline. This is a read only version of the page.
We are in the process of implementing Five9 Adapter on our Dynamics 365 CRM environment. As a part of the solution, a Five9 button is added to all screens. However, we would like to dynamically hide the button depending your Entity Privilege. Using Ribbon Workbench 2016, I created a display rule (EntityPrivilageRule) on the Five9 command for the ApplicationRibbon. However, the rule doesn’t seem to be applying to the 3rd party button.
Other tests performed:
Has anybody run into this issue were display rules don’t apply to the 3rd party button? If so, how were you able to resolve this issue.
Thanks,
Fred
*This post is locked for comments
I have the same question (0)After some addition researching and testing, I discovered a solution. However, I can’t explain why it’s working.
When selecting the “Customize Command” option on a button in RWB 2016, it was creating a command called five9.ApplicationRibbon.Command0.Command. I added a “Display Rule” to dynamically hide/show the button; however, it wouldn’t take affect even though it worked on the entity ribbon. I decided to create a new custom button using the same properties and the Five9 button. I reproduced the same issue using my custom button. I decided to create a new command for my custom button called new.ApplicationRibbon.Command1.Command. I gave it the same Javascript Action and added the display rule. It started working!
Changed the Five9 button command to use my custom command and removed my custom button. The logic works as I expected it. What I don’t understand is, why the application doesn’t recognize the display rule when the command was named five9.ApplicationRibben.Command0.Command?
Share
Report
All responses (
Answers (
4
