Hi,
We would like to build a canvas app against a table in Dataverse. An end user should be able to create records in the table only through the canvas app. The user should not have direct access to the underlying dataverse table from make.powerapps.com. Also, there is a field on the table called 'On Behalf Of'. The user who is creating a record using the canvas app can pick another user in the 'On Behalf Of' column. Now, the access that we need is that both the creator of the record as well as the user in 'On Behalf Of' field need Read/Write access to the record (again only through the canvas app). I understand that if the table was a Sharepoint List then this could be possible by changing the item level permissions (though we still have the issue that user's can directly access the SP List).
Would like some guidance on how we can use dataverse to achieve the above.
Solved! Go to Solution.
Hi @prathyoo ,
A couple things on your business case here...
Hi @spow ,
Based on your specific need I would do the following, let me know if this answers your question...
At this point the record will not be tied at all to the user that created it, it will be owned by the Manager so he / she will have access and the roles will of course allow HR to see the records.
Your case is a bit different so I would not use Access Teams for your scenario as you do not need the end user that created the record to maintain access to it...
Hi @prathyoo ,
A couple things on your business case here...
I have the same issue. I’ve watched the YouTube and others about Access Teams and that aligns it to a D365 scenario, not so much canvas app with Dataverse as a respository.
My issue is an HR app where a manager may need to delegate a user to add an entry on their behalf. The manager would need to see the entry the on behalf user has created. I get that the access team covers this but don’t understand how it connects up. The video talks about a team template then adding a sub grid to the form but that does not align to my app.
Can anyone guide me further, I’m sure I’m missing something small!
Hi @spow ,
In your situation you are having an individual create records within Dataverse and the Manager needs access to these records or do you want the owner to be setup as the Manager and the on behalf user still have access to the record? Just want to make sure I understand what you want to happen as there are a number of options here.
Example options:
Once you provide access you can have a view setup in Dataverse that will show the user's records and can include the records they have access through Access team assignment as well. See Neil's article here (https://neilparkhurst.com/2021/10/31/view-records-owned-by-an-access-team/)
Thank you so much for taking the time to reply.
The scenario is the logging of an absence. Because of the content of this, the data needs to be locked down so that just the HR team see all the records and the manager just sees what they have logged. I’ve sorted that with security roles, tested it and it works fine.
There are scenarios where a user would do this on behalf of the manager and the manager would need to see those entries to update them.
My confusion is how does the access team link to the Dataverse table? The vids I’ve watched talk about team templates and sub grids.
I’ll check out your link and let you know if I’m still confused!
Yes still confused! 🤦♀️
Hi @spow ,
Based on your specific need I would do the following, let me know if this answers your question...
At this point the record will not be tied at all to the user that created it, it will be owned by the Manager so he / she will have access and the roles will of course allow HR to see the records.
Your case is a bit different so I would not use Access Teams for your scenario as you do not need the end user that created the record to maintain access to it...
Hello
I have now tested this and it works really well for our scenario.
I really appreciate your time in helping me, thank you so much.
User | Count |
---|---|
20 | |
11 | |
9 | |
5 | |
5 |
User | Count |
---|---|
31 | |
30 | |
15 | |
12 | |
9 |