Hi, guys!
TLDR: Using Sharepoint PowerApps forms to display list items, also setting item-level permission through a power automate flow. By design I do not want users to have Sharepoint-site access to the lists itself and only item-level. When they navigate to the specific item (which is granted by item-level permission through Power Automate), they get an error when the forms app is loaded: "This app isn’t opening correctly It looks like you don’t have access to this app. Ask its owner to share it with you".
Background (details below of what we want to achieve):
I've created a Sharepoint list ('Oppgaver') forms where we are mimicking a to-do list for a group of people.
The idea behind this is that the manager(delegator) simply has full access to the whole list where this is his view (the only person that is a member of the specific site):
And the rest of the users (task-handlers) will only be able to see their items (item-level permission) as long as they have been assigned to the person-column "Ansvarlig".
This means that whenever a task-handler tries to open the link and navigates out of the item and to the manager-restricted list itself, they will only see their own assigned/permitted items only:
So far so good, but as soon as we activate the PowerApps forms it seems that the app's permission settings are inherited by the list/site-permission rather than item-level permission set by the Power Automate delegation-flow; they get this error during PowerApps load:
Are there any workaround to make the PowerApps forms not inheriting the permissions based on the Sharepoint list, but instead be based off the list-item permission set by the existing Power Automate flow trigger?
Suggestions, links and articles are greatly appreciated to guide me!
Br, Ga Kin
Edit: Changed title to reflect the specific issue with Sharepoint forms item-level permissions including a Power App.
(Update) as a temporary workaround:
I've made the list available (edit-access) to members in a specific group and created a custom default filter for the list, to filter the list-items only displaying [Me]. This way, the PowerApps forms will be available for the users to edit the items, and when trying to navigate back to the list - the view will be filtered (but unfortunately not restricted if they happen to change the filter view).
Hi, @Caryn !
Unfortunately, no... Instead I made a default list-view in my Sharepoint List for users in general, which only showed items that was tagging themselves from a specific column.
A temporary solution involving changing the SharePoint list filter. But they will still be able to see the other items not assigned to them if they are changing the list filter view in the future:
I cannot remember the syntax for the filtering since this was done on a customers tenant, but you might be able to find the right syntax if you search for it online. it was something with "[@me]"...
Hello again @Caryn. I noticed that @RezaDorrani have shared a new tutorial that might be touching abit on the subject to resolve this (I've only been scrambling through the video) - the next best thing is that you have an additional Power Automate flow that tracks any list item changes, with an action that just updates the permission right to the specific item to the assigned users:
Wonderful thank you!
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
This training provides practical hands-on experience in creating Power Apps solutions in a full-day of instructor-led App creation workshop.
User | Count |
---|---|
195 | |
45 | |
45 | |
44 | |
36 |
User | Count |
---|---|
279 | |
81 | |
81 | |
79 | |
69 |