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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Security: form read-only, except two fields

(0) ShareShare
ReportReport
Posted on by

Hi

I'm trying to achieve the following for a user role. The user needs to have read-only access to the Supplier Form. Except that the role should be able to change the Primary Contact and the Default Vendor Bank Account.

How do I achieve that? In old AX 2009 you could drill down to the table level and arrange this there. But that seems to no longer be an option in AX 2012? Detailed instructions appreciated :-)

Yours


Abaw

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Mahmoud Hakim Profile Picture
    17,887 on at

    just override permission for this role and override permission for this table, set permission for every field as you need as the below

    2728.12.png

  • Community Member Profile Picture
    on at

    Hi Mahmoud

    Thank you for your time.

    I tried this but the field continues to be greyed out. The role has the VendTableView privilege and I have modified the VendTable table through Override Permissions. The table itself has been set to "Edit", all its fields to "view", except the BankAccount field, which is also "Edit".

    What am I doing wrong?

  • Mahmoud Hakim Profile Picture
    17,887 on at

    can you share print screen

  • Verified answer
    Chaitanya Golla Profile Picture
    17,225 on at

    Hi,

    I assume you have added VendTableview security privilege to the user role(Path: \Security\Roles\<RoleName>\Privileges\VendTableView) and added table VendTable to the tables Node and included field BankAccount with effectiveAccess set to update for both table and field.

    Path:  \Security\Roles\<RoleName>\Permissions\Tables\VendTable - EffectiveAccess property to Update.

             \Security\Roles\<RoleName>\Permissions\Tables\VendTable\BankAccount - EffectiveAccess property to Update.

    If you have done above setup and still not working, you can add the form fields from form VendTable by adding it to the Forms Node and set its effectiveAccess property to Update.

    Path: \Security\Roles\<RoleName>\Permissions\Forms\VendTable\BankAccounts(controlName) - EffectiveAccess to Update.

    Set NeedePermission to yes on BankAccounts control.

  • Community Member Profile Picture
    on at

    Hi Mahmoud

    Hereby the screenshots of the form and the AOT set up.

    My working hypothesis at the moment is that the EDIT button is throwing a spanner in the works. I tried your recommendation on a different form (VAT Codes) and there it works flawlessly.

    7206.AOT.JPG

    7206.AOT.JPG

  • Community Member Profile Picture
    on at

    Hi Chaitanya

    Thank you very much for the detailed instructions. Absolutely brilliant! However...

    I did the first part (adding the table + field and setting the EffectiveAccess to Update), which had no effect. The field in the form remains greyed out.

    I then tried the second part but I must be doing something wrong. I can add the form. But when I want to add a control to the form, the drop-down list on the Control property is empty. So, I am unable to create the path \Security\Roles\<RoleName>\Permissions\Forms\VendTable\BankAccounts

    Also, the NeededPermissions property that I found under the Form Design does not list "yes" or "no" but instead lists "none", "read", "create", etc.

    Yours

    Abaw

  • Verified answer
    Chaitanya Golla Profile Picture
    17,225 on at

    Hi,

    NeededPermission should be set to Manual on the FormControl and just copy paste the control name in the control property dropdown.

  • Verified answer
    Community Member Profile Picture
    on at

    Hi Chaitanya

    That, or setting them to any other value but "none", did the trick. After that, it still didn't work, until I added the Entry Point that enables the EDIT button to the privilege. Once that was done, things worked. However, this also opened up some other fields for editing, which I then had to close down by adding those controls as per your instructions above.

    Yours

    Abaw

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

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
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans