Forum Discussion
Send a document for review Part 2
Hi Quotidian,
You can add an "Due Date" input to "For selected file" action. See image below.
Use "Due Date" value from the action to populate the "DueBack" column.
The user experience will look like this:
I hope this helps.
Norm
Hi Quotidian,
Check out this post: https://powerusers.microsoft.com/t5/General-Flow-Discussion/Send-Email-With-Options-Two-sets-of-buttons/td-p/179787
Using your last suggestion to trigger off of the "Due Date" column, send an email with "Reviewed" or "Not reviewed" buttons that can in turn set the "Status" column.
I hope this helps.
Norm
I'm trying to work in an Approval process now, like this:
It all works - to a point. When file is Sent the Doc Status is set to Under Review (you can see it change, which is neat!)
Then it's 'wait for Approval' while the reviewer does the review and after finishing, clicks Approve. I want the Approve action to trigger 'change Doc Status to Ready' as per the following.
This last step isn't working, I'm getting this error:
Branching Error
Any tips or guidance appreciated.
Norman Young I've posted it to the MS Powerusers forum. A lot of people are dealing with this type of issue. Thanks again for your help, if I solve it I'll post the solution here.
Norman Young Probably right! I thanks again for your guidance I will keep trying.
Hi Quotidian,
I'm not certain ID as "Current Item" is resolving. It's hard to tell at this point. If you have ID stored in a variable that might help but I'm afraid anything I suggest might lead you down the wrong path.
Sorry not much help.
Norm
Norman Young
Don't know how I missed that, but I rectified it and am still having this error. I'm basically trying out different connectors and seeing if any of them work. This is the current configuration:
This is the error:
I have googled the 'branching condition' error but it doesn't cast a lot of light.
OK, the story so far - to recap, select a document from a SharePoint library, then the flow prompts sender to enter the Reviewer Email and Due Date, and sets the document status to Under Review; Approval status is set to No by default.
That all works:.
Then the plan is that the reviewer has the set number of days to review the document and make any changes, THEN clicks Approve. The idea is that this changes the approval status to Approved and the file status to Reviewed, telling the Sender that the review is completed.
This is the part that isn't working:
Following the thread suggested above, I found out about the 'ETag' which apparently is required to track document approvals - that is why I added the step 'get file metadata', before 'Set content approval status'. But now the flow is failing with this error:
StatusFailedErrorAction 'Get_file_metadata' failed.
Oh sure, I could do that. I'm still working on it, I'll let you know.
Hi Quotidian,
By share, I meant an image of the entire Flow. It's hard to help further without seeing the "bigger picture". No worries if that is an issue - I get it.
Norm
>Can you share the Flow?
I hadn't thought of doing that - I think my organisation might not be happy for me to do that, and I'm not inclined to ask, as they're not providing any support for Flow/SharePoint. I'll read through that other post carefully and see if I can resolve it. Thanks.
Hi Quotidian,
I have not seen this message before. Have you seen this post on the PowerUsers forum? It might apply.
Can you share the Flow?
Thanks.
Norm
