Get manager (V2)

[Anonymous]

Hello,

My workflow fails when reaching the "Get manager (V2)" step.

I am currently using the template: https://us.flow.microsoft.com/en-us/galleries/public/templates/906bdcc238bb49f19879ab62a88f3aa7/requ...

I am not making any modifications to the workflow until AFTER this step. The default value for "Get manager (V2)" is User Principal Name. The error detail is "User not found". I looked into our Azure Active Directory and my profile currently has a manager listed in the details of my account. 

Here are two pictures that illustrate the error message received: https://imgur.com/a/nBf1J4W & https://imgur.com/a/v0nSa6k

Any help would be greatly appreciated!

[v-yamao-msft · Accepted solution]

Hi @Anonymous,

Thanks for sharing the detailed info.

I have made some changes on the template.

Instead of using the action Get my profile, use the action Get user profile (V2) in the flow. And select dynamic content Created By Email from the trigger for the User (UPN) field.

Please take a try with it on your side.

Best regards,

Mabel

[Anonymous]

Thank you for responding to my question. I'm having a massive amount of trouble just trying to edit "get user profile (V2)" into the workflow. 

I can't delete the "Get user Profile V2" step without deleting the steps that rely on this. Is it possible for you to send the template that you've sent in your last post? (The screenshot)

[Anonymous]

I am having the same issue here. However my inital input is coming from MS form.

-using "get user profile2" - from MS form.. using mail..Which is successful

-using "get Manager v2 - using UPN... Fails.

I have tried using  (from user profile data return) upn, mail, given name, etc...... All fail.

>>I have another flow where mail for get user profile and UPN for get manager all work.

Can we get developers looking at the get manager connector and how it connects/retrieves to/from an enterprise azure.

Office365 connectors need to be solid if you want MS flow adoption in the enterprise.

[zoidberg]

I ran into this same error today, after trying to optimize a flow which was working fine a few hours ago.

This whole flow stuff seems to be on some pretty shaky ground. It my second day using this and I have already run into 3 bugs.

Solution:

Turns out that if you use the "Select fields" in advanced options of the previous step, and don't include userPrincipalName, you get this worthless error message which says nothing about the actual problem.

This took me an hour to nail down the true root cause.

"user not found" ? Really ? How about "UPN missing" ? Or how about don't show UPN as an available choice in the Dynamic Content options of GetManager if the previous step GetMyProfile did not even include it !

Inputs

{
  "api": {
    "runtimeUrl": "https://flow-apim-msmanaged-na-eastus2-01.azure-apim.net/apim/office365users"
  },
  "connection": {
    "name": "/providers/Microsoft.PowerApps/apis/shared_office365users/connections/5962745f8a4a43abb086"
  }
}

Path

/codeless/v1.0/users//manager

404 Response

"Flow error: 
{
  ""error"": {
    ""code"": ""ResourceNotFound"",
    ""message"": ""User not found"",
    ""innerError"": {
      ""request-id"": ""ef98033e-692c-4b68-ad0d-79041dd337b8"",
      ""date"": ""2019-10-09T22:23:30""
    }
  }
}"