![]() There is no action required - this is just a name changed and it doesn't impact the user privileges or role assignment. ![]() Note from the docs: The (old) Common Data Service User security role was renamed to Basic User. This role is for actions in core entities where the user can write, update, and delete records that they created or owned. Every user with a license is automatically assigned to that Security Role. This opens a new tab - just to mention, this can take some time to load. In the menu, open the Advanced settings as here. So, to add permissions to users follow these steps: As Administrator, you can open the gear icon in the top right corner next to the account icon to open the settings menu. See more about the predefined security roles at Environments with a Dataverse database. Users with that security role can view all data in the environment - they don´t need explicit permissions. The System Administrator role has full permission to customize or administer the environment, including creating, modifying, and assigning security roles. Note that these steps are required, since the Environment Maker role doesn't have privileges on the environment's data. You can find out more about using Dataverse at Common Data Service Introduction - CDS 101. The table name here is atworktest with some text columns. To demonstrate how to set permissions, I switched to the environment (in my sample, it´s the " Dev environment") and created a new table in the / Data / Table menu. So, if your users get an ugly "unknown error occurred" when accessing the PowerApp, here´s the solution to assign the required security role and permissions. When users shall have access to a PowerApp that is using Dataverse (formerly Common Data Service - CDS), they also need to have the permissions to access the data entity (nowadays called table).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |