Unable to fetch user id after passing obtained access token of my sharepoint app in Microsoft flow

(0) Share

Report

Posted on by Community Power Pla...

Went through these tutorials to assign item-level permissions using Flows:

https://noellawlor.wordpress.com/2018/01/18/setting-sharepoint-item-list-permissions-with-flow/

and a follw-up to

https://powerusers.microsoft.com/t5/Using-Flows/Item-Level-Permissions-not-setting-in-sharepoint-online/m-p/261578#M6250

I am unauthorized to fetch the user ID in flow.

Here's what I did:

After running the workflow:

Categories:

Using flows

I have the same question (0)

All responses (5)

Answers (1)

MattWeston365 1,701 on at

Like (0)

Report

Have you tried running the call within Postman to see if you get the same result?

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Postman says
{
"odata.error": {
"code": "-1, Microsoft.SharePoint.Client.InvalidClientQueryException",
"message": {
"lang": "en-US",
"value": "The query string \"loginName\" is missing or invalid."
}
}
}

What I read from Microsoft Flow docs, to get user id by REST API in flow, you have to pass your login name in this URL format:
https://<sharepoint-sitename>/_api/web/siteusers(@v)?@v=’<login-name>'
and various examples have used 'CreatedBy Claims' to get the <login-name>

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Here is one more good example following my question:

I replaced '' with %27 and am passing the encodeURIcomponent(variables['email']) value as a request parameter and still says 'Unauthorized'. I did the same thing in Postman and it fetched me the result. I don't what's going wrong. No way to debug and no way to see what's going wrong. Sharepoint Online is such a frustrating creation of Microsoft. I have been stuck into Item-Level permissions for 2 weeks and still 25% success.

Also to let you know that I tried encoding UserClaims and passed the same way as I have asked in the original question but it's still unautorized.

Was this reply helpful? Yes No
Verified answer

MattWeston365 1,701 on at

Like (1)

Report

Hi @Anonymous have you considered using the builtin "Sent HTTP Request to SharePoint" action? That way you won't have to worry about the oauth elements, you just need to get your REST call right. Happy to provide guidance on that action if you need any help.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

I didn't feel the need to use HTTP connector and try the Oauth steps. "Send HTTP Request to Sharepoint" does all that without prompting you for access tokens.

Was this reply helpful? Yes No