Approval Process with Modifying File Question

[Anonymous]

I have a process that goes as follows: 

When a file in "Unpublished Documents" is created or modified:

- User uploads or creates a file in a document library called "Unpublished Documents". 

- Manager approves the file 

- Column that sets the state of the file in "Unpublished Documents" switched to "Yes"

- The approved file gets copied over into another document library named "Published Documents"

- End

So there will be instances where the manager will want to modify the original document and run it through the process again. However, every time the item is updated or modified it will kick off the flow again. I want it so a manager can modify a document and then move it through the flow again after everything that needs to be changed is changed. 

[haroldbk_msft]

It's not clear what you want to happen when the manager modifies or updates the file. If the trigger is when a file is created or modified then when the manager edits the file, we would expect the flow to trigger.  

Did you not want to approval to run again? 

[Anonymous]

So when a manager wants to change a previously published file, just changing one aspect will fire the flow. So if the manager makes five changes on the item/file, then the approval will fire ten separate times. I am trying to avoid that. 

[haroldbk_msft]

Yes, that is a challenge.

You could try to use a Trigger condition that evaluates the trigger action.

This is a good explanation of how to set it up

https://www.timlinenterprises.com/microsoft-power-automate-flow-trigger-conditions/

[v-alzhan-msft · Accepted solution]

Hi @Anonymous ,

Trigger condition wouldn't work since the connector is modified now.

The workaround should as below:

1. Since you don't want to trigger the flow before the update is finished, you could add a Yes/No type column IsFinished column in the library, the column's default value is No, so you add a Condition under your flow trigger to check if the IsFinished column value is equal to true, if yes, do something you want inside the If yes branch, leave the if no branch blank.

2. since if you modify the "Unpublished Documents" column in the flow, it would also re-trigger the flow, you could also add a Condition to check the value in the "Unpublished Documents" column under the trigger to prevent the loop.

Best Regards,

Alice

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.