web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Override Permission functionality doesn't override Entry Point Access Level

(0) ShareShare
ReportReport
Posted on by

I have a menu item X pointing to a form that has 2 datasource tables: Y and Z. I created a role having only 1 permission. This permission has only X menu item added as an entry point and its access level is Read/View.

When I override Permission for Y and Z tables as and set Full Control / Delete, the users having only the above-mentioned role still have No Access to the form.

I tried overriding permissions from the client side System administration > Security Roles > Override permissions form. Also did it from the AOT: I added the tables on the Permissions > Tables node of the role.  The result is the same.

Y table has a few tables in delete actions, I also overrode permissions for these tables and set them as Full Control / Delete. But the result is still the same.

Do you know what could cause such functionality? My understanding is that overriding permission should overshadow the entry point access level.

I'm using Security Development Tool to test the role.

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    on at

    *When I override Permission for Y and Z tables and set Full Control / Delete, the users having only the above-mentioned role still have Read/View to the form.

  • Sohaib Cheema Profile Picture
    49,515 User Group Leader on at

    I have tried to replicate the issue, and I can confirm that issue is not reproducible. It is working, not in the way you mentioned. Instead its acting as it should. Following is what I did for testing

    1. Created tow sample Tables

    2. Created a form and added sample tables as data source.

    3. Create a display menu item

    4. Added this menu item to a new privilege( has Read access)

    5. Create a new security role and added newly created privilege into that role.

    6. Assigned newly created role to user.

    7. Opened ax client and user was able to VIEW only records.

    8. Went back to system admin mode in ax, and overridden permissions of two tables for newly created role. From view to I mead Full access.

    9. Went into AX with test user and I were able to delete/create/update records.

       

    you may be missing something fishy.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Season of Giving Solutions is Here!

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
TAHER Mehdi Profile Picture

TAHER Mehdi 3

#2
Martin Dráb Profile Picture

Martin Dráb 2 Most Valuable Professional

#2
Nakul Profile Picture

Nakul 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans