You’re offline. This is a read only version of the page.
Hi all,
Newbie to power automations here, but I have a basic work flow set up to copy files from Site A to Site B, and Site B to Site A, when the files are created or modified in specific subfolders defined using a conditional statement.
So let's say the only folders I'm interested in are "Monthly, Quarterly, and Yearly". Let's say I'm not interested in new files in any other folders. I only want to see successful and failed workflows if the subfolders consist of "Monthly", "Quarterly", or "Yearly" folders. I do not want the workflow history if any other folder is touched.
So if my condition is "Folder Path contains [Monthly OR Quarterly OR Yearly], and it performs the copy action when the expression is true, is there a way on the false expression to remove the flow action from the history.
Otherwise I am going to see thousands of workflows each week, when for system health I'm really only interested in actions affecting the specified folders.
Thank you!
Sincerely,
Dave Childers
Ah, sorry about that - I guess I overlooked the article. Thank you, to both of you!
Mahoneypat,
Super! This looks like it's working perfectly! I would never have figured this out without your help, only been using Power Automation flows for a few weeks.
Sincerely,
Dave Childers
You could use a trigger condition like this in the settings of your trigger. That way the flow will only trigger when the file is created in one of your Folders of interest. Replace Folder1 and Folder2 with Yearly, Monthly, etc..
@Anonymous(contains(triggerOutputs()?['body/{Path}'], 'Folder1'), contains(triggerOutputs()?['body/{Path}'], 'Folder1'))
Pat
I Appreciate the response. That's too bad, because building it on the specific folders would mean having to build 500-600 individual workflows. Right now I have it *almost* working with two workflows that trigger with any change in the library, but stops at the first conditional that checks the specific folder path with the triggering item.
The flow history will show any flow that runs. So the only way to keep a flow out of the flow history would be to use a trigger condition that prevents the flow from running when that trigger condition isn't met. Here's a good introduction to trigger conditions.
Power Automate Trigger Conditions made EASY - Power Platform Community (microsoft.com)
#1
Tomac
986
Moderator
#2
stampcoin
699
Super User 2025 Season 2
#3
Riyaz_riz11
577
Super User 2025 Season 2
Share
Report
All responses (
Answers (
