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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Security setup to restrict certain form fields

(4) ShareShare
ReportReport
Posted on by 1,993
Hi,

If i created  a form with two privileges (maintain and view)
this form has more than one datasource with lots of fields (30)


They want two menu items

one when opened should show all fields (allow edit, create delete)
 
the 2nd one, will open same form, but all fields should be editable except for 5 fields

so we can add code and say if the 2nd menu item is caller, then make everything not editable (no create, no update, no delete) and all fields disabled except for 5 fields.


My question is, is creating two menu items is a good solution? would it work with security? if yes how? but maybe with security it will be hard because the fields are alot?
Categories:
I have the same question (0)
  • Suggested answer
    Sohaib Cheema Profile Picture
    49,677 Super User 2026 Season 1 on at
    Hi, 
    You do not need code (if conditions).
     
    What you need are two privileges. Under the permission node, you need to specify the table name (and the type of access you want). Then, under the table node, add the fields (any number of fields you want ; those for which you want an access type different from the table access type), and for each field, specify the access type.
     
    You can also do this from UI (without going into AOT)
     
     
    cut short, you do not need If/else conditions (or any x++ code)
  • Suggested answer
    Martin Dráb Profile Picture
    239,040 Most Valuable Professional on at
    It's doable. When defining a privilege, you can add extra details of the entry point, such as configuring individual data source fields:
     
  • Suggested answer
    NikolajSorensen Profile Picture
    1,814 on at
    Having two seperate menu items should really not be necessary.
     
    If these are custom fields, then I would definitely argue that the "AOS authorization" property of those 5 restricted fields should be changed to "Yes".
     
    That will ensure that users will only have access to those fields if the fields are specifically added to a privilege/role. 
    Then you can add the specific field level access on the maintain privilege (which is supposed to have access) and not add it on the view privilege.
     
     
    Otherwise you can define on the view privilege that there should be "No access" to the 5 fields in question.
    With that solution you will however be blocked from accessing those 5 fields in case you have the view privilege, even if you are also granted the maintain privilege, as it will overrule any other access granted to those 5 fields.
  • André Arnaud de Calavon Profile Picture
    303,730 Super User 2026 Season 1 on at
    Hi ..,
     
    Above you got several suggestions which are valid in case you need to distinct opening the form by different users with different roles. 

    Can you clarify if this is the case or if the two menu items are supposed to be opened by one single user?

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 616

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 460 Super User 2026 Season 1

#3
Syed Haris Shah Profile Picture

Syed Haris Shah 331 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans