Customer experience | Sales, Customer Insights,...

Dynamics 365 Field Level Security Question

(0) Share

Report

Posted on by AC-29050120-0

Hi,

Is it possible to have field level security set up so that admin and normal users can follow the below logic:

e.g.

Field called /ABC/:

Admin has create, read, update access

Normal user has read access only

In the above scenario, admin can manipulate field however they want, and normal user can't (expected behaviour).

However, following this logic means that normal user also cannot create or update a D365 record without getting an error message.

Field ABC needs to be editable by admins only.

The only way getting around this at the moment is setting field to read only for everyone and using god mode from plugin to edit as admin. Would like to have an alternate method to this using what was described above.

Thanks

All responses (3)

Answers (0)

Leah Ju Microsoft Employee on at

Like (0)

Report

Dynamics 365 Field Level Security Question

Hi Partner,

Have there been any updates?

Please feel free to ask me any questions you may have!
Suggested answer

Leah Ju Microsoft Employee on at

Like (0)

Report

Dynamics 365 Field Level Security Question

Hi Partner,

Why do normal users get errors when creating or updating records? Because they cannot edit the 'ABC' field?

All I know is that when a field is required, a null value on creation prevents the record from being created successfully, but it shouldn't have any effect on editing (successful record creation means that the field value is not null).

If this is caused by the field being a required field, you may consider using the following method:

1.Change field requirement:

--You can set it with 'Business Recommended' option:

2.Set one default value on the field:

--You can use Business rule to achieve it, it has one action--Set Default Value, which can populate value when someone create one new record.

https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/create-business-rules-recommendations-apply-logic-form?view=op-9-1

I hope you can mark my answer verified if it is helpful! If you have any questions, please feel free to contact me.
Regards,
Leah
Suggested answer

PerezAguiar on at

Like (0)

Report

Dynamics 365 Field Level Security Question

Hey

I think that precissely, the behavior you're describing (some users have CRUD permissions, while others have Read only) is the whole point of Field Level security. Even on the example on https://learn.microsoft.com/en-us/power-platform/admin/field-level-security it's described that you can have 3 different teams (managers/Read only, VP/Full, Agents/None) and the behavior would be different.

On the same documentation, after step 7 you have how to configure Security Profiles and associating specific permissions to each profile. Please note that the Profiles are NOT the same as Security Roles.

******
I hope this answer has helped you solve your problem. If you are satisfied with it, please consider marking it as the excellent answer by clicking on the green check mark below. This will help other users who have similar questions find the best solution.

Thank you for your feedback!