Dataverse Record Level Security in Power Apps

Рет қаралды 6,770

Күн бұрын

00:00 - Intro
00:55 - Enable Business Unit Ownership
01:39 - Create Business Units
02:15 - Create Security Role
04:04 - Assign Security Role
05:59 - Create Business rule
10:26 - Final Demo
The scenario here is to enable row level security within the concepts of Dataverse. Important to note, this can be applied to Canvas or Model-driven apps.
For example:
I have a Sale Commission table which is connected to a Model-Driven App. One of the columns is a choice called Store.
To do this functionality we will be using the following:
- Business units
- Security role
- Dataverse table
- Business rule
- And more..
::---------------------Documentation---------------------::
Record Ownership in Modernized Business Units
learn.microsoft.com/en-us/pow...
Security in Microsoft Dataverse
learn.microsoft.com/en-us/pow...

Пікірлер: 14

@kannank7313 11 күн бұрын

Fantastic demo. MVPs really suck at explaining this concept.. you nailed it.

@pramodagarwal1990 Ай бұрын

This Video was very informative. Make more videos on Business Rules and Dataverse Table relationships

@leJuan5150 Жыл бұрын

Great demo Josh!

@flowaltdelete Жыл бұрын

Thanks John!

@davediguer4770 Жыл бұрын

Hello - thanks for putting together this video. This was very helpful. Looking at the fields in a Dataverse table i see there is Owning Business Unit, Owning Team, and Owning User. I will also do some research into the Owning Team and Owning User fields to see how they can be used. Any chance you want to make a video on those ....😁

@ronn_zw Жыл бұрын

Thanks for sharing. Maybe expand it to have a global role that will see all the records.

@flowaltdelete Жыл бұрын

Great idea!

@radhashroff7738 Жыл бұрын

Thank you for this video! Is there a way we can set more than one teams as owning team of the record?

@headflask Жыл бұрын

How would this work with Power Pages and the Contact List? I would want users from one client to only see their client records. Some users (internal or consultants) could see more than just the one client's records. Right now I have been trying table permissions per Account but that doesn't allow viewing more than one account at a time. Looks like permissions are linked to a person through Contacts or Accounts.

@flowaltdelete Жыл бұрын

It should the same. As the permissions I am setting in the video are Dataverse roles and Business units. You might be able to use the sharing feature. For example: restrict all records, than have client records assigned (shared) to the user who owns their contacts. For additional help in your scenario. You can also post in the community forum: powerusers.microsoft.com/t5/Forums/ct-p/mpp_forums

@headflask Жыл бұрын

@@flowaltdelete I started with making a Client table that had all the different accounts then an Account1, Account2, Account3 column matrix to build a hierarchy. Then I ended up using the Parent Account column in Account table to set up a hierarchy 3 levels deep. The fun part was hashing out 3 different levels of Account-Table, Account-Parent Account-Table, and Account-Parent Account-Parent Account-Table of account level access for an edit web role. Then all over again for the view web role. Lots of table permissions but I managed to delete that superfluous Client table. Now each Contact will have access to different rows depending on their Account as well as where that Account sits in the Parent Account hierarchy. I can see everything. My consultants can see their stuff and their client's stuff. Clients can see just their stuff. Figured I'd better circle back here.

@stabiloboss2764 8 ай бұрын

hi flow alt delete. really appreciate the video! But i ran into a problem that others might have aswell. My problem is that my new users, being added to the business units in the way you've said, cant view the table of interest in dataverse. Instead, an error message appears: 'We couldn't load your data. Please try again later'. What my general background is: - I am an admin in a dataverse development environment. In this environment I created a table in which i need row level security. - i created a new test user, and have just added it to this development environment in hope it will enable the user to see the table. - and i have followed the steps in this video to implement record level security in this table, and have assigned the new test user to a 'child' business unit. I have been stuck on this for ages! Let me know a solution (anyone)

@e-polk Жыл бұрын

This was very helpful. I changed a user to a different business unit and updated her security role to Parent Child Business Units level on all my custom tables. She can no longer see the records on the Lookup tables that someone else entered in the Original Business Unit. Can you tell me what I might have done wrong?

@chintandd 8 ай бұрын

One user can be part of max one BU and not multiple