Planner Report - Problem with 'Get user profile (V2)'

[agaskew]

Hi,

I have downloaded Microsoft's "Create a daily summary of Planner Tasks by Bucket. 

Also have tweaked it to include an 'Assigned to' column in the report.  This is done by passing the 'assignment' value from 'List tasks' to 'Get user profile (V2)' and returning the 'Display Name' to a String Variable that is included in the output table.  So far so good.

The problem is that in the Plan there are  (completed) Tasks that remain assigned to Team members who no longer exist in the domain.  Planner itself lists the task as being assigned to 'Former member'.  The Flow report 'Get user profile (V2)'doesn't cope with this, instead it fails with a standard statusCode of 404 "Request_ResourceNotFound".  When this step fails, the whole Flow fails.

Is there a way to cater for 'Get user profile (V2)' not finding a result without breaking the Flow?

Thanks.

[Pstork1 · Accepted solution]

Try setting the Run After settings for the action after the Get user Profile V2 to run both on success and failure. Then make sure to test for whether the DisplayName was found or not.  If not put a string in its place.

[agaskew]

Thanks, I'll give that a try, didn't know about the 'Run After' setting.

[agaskew]

Thanks, I think this is working better now in that the Flow does not fail if the user does not exist at all.

The next challenge is to work out how to cater for Tasks that are Unassigned.  The 'Get user profile (V2)' lookup is inside an 'Apply to Each' for 'List Tasks:value assignments'.  Is it correct that this 'apply to Each' loop will not try to perform the Get user profile (V2)' lookup at all, for any Tasks that are Unassigned, becase there is no value for 'assignment'?  If that is the case, I'll have to add a test for the value of the assigned user outside the lookup, ie just after. 

Sorry if this is confusing.

[Pstork1]

YOu'll need to test it to be sure, but yes, I think it will ignore the ones that haven't been assigned based on the loop processing just the assingment entries.

[agaskew]

Thank you again, and sorry for the delay in replying.  Testing shows that Unassigned tasks are totally ignored by this part of the flow, whereas I had mistakenly assumed that the flow would check every task and treat the assignment differently depending on its value.