Hi everyone. I am facing an issue with the latest Dynamics 365 multi select control. Admin user can select, change and remove options from the field.
But non admin users are not able to select or remove the options. They are however able to view the oprions selected by admin.
Both using the same form and the field is not read-only. Non admin users have create privilege over the entity and field security profile is not enabled for thos field.
Am I missing with privileges or something else?
Thanks in advance.
*This post is locked for comments
Hi Everyone,
Recently even I had this issue but couldn't find "Multi Select Option" entity in security role tab anywhere. I even tried with Optionset entity privilege but no luck.
Thanks in Advance
Ravi B.
I just had a similar issue, and this fixed it
Multi Select Option Sets require prvReadSecurityRole
Multi Select Option Sets require prvReadSecurityRole
Hello, we had this problem with all browsers, but we found a solution. It is an permission issue, and in my opinion a bug. In our situation the users needs in his security role under <Business Management> read rights for <Currency>. For whatever reason we dont know, but this solved the problem on our side.
Which browser are you using? Did you try Chrome?
No. We couldn't fix the problem.
Workaround is - to use the CRM Hub app url and update the multi-select field. Works in mobile app also.
Hi there, we have the same problem. Did you find the cause of this?
Hi,
Could you kindly check whether the field is enabled field security.
Dynamics 365 comes with security settings that control your access to certain features, data, or even fields on screens, depending on your role.
If it turns out that you can’t see or access something described in this guide, or if some data is marked “read only,” check with the person who manages your system day-to-day. You may need to get additional security permissions.
For more information, you could refer to the following article.
https://docs.microsoft.com/en-us/dynamics365/customer-engagement/basics/basics-guide
BR,
Judy
Seems like you have the right privileges.
If user has read/write access to entity, and the field is not secured, they should be able to make changes to the field.
Possibly this is a bug or an update that was performed on your instance that caused this problem. Has this problem just occur or has it been around for a while? If you can't get it resolved, I would suggest a ticket with MS.
Hope this helps.
Mohamed Amine Mahmoudi
83
Super User 2025 Season 1
Community Member
54
Victor Onyebuchi
6