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

8013
34
Jump to solution
06-20-2023 02:00 PM
Tiff
by
Frequent Contributor

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!

34 Replies
Tiff
by
Frequent Contributor

Hey @Beard_Greg, no worries - I appreciate your help! By the way, I fixed the issue. Turns out it wasn't a Power Automate issue or anything to do with the authentication. It was my report template. Somehow I tested it and it worked perfectly 3 months ago and revisiting it now, something was up with my syntax for one of the photos. Either way, so glad it is resolved.

My flow with the HTTP request actually directly uploads the created report to SharePoint, so it's an alternative approach to the method you show above. Here's my general flow:

Tiff_0-1711546688193.png

 

0 Kudos
Beard_Greg
Occasional Contributor

NICE! I hate it when that happens. 

Thanks for sharing. Always nice to have an alternative method. Good luck!

0 Kudos
Beard_Greg
Occasional Contributor

@SeanKMcGinnis  / @Tiff , 
Are these flows still working for you? I found this suggestion on another thread a little while ago and it had been working great. Unfortunately the PDFs in SharePoint are coming in empty now. It looks as if they are there, but the files are only 1KB now.

0 Kudos
SeanKMcGinnis
Esri Contributor

@Beard_Greg - I am testing a number of different flows in support of UC presentations and am having no issues.

-sean
Sean McGinnis - ArcGIS for Microsoft 365 Product Manager
0 Kudos
Beard_Greg
Occasional Contributor

Thanks for the quick reply. I'm not sure why it isn't working for me. I'm rebuilding using the ESRI's "Get Attachment" instead of using the HTTP. That seemed to have resolved my issue.

0 Kudos