Finance | Project Operations, Human Resources, ...

Makin certain field editable

(4) Share

Report

Posted on by DELDYN

464

Hi,

if we have a standard form that is "read only" for 3 roles (the form contains around 20 fields)

if they want those 3 roles to only be able to edit one field out of those 20 fields

does that mean i need to add those 19 fields as "read" in the security privilege for the datasource And that one specific field to be "delete"?

but what if in the future, Microsoft adds more fields?

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (5)

Answers (0)

Sidick 168 on at

Like (0)

Report

Just a thought, I don't even know if this is feasible. Why not deny access to the whole table and create an override to give read access to only one specific field.

Was this reply helpful? Yes No
DELDYN 464 on at

Like (0)

Report

Hi @Sidick

I'm not sure what do you mean? how to do that??

and just to make sure the requirement is clear, other specific roles can have full access to that form

it's just those 3 roles, can only edit one field from that form and other fields are not editable

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 300,743 Super User 2025 Season 2 on at

Like (0)

Report

Hi DelDyn,

To achieve this, you will need to grant update permissions for the menu item in the privilege. Then restrict 19 fields via table permissions where you set deny permissions on Update, leaving the single field open for edit.

Was this reply helpful? Yes No
DELDYN 464 on at

Like (0)

Report

Hi Andre

When you say under table permissions, do u mean under permission node in the menu item?

If yes, then why not under datasource in the entry point? What's the difference?

And when you say deny permissions on update, do u mean to make access read? Or is there a property called deny permissions?

Also if i go with this approach, doesn't it mean that each time they add a field in the table, i need to go to the privilege and add the field with deny permission? Is this really a good solution?

Wouldn't it be better to add code for those 3 roles to only edit one field? I know in the future maybe a role might increase but i think it's chance is less than adding a field in the table.

I feel those 2 solutions have disadvantages

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 300,743 Super User 2025 Season 2 on at

Like (0)

Report

Hi Deldyn,

You can try the data source as well. There is indeed a deny permission level. You can read about this field permission in an example on my blog: Security how-to: Only finance users are allowed to see cost prices in Dynamics 365 Finance and Operations - Dynamicspedia
In case you give read access from the privilege for the menu item, this is the highest level of security for the form. Indeed, this approach is cumbersome, but works using the security configuration.

You can also manage it using coding, but that will be for the form where you need to recognize the security roles preferably without hard-coding them.

Was this reply helpful? Yes No

Join the conversation

Community site session details

Makin certain field editable

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

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

Featured topics

Product updates

Community site session details

Makin certain field editable

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

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

Featured topics

Product updates