Moving Files to the folder in Document Library

[hiti]

Hi ,

I have built the flow when a new file is created or modified based on the document type it should move to a particular folder. When I run the flow it shows run successfully. However, nothing happens in the library. It throws the error ActionBranchingConditionNotSatisfied. The execution of template action 'Condition_2' skipped: the branching condition for this action is not satisfied.

Please help

Thanks 

[eliotcole]

Hi, @hiti , please place a screenshot of your flow in your original post, and obfuscate (blank out) any sensitive data.

Essentially, though, the reason it's failing is that whatever you have set in Condition_2 is not triggering.

[hiti]

[eliotcole]

Hi, @hiti 

It would definitely help to see a screenshot of the flow in the 'Edit' screen? (before it is run or tested)

In the meantime, I suggest that you perhaps try this simple flow:

Basic Solution

This is almost a one step flow, that should work for each file that is added or modified to the chosen folder, it is simple:

1. New/Modified File - If a file is created or modified.
2. Run Case - Run a Switch case depending on the Content-Type of the file that moves the file.
3. No Match? - If it doesn't satisfy any cases, then send me an email about it.

This uses the Media Type of the file to sort, but you can just as easily use the file extension with a little bit of expression writing in a Variable. I will cover that below.

If I want to start moving 'document/pdf' file types I will add a case for that. 🙂
 
---
 
Optional: Trigger Conditions
One thing I highly recommend is that you do not run this flow on every file added to a folder. This is because people might place stuff there by mistake.

If that is not the case, then you are good to go without a Trigger Condition. If however this is a multi-use folder, and you just wish to move certain file types, then limiting what it will run on will assist you.

To do this you must define "Trigger Conditions" in the trigger settings. In the case of new files here, I have set it up to trigger on JPG or PNG files by:

1. Identify all the file Content / Media types that you intend to run this on. In my example here I want to run it only on 'image/jpg' and 'application/pdf' files.
2. Create an equals() expression function for each of those. (Example: equals Function)
3. Now paste each equals() function, separated by commas, in an or() expression, with an '@' before it. (Example:or Expression)
4. Paste your or Expression into the Trigger Condition box.

equals Function

equals(triggerOutputs()?['headers/Content-Type'], 'image/jpeg')

The equals() function checks the Content-Type of the file that might trigger the flow, and if it matches the text specified ('image/jpg') it will return a true value.

or Expression

@or(equals(triggerOutputs()?['headers/Content-Type'], 'image/jpeg'), equals(triggerOutputs()?['headers/Content-Type'], 'application/pdf'))​

The or() expression checks to see if *either* of the two equals() functions return a true value, if either are true it will return a true value to the Trigger Condition and allow the flow to run.

File Extension Solution

This is the same as the previous flow, with the exception that I am now checking for the file extension of the actual file. This is a little more advance, but only because of the aaa layers in the expression to get the extension.

You can either make a variable, like I did in this example, or you can just put the expression in the From field in the Switch action.

This is the expression:

last(split(base64ToString(triggerOutputs()?['headers/x-ms-file-name-encoded']), '.'))

This does aaa things from the inside (first) out (last😞

1. base64ToString() - Because the file name is encoded, this function will decode it to a normal string value.
2. split() - Because only the last part of the filename is required, this splits the filename every time there is a '.' in it.
3. last() - Because the split() made an array of string items, this picks the very last one which will contain the extension.

Now each case that you create is just going to be based on the file extension, in this case I have changed it to only take 'jpg' files. (which will ignore 'jpeg' files!)

---

The only downside is that if you are using trigger conditions with this one, the condition functionss will look a little bit more complex, as you'll need this whole expression instead of the previously more

equals(last(split(base64ToString(triggerOutputs()?['headers/x-ms-file-name-encoded']), '.')), 'jpg')