Share
Report
188About 4 months ago I have inherited the responsibility as the administrator of my companies CRM 2013 On Premise application. Most everything in CRM Seems fairly straight forward but occasionally I run across some things that the previous admin did that seem questionable.
For example one of the managers requested that the export to excel button be removed from a ribbon about a year ago. Now its circling back around to me due to some of the processes they need require to have this button. I am now tasked with bringing this button back and applying a display rule to check to ensure the read permissions are set to Organization for the custom entity before it will show the button.
It appears that the previous Admin created a new solution on top of the initial solution, which contained all of the entities with the initial rollout. However, In this new solution is two entities the Custom entity we will call it X and Application Ribbon entity We will call it AR. Inside the Ribbon Workbench I am able to see that X indeed does not have the Export to Excel button. However, AR does have the button.
As a bit of a hack I was able to copy the XML from AR into X and published and it almost seems like it published both X and AR with nothing duplicated. I say that because it brought back Export to Excel which was on AR but also had a button on it that was in X but not AR. So essentially it worked but when I pulled down the solution again in ribbon workbench X still didn't have the button located up in the designer and the XML Looked very reduced compared to what is in AR.
I published it again to ensure the result I was seeing was based on what I was seeing currently in the Ribbon Workbench. Redundant, I know. The result was the same; the button was back.
Since I know that the button was coming from AR I attempted to create a display rule as seen below.
After making this addition I had a test user that only had User Level Read Permission for X to see if they could see it. Success, they couldn't see it. I then elevated their role to a role that had organizational level Read Permission for X and had them check again. This time they still couldn't see it. I, with Admin privileges, could still see it.
I've tried a few variations for the configuration of the rule with no success. Can anyone see if I am missing anything?
Any help would be greatly appreciated.
*This post is locked for comments
All responses (
Answers (
