Forum Discussion
Microsoft Flow and document lifecycle for approving major versions
Similar to Mark's question / situation.
I can do an approval based on the assumption the file is new or someone has edited it in the library so the approval status is reset to Pending.
But what about situations where the doc owner gives the file a surface review, makes no changes and simply wants to re-approve / reset the document review date. It would be great if I could wrap these teo scenarios into the same flow with a check against current approval status. But it looks like I'm going to have to build 2 flows for each, and work off another column, or automatically update a metadata column to force a Pending state then send for re-Approval.
Is my take on this still accurate? Still cannot look up the selected files approval state via a condition?
Cheers
To update myself.... looking at a REST call on item get _ModerationStatus and see if I can check the current status via REST then apply this to a condition. So if current status = Approved = reapprove, else regular approval flow.
To assist anyone - using the SP api of GetByTitle combined with the method of calling your tenant/site/library with a client secret etc allows you to send a GET of
You can then assess the current status of the object approval with the following -
Approved, //0 Denied, //1 Pending, //2 Draft, //3 Scheduled //4
run a condition against that and then keep a basic 're-approval' in the same flow as a full on new doc approval.
Hope this helps..
In my use case I am not using documents. Does this work on Lists for items with content approval turned on? I can't seem to get this to work no matter what I try. I used the REST call to obtain the metadata and Etag of the item. Then attempted to use the "Set content approval status" control. Just can't get past this kind of error....
"The current state of the item is Approved and the following action Submit cannot be implemented"
