Can "Upload file from URL" destination be a SharePoint folder?

[Tiff]

I have a flow set up that starts with a Survey123 submission trigger, generating a feature reporting and then uploading that to OneDrive and subsequently sending an email.

This project is highly collaborative and I would like the reports to reside in a shared SharePoint folder rather than my personal OneDrive. I have not been able to find any resources on how to do so/whether it's possible using the Destination File Path parameter. Any assistance is appreciated!

[MichelleWilliamsERM]

Thank you, I went into TEAMs and there are two types of folders: 

~ OneDrive | My Files (this one works)

OneDrive | Quick Access (in SharePoint - This one is broken)

@Beard_Greg and Robert are you seeing something different on your end?

[Beard_Greg]

@MichelleWilliamsERM,

I didn't see your other messages. Apologies. I'll read those first and respond.

I might not be following along. In the solution, we have it first going to OneDrive then moving it to SharePoint, and then deleting the file in OneDrive. It sounds like your OneDrive link is there, but your SharePoint link isn't (kind of the opposite of what you would actually want out of this flow)?

[MichelleWilliamsERM]

@Beard_Greg Thank you, and I found the issue and I'll share it here for anyone who gets a new computer.

This is a device issue on my new laptop, after having the same issue when I tried to download a WORD feature report template from AGOL I thought I should try my other laptop, and it works fine over there. 

Hip Hip Hooray! 

[Beard_Greg]

Oh Weird! Yes please, share!

I don't have this flow going anymore so I was going to try and rebuild one tonight or this weekend. Thanks for getting back to us.

GB

[Tiff]

Hi @SeanKMcGinnis I think I followed your flow and it worked very well for me last year. I temporarily turned off the flow and once I turned it back on, the HTTP step is not working now. I think my flow has "URL of first result file" not the url parameter, but that looks to be the main difference.

The error I am getting for HTTP step is as follows. Do you have any thoughts on what broke this?

Unable to process template language expressions in action 'HTTP' inputs at line '0' and column '0': 'Required property 'uri' expects a value but got null. Path ''.'. 

[Beard_Greg]

Hey Tiff,

 I know I'm not Sean, but have you tried ESRI's built-in functions instead of the HTTP request?

[Tiff]

Hi @Beard_Greg, which ones are you referring to? I'm open to trying. I just know I had some trouble (and now digging back into these posts) figuring out how to upload to SharePoint easily. Edit - I am seeing your "Get attachment" comment. I can look into that, however I'm nervous to totally rebuild this flow though since that may require updating web hooks (that is also a bit confusing for me sometimes).

[Beard_Greg]

@Tiff 

You can have more than one webhook going to Survey123. I recommend going to https://survey123.arcgis.com/ --> Settings --> Webhooks and then naming your webhook so you don't get confused later on.

Then go into Power Automate and create a copy of your existing flow so you do not damage your original. You'll notice it added a second webhook (might be worth naming this too). You'll have to rebuild some but shouldn't have to start from complete scratch. You'll just have to update your variables. 

[Tiff]

Thanks @Beard_Greg for the tips. I started doing that for the webhooks since I had to make various versions for testing. As for the "Get attachment" action, is this something you are using the pull the automated report that is created? Can you advise on the parameters for the action? For example, my reports are based on a layer and its related records. Should the feature layer be the layer or the related table, and how did you demonstrate the "Attachment" and "Object ID" parameters? Did you need other steps prior to that for it to work?

[Beard_Greg]

Apologies. I was thinking of file uploads again vs creating a report from the information submitted. Looking at what I submitted last time, where does yours differ with an HTTP Request?