Is there a trigger for SharePoint Document Library for a file added or modified in ANY folder not just a specific one?

[ralphrmsn]

The core issue for a SharePoint Document Library where Folders are used (yes, folders instead of using column meta data and views to group them), is that the trigger appears to only work with a single folder and will ignore sub folders or items below.  This effectively means if we want to handle changes to a document library based on new or updated items, we will have multiple and potentially dozens (or hundreds!) of triggers for every individual folder and, to make matters worse, we would have to duplicate the main flow for all of those folders every time a new folder is added (to which is there is no available automate to duplicate the flow for the newly added folder).  

When running the flow, there appears to be a "check" when an item is added to the document library so we know the act does trigger something but because it then looks to see if the item is in the folder specified, it essentially "ends".   

Is there a trigger that will by pass the check for the folder in SharePoint for a document?  And if not, what is the alternative for this?  Thank you! 

[AnthonyAmador]

Hi @ralphrmsn 

For what I know to this day, there's no way to do this, you can vote for this idea at this link 

Trigger When File is created or modified on folder... - Power Platform Community (microsoft.com)

If anyone has a workaround for this problem, feel free to join. 

Hope this helps.

Cheers. 

[ralphrmsn · Accepted solution]

Ok so, it turns out the issue is that the trigger chosen was the one where File is Created or Modified IN A FOLDER which, of course, will ask for a folder.  On twitter they implied that there was a "file modified" where you can specific columns but that was a red herring that did lead to me looking up ALL the File create choices and the one that should have been used was the one that was File Create but also had "(properties only)" .... it was the properties only "tag" on the end of the trigger name that threw us off.  When using that one, the folder is NOT required which means any file added to any folder will trigger the flow!  

This was part of a copy action so the thought was with the "In folder" piece, I could get the content directly but there is also a Get Content action for files anyway so the fix is simple:

1) Get new file or modified (properties only)

2) use the properties to get the Identifier (don't use ID folks!) for anything involving file operations

3) use the properties for just about anything else you want to do but know you need to have the action to do it and you don't get content or other things for free 

Thanks again for looking at this!