Share
Report
63Hello,
I've a question regarding the security roles in Dynamics that I need for the users of my Model-driven app. So I hope you can help me with this since it's actually a Dynamics related topic I guess:
My Model-Driven app uses some custom tables in Dataverse. One of these tables stores records that only special users with a custom security role can edit. Other users only have read-only permission on this table that I manage with another security role.
The users with write permission on the table can edit the records of this table and also deactivate them. This means, they can set the state (or value) of the standard entity statecode from active to inactive (I renamed it to open and fulfilled). I added this entity to the main view and the main form so that a record can be set to fulfilled (with that, inactive).
The problem is that these users with write-permission can also click on the deactivate button on the top which deactivates the record. However, this shouldn't be possible.
I want the users to use the drop-down menu of the statecode field to deactivate the record because there's a business rule behind this statecode field that disables the write-protection based on a condition. If my users could just use the deactivate button, my business rule wouldn't make sense.
Now, I'm looking at the security rules in Dynamics to find a solution for this:
- Is there a setting that disables the deactivate button at the top?
- And a permission that allows a user to set an inactive record back to active (in my case, only the manager role should be able to do that)?
Best regards,
DogWithRedSocks
All responses (
Answers (
