Power Automate SharePoint Online Move File vs Copy File Behavior

(0) Share

Report

Posted on by sec

I have a workflow A that moves a SharePoint Online document from library 1 to library 2 that runs successfully.

I have a workflow B that triggers when a file is created or modified (properties only) in library 2.

Workflow B will not see that a file is created or modified in libarary 2 when Move file is used. The workflow will not fire at all.

Workflow B WILL see that a file is created or modified in library 2 when Copy file is used.

What is needed to make a workflow see that a file is created or modified when Move File is used?

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (1)

Sort by

MarvinBangert 1,924 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Hi @sec

I guess somewhere back in the SharePoint or Power Automate backend, there is this difference with some metadata (or anything else), that actually triggers the flow. It could be, if you are creating a new file, that there are is some webhook triggered and Power Automate checks for these messages (of the last 5 minutes). Maybe it's something within Power Automate, that checks some metadata - we cannot see / it's definitely not the "created" or "modified" field we can see - if there are new or modified files, unfortunately I cannot 100% answer this, maybe someone else can.

But to answer your question: If you are moving a file to a folder within the new library, it also triggers the flow using "When a file is created or modified (properties only)".

Does this help you? Otherwise please give me some more information.

Best regards
Marvin

If you like this post, give a Thumbs up. If it solved your request, Mark it as a Solution to enable other users to find it.

Blog: Cloudkumpel

Was this reply helpful? Yes No
sec 12 on at

Like (0)

Report
Copy link

Link copied!

Thank you for your post. Your answer is helpful in directing me where to research where the problem may be (potentially metadata).
My need is to move from one library to another, not to a folder within a library, so I would like to keep this open for other suggestions.
I have thought of creating a new column in the destination library with NEW metadata created by the Move Workflow A that may force the Workflow B trigger to see it...could even set it in the trigger condition to specifically look for it - stab in the dark but will give that a go.
Move File should work - should not have to make it work

Was this reply helpful? Yes No
Verified answer

sec 12 on at

Like (0)

Report
Copy link

Link copied!

Workaround used for this issue (for now) is to use Copy file instead of Move file then delete the file in the source.

Was this reply helpful? Yes No