How do I use dynamic content from trigger "When a file is created (properties only)" (SharePoint Library) without apply to each?

[Nunya1]

Hello, long-distance friends. I am trying to make a Flow that looks at a SharePoint library, starts the Flow when a new file is created in it, then sends that document for signature in Adobe Sign via e-mail (all one action anyway), then e-mails the signed document to another user.

I am stuck at the very beginning. I started with a template, and the first trigger is "When a file is created (properties only)". All is well and good until I try to use ANY dynamic content from that trigger. I.e. ID, Name, etc. It automatically puts any action in its own apply to each loop. Except that I don't want an apply to each because it's complicated and there may be several, several files in this document library. I just want the newly added one (not modified, just newly added/created) and to be able to refer to that one without using a specific name.

My first test was unsuccessful and never sent me a request to sign. So then I started to put in the actions for Get File and Get File Content. Every time I try to use anything dynamic though, it starts throwing in all of these apply to each envelopes. I don't have a coding background and am very confused. I understand that somehow an array is getting created (through much research, I've learned that's why these apply to each things keep coming up). But I don't know how to stop it or avoid it properly and get the dynamic content I need. I've tried throwing in "Select" and using the filters in Get Files (properties only), but nothing seems to help.

Honestly, my flow is so messy right now that I don't even think a screenshot will help... but here it is just in case...

[trice602 · Accepted solution]

Hi @Nunya1 ,

I was unable to duplicate the loop at the trigger using dynamic content.  In my test, I grabbed the file name and looks accurate.

In your flow, get files is a multi-file action and inherently will wrap itself in a loop because, technically, there may be more than one file in your "get files" action.  There are ways to get around it by using first() and other options.

My recommendation is to replace "get files" and the apply to each(s) with a get file using path (properties only) for SharePoint so you can point to the single file you need from the trigger using the dynamic content "ID".

This action will give the file content you need for your additional actions downstream. 

[Nunya1]

Thank you, @trice602 . I scrapped the whole flow and started over, and it works now. My goodness. I am exhausted! I am crying inside that this stole a whole day from me at work, but I thank you profusely for saving me in my hour of need.

It's working.

[trice602]

Hi @Nunya1 ,

Always great to hear!  Always glad to help!