Replies: 2 comments
|
For a model-driven app, you share the app directly with a security role: users with this security role will have access to both the app and the data. For canvas and code apps, you share with a team (or user), and people in that team can access the app. They obviously still need access to the underlying data through a security role. Your issue seems to be with the security role, not the code app. To test this, I would suggest creating a disposable model-driven app with the same table, sharing it with a security role, and seeing if users can view the required data. If not, it is definitely a security role issue. |
0 replies
|
Code apps adhere to Dataverse's security setup meaning that the end users require relevant access to the underlying tables. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi All,
Here is my usecase:
I have a Production, managed environment
i have 2 solutions:
8 users: with assigned Powerapps Premium license (and powerautomate premium licence), plus assigne "Basic user" sec role and the custom sec roles needed for one-one app.
What's the problem:
What i did:
Question: hooooooow can i make it work for the users? This is a try with code app, previously i was building a model driven on top of these and i deleted it, since the code app had mor UX/UI flexibility. back in the stone age, model driven was needing only a "share" and that the users had license, sec role and that's it.... Am i missing something?
All reactions