I have a SharePoint Library with the following columns (red-colored font are required fields):
Here is my Flow (more details below the image):
The flow continues further on down to a second approver and various emails and such, but the above image shows where I am getting stuck.
In my first version of the flow I did not have the "Delay" action included in the Flow, nor did I have the 2 Condition Actions: (1) "Condition" and (2) "Condition 2" and I was getting this error: The request failed. Error code: 'InvalidApprovalSubscribeRequestAssignedToMissing'. Error Message: 'Required field 'assignedTo' is missing, empty, or contained no valid users.'.
This error made me think to myself, okay... The document is being uploaded and the flow is kicking off before the document uploader can set the metadata for the two required columns (Approver #1 and Approver #2), so I went online and found a trick to use the "Condition" in an effort to hold up the flow in a state of pause until the document uploaded assigned metadata to the two required columns. I still got the error stated above.
I then thought, what if I set an inherit delay into the flow, hence the addition of the "Delay" action and I set it to 1 minute - plenty of time to do the required fields. I sat and watch the flow, and I saw the countdown from 1 min to 0 seconds, flow would process and I STILL get the same error.
To me the error is indicating that it is not able to detect a value in the "Assigned To" field within the first Approval action.
Here is an image of the error:
The weird thing is... If I change the initial Trigger Step to "When a file is created or modified (properties only)" using this exact same process works as intended - the problem is, when I go and update the metadata of the file as a result of the Approve/Reject from an Approver it starts a second instance of the flow, because the file's metadata is modified.
The WHOLE reason I want this to work is so I can reduce my total number of manual entry points into the flow so I can replicate it many times. The ONE thing I want to work is I want to be able to auto-populate the Approver's email address into the Approval email, which is dynamic metadata as a result of requiring "Approver #1" (People Picker) and "Approver #2" (People Picker). Here is a screenshot of the field I want to be Dynamic, but is the reason why this flow isn't working:
That field I highlight above is "Approver #1 Email" which is something that should be able to pull from the AD, because using People Picker field.
I cannot use "Get Manager," which is a very common solution I found online, but it won't work in our tenant due to accuracy/data integrity related issues.
Any help would be greatly appreciated.
Have you tried to output the values of the Dynamic content populated in Assigned to?
You could output this value to see if it is the expected value.
From the error message, it seems that this email address may not be a user within the organization, or is not a valid email address.
Please make sure that the value of Dynamic content populated here is a valid email address and must be a user within the organization.
Take a try.
I thought of that. For my testing of the Flow I was using one of my service accounts - the service account we use for Flow creations (because we are an MFA environment), and in my SP List in the "Approver 1" field I was inputting my own name, and so I don't think this is the issue :-\
Thank you for posting a reply to a topic on the Microsoft Flow Community! It appears that the users who you have been engaging in this thread with are now awaiting your reply! Please follow-up on this thread ASAP.
Microsoft Flow Community Manager
Join us for an in-depth look at the new innovations across Dynamics 365 and the Microsoft Power Platform.
Continue your learning in our online communities.
Features releasing from October 2019 through March 2020
Fill out a quick form to claim your user group badge now!
Learn how to build the business apps that you need
Find out where you can attend!
Watch & learn from the Flow Community Video Gallery!