Controlling Menu Items visibility with Role.

(0) Share

Report

Posted on by Sabarish

Hi All,

I have a quick query and your thoughts this will be helpful. There is a MenuItem in customer UAT environment which is currently visible, their requirement is to make this Menu Item not visible in production. I can set visibilty to No in Production, but setting it to No will revert changes when they do their next deployment from UAT.

I thought of creating a Role e.g: RestrictedRole and add these menuitems to it, and not give permission to any user. I tried doing this but it was not helpful.

I would like to know if there are any more thoughts around it.

Regards

Sabarish

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (2)

Suggested answer

Community Member on at

Like (0)

Report
Copy link

Link copied!

Hi Sabarish,

You need to control the access point to that menu item and ideally this should be controlled on all privileges having access to that menu item.

You can also refer to Andre's blog for good insights to managing AX security

kaya-consulting.com/ax-2012-security-development-tool-part-1

Regards

Was this reply helpful? Yes No
Sabarish 80 on at

Like (0)

Report
Copy link

Link copied!

I want to do this for 2 menuitems.

Sure I will mark the answer Verified if it answers my question.

Was this reply helpful? Yes No
Suggested answer

Vilmos Kintera 46,149 on at

Like (0)

Report
Copy link

Link copied!

Security changes through the System administration module are actually modifications within your AX AOT. It is not a task for a functional consultant to carry this out, that is why you are losing your changes with the next modelstore deployment - since AOT is replaced from the source environment, where the changes should have been carried out in the first place.

Please tell the requirements to your technical team and let them implement it properly, by checking which security privileges are using the menu items in question and limiting access to those.

Was this reply helpful? Yes No
Sabarish 80 on at

Like (0)

Report
Copy link

Link copied!

Hi Vilmos, the requirement is a bit out of box for the client. Basically in UAT they want these 2 menuitems to be visible and functional. When they come to Prod they want to restrict this MenuItem completely from the AX System.

Was this reply helpful? Yes No
Verified answer

Basheer17 2,720 on at

Like (0)

Report
Copy link

Link copied!

You can export xpo's of required roles from UAT keep a backup and change their access level to No access for required menu items, this restricts access during Production deployment. Since you want these menu items in UAT, importing those exported xpo's should be added as a step to your UAT deployment activity.

Was this reply helpful? Yes No
Verified answer

Vilmos Kintera 46,149 on at

Like (0)

Report
Copy link

Link copied!

It does not matter which environment it is, Security changes are a technical task. In case you want it to behave differently for different environments, you might have to add additional steps to your environment cloning process as suggested by Basheeruddin.

For example we are running a job after each Production->Test system clone, which does a lot of cleanup i.e. removing batch jobs, changing proxy account, AIF port trusted intermediary users, etc.

You could do a similar practice, where you modify the security treenodes with simple reflection within the X++ job to add/remove those menu items as per your requirements.

Was this reply helpful? Yes No
Suggested answer

Sabarish 80 on at

Like (0)

Report
Copy link

Link copied!

Hi Basheeruddin,

Thanks a lot for the suggestions. I will follow this suggestion.

Was this reply helpful? Yes No