Hi guys,
this one has me stumped, primarily as I'm not a developer and no expert on JSON and SharePoint REST API stuff.
However, here comes the crux. I was then asked to ensure that the flow runner can only run this update flow if they were able to create files in the folder in the first place, to avoid the flow runner from updating files in folders they were not supposed to do so in. And this is where I am a bit stumped. As I understand it, I cannot have RunAs flows run with actions from the same connector but under different contexts (i.e. one action run as whoever RunAs triggered the flow and another action from same connector later run as elevated user).
One suggestion, which I assume could work, would be to create a solution so I can have childflows and
The primary reason that I have not gone for this approach is uncertainty about the licence requirements for solutions and not being quite aware of them until I was already deep into the approach I began with. My second concern with this approach is of course that the recycle bin of that site will contain a lot of deleted temp files that won't be deleted until 93 days have passed. It feels... crude? 😅
From a little googling, it looked like it could be possible to accomplish something similar to the "Check permission" button using REST API calls. Ideally, I want my flow running under elevated permissions to determine if the (RunAs) flow initiator has either the "Add item" permission or the custom permission level in a folder and then proceed from there.
My problems here is figuring out the correct REST API call to use and how to handle the JSON that it returns to get the values I need to check again. I get a ton of information back but I am not a JSON guru and my Parse JSON attempts validate but still gives me issues trying to parse them...
I want the flow to test against a given folder if a certain user either has "Add item" or has access due to a custom permission level "Contribute - no edit or delete"
I created a flow purely to determine permissions and I have been playing around a lot in it, so it is a bit untidy with regards to use of dynamic data and so on, but any input, blog links and so on is appreciated 😅
Screenshots of flow (also as OneDrive link😞
Everyone has read access. Certain users have write access but not modify access. The purpose of the flow is to provide only these users a way to modify an item but also prevent them from accidentally overwriting the item using a move action from another library for example.
What is the reason for checking this? Is everyone able to read/edit the folders but not everyone is allowed to archive?
I'll give it another try with my hacks. Thanks for reminding me of it!
I have! It was the basis for version 3 - the problem is that it only tests on a library and not a folder inside the library I think?
I should add that HTTP request 3 returns two values - a "High" and "Low" appearantly for the correct user. However I have been struggling to interpret those values...
Have you found this post?
WarrenBelz
146,731
Most Valuable Professional
RandyHayes
76,287
Super User 2024 Season 1
Pstork1
66,075
Most Valuable Professional