Dynamic Content not appearing in Recurrence Flow Action

[Anonymous]

Hi

This is following on from a previous post. I'm trying to ceate a set of actions to check a folder for files over the weekend. I set up a test Flow using +Scheduled - from blank, but when I add the Move File action it's not giving me the option of add File Identifier from the Dynamic Content option? It says No Dynamic Content Available? 

[ScottShearer]

@Anonymous 

Please post a screen shot of your Flow - that will make it much easier to assist.

[Pstork1]

If you are using a recurrence trigger did you do a get files action to get a list of files to move? That should give you access to the file identifier.  When you add it to the move action it should automatically create a loop to loop through the list of files.

[v-bacao-msft]

Hi @Anonymous ,

Recurrence trigger has no output, it only assumes the function of periodically triggering Flow, and does not return any value.

So you can't get any Dynamic content when configuring Move file action.

Secondly, the fields in the Flow action have their own types by default, which will automatically match the same type of Dynamic content. If the type of Dynamic content output by the previous action does not match the corresponding field, it may also display "No Dynamic Content Available".

If you mean that the action below the Move file action cannot use the Dynamic content it outputs, you could try to use Compose to get the desired Dynamic content, then use Compose's output to configure other actions.

Best Regards,

[Anonymous]

HI

Right, I've added the Get Items action. The list field is actually a Document Library. I'm thinking in the File to Move field I need the 'File Identifier' dynamic content but it's not there as an option?  

[Pstork1]

You want the Get Files (Properties Only) action to get the list of files.  This will have the identifier included. Use the properties only one at this point to avoid pulling back a massive amount of data that includes more than you need.

[Anonymous]

Thanks @Pstork1  I came to that realisation with the around the same time when I read over your post, changed it and it works! One question, would the 'When a file is created' trigger work independent of the Recurrence? So if the Recurrence is set to once a day will a file be moved as soon as it's added because of the trigger? 

[Pstork1]

Given the placement of the trigger in the screenshot I don't think it will work.  In my experience triggers only work when they are the first action in a Flow.  I think what you might want is Get File Content action.

[Anonymous]

You're quite right, when I put that Trigger in it just chugged along and it didn't do anything. I took it out and it works fine. Where would I need to put the Trigger and Recurrence so that they'd both work? 

[Pstork1]

I've never had any luck trying to use two triggers in a single Flow.  If you think about it the point of the trigger is to start the Flow, so how can you have two.  In this case you want recurrence to start the flow at a point in time, every day or week or month.  Then go get all the docs in the folder and move them. In that scenario you don't need the other trigger.

The alternative design is to trigger the flow whenever a document is created. But I think you were the one who posted elsewhere that it didn't always fire (although it might have been a different requestor). If that is the case doing it for anything that's there once a day is a better design.

[v-bacao-msft]

Hi @Anonymous ,

Perhaps we could focus on your initial needs, what kind of events do you want to achieve through this Flow?

If you want to specify a file in the Folder to be created, move the file to another folder, perhaps you could directly refer to the following configuration:

If you want to transfer the files created the previous day in the specified Folder to another folder, you could refer to this configuration:

If you need additional assistance, please provide more details about your needs.

Best Regards,

[Anonymous]

Hi @Pstork1 

Yes that was me if the earlier question.

@v-bacao-msft  The requirement is that as soon as a file gets added to  folder A it gets moved to a different folder B  with a different name. I've inherhited a flow which is triggered when a file is added to folder A. This  perfectly fine 95% of the time, however the last two weekends the triggered flow has failed leaving files behind in folder A. What I want to build into the flow is a failsafe which will check folder A once or twice over the weekend and will move over any files which have been left behind. 

I realise I could create another scheduled flow to check folder A but that seems incredibly clunky.

[Pstork1 · Accepted solution]

You can't really build a Flow that is Triggered when a file is created and on a scheduled basis.  You could build a Flow that is triggered when a File is created then do a Get Files to see if there are any other files in the Folder and move them all. It would be the same as the recurrence Flow except it would trigger when new files are created. If it doesn't trigger then the file that was left behind will get moved the next time a file is created.  

Otherwise the only real option is two Flows.  One based on when a file is created and another based on recurrence that will copy anything that is missed.

[Anonymous]

Thanks @Pstork1  the penny's dropped! That works, thanks.