move all files to another folder except 1 file which needs to go to another folder

[lshneier]

Once a month we'll receive a monthly batch of files uploaded into a central folder. I'm trying to automate the process of moving these files into archive folders and notifying team members where the files are. So far I'm using when a file is created to start the flow and move the this file to the correct dynamic folder from other variables in the flow.

The monthly batch is 18 files uploaded in one bulk upload. 17 of these files go into a response folder and one is a consolidated file that goes into the parent folder of the responses. I'm guessing I can use some form of loop that checks if the file name contains consolidation and provide that file a different move command. My issue is when I look through the dynamic content on the move file step I put in after the filtered get files. there ae no options to use as the file I want to move. into the other folder. 

Can anybody think of a way to basically have the flow say if file name contains consolidation move to folder x, if not move to folder y.  Ideally I would also need a stage in the flow that checks if the response folder exists if not creates one.  This flow would need to be created in the web app as there is no change my IT team will ever allow the desktop version to be installed.

edit: as suggested please see some screenshots of the current state of this flow. naming conventions are still a mess as i have been testing this in several parts using instant flows whilst I build it up. this also means I've chopped and changed some of the steps so i've removed variables i created when i realised they weren't needed etc.

 my current thought process is to add a conditional branch between the new folder and move file step.  this condition would be something like substringof('Consolidation',FileLeafRef ) to test if the file contains the word consolidation and triaging accordingly. then i'll remove this move file step and replace it with two moving operations one to the main archive and one to the parent folder for the consolidations.

the variables are not that important to the question at hand but most are just stages of producing the folder name which is dependent on the month and year that we are currently in. the year code

if(less(variables('folder month'),4),concat(formatDateTime(utcNow(),'yyyy'),'-',add(int(formatDateTime(utcNow(),'yy')),1)),concat(sub(int(formatDateTime(utcNow(),'yyyy')),1),'-',formatDateTime(utcNow(),'yy')))

 and the month code 

if (greater(add(int(formatDateTime(utcNow(), 'MM' )),-5),1),add(int(formatDateTime(utcNow(), 'MM' )),7),add(int(formatDateTime(utcNow(), 'MM' )),-5))

[eliotcole]

Hi, @lshneier, can edit some screenshots of what you've tried so far in the original question above?

This will help with more context, as folks won't necessarily want to do your job for you. 😉

Either way, the problem that you will have for your trigger, here is that even if you wanted it to be so, not all 18 files will appear at once. So you will need to trigger on a new file, then wait for 18 files.

1. Trigger on a new file in folder
2. Initialize an Integer type Variable called fileCountVAR to count the number of files in the folder.
3. Run a Do until action where it runs until that integer is 18, inside the loop you have 3 actions:
   1. Insert whatever delay you want.
   2. List the files in folder.
   3. Set Variable fileCountVAR using a length() expression on the list files action prior.
4. Afterwards run two parralel branches:
   1. Branch One:
      1. Run the list files again and filter by the file that you need.
      2. Move that file where it's needed.
   2. Branch Two:
      1. Run the list files again and filter by everything *but* the file that you need.
      2. Move those files where they're needed.

If you want to capture errors then you can add further branching using the 'Configure run after' option to set a success and failure branch for each thing that you want to log.

If you wish to capture a long running task, you can notify yourself upon start, and run a parralel branch to the main one, with a delay for whatever time you feel is too long. Once it hits that, you can have it send you another notification to either check the files, the process that's moving them, or speak to the people involved.

[lshneier]

as suggested i've put the overall structure of the flow as it currently stands into the question but i didn't feel the need to expand all the elements and redact portions as the notification code isn't in there this is an easy thing to add at the end when i let the code go live.  also alol the variables are fairly simple aside from the month and year variables but i have tested all of them in an instant flow posting results to my teams chat so i could tweak before loading them into the project.

if you think anything else could help let me know.

[eliotcole]

Yeah, try doing what I suggested in my previous message, @lshneier ... you'll never know unless you try what can work, here. 😉