cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Advocate IV
Advocate IV

file upload functionality towards a sharepoint document library

I’ve made an app to test file upload functionality towards a sharepoint document library, using a flow to create the file on sharepoint.

 

It went smooth and worked as expected, I tested two components to select the files, being an ‘attachments’ control, and a MediaButton control (it’s call ‘add picture’ in the GUI).  

 

 

attachment controlattachment controladd image controladd image control

 

Both buttons call the same flow called SendFileToFlow using the code below which stores the file on sharepoint.

 

 

Set(FilePath2, SendFiletoFlow.Run( 
    { file:
        { name: Last(Upload1.Attachments).Name
        , contentBytes:Last(Upload1.Attachments).Value 
    } } 
));

Set(FilePath1, SendFiletoFlow.Run( 
    {file: 
        { name:Upload.FileName
        , contentBytes:Upload.Media 
    }} 
));

 

 

flowflow

 

 

I had a nasty surprise when I tried the same code in the production app. It doesn’t work.

 

Now whenever I copy this working code into a new app, in conjunction with the very same flow, I get this exactly the same error message for each control:

 

new appnew app

So now I’m trying to understand why code is right in one app and wrong in the other.

 

I would assume since the contentBytes ‘type’ in the upload is set by the control it must be the same in every app!

 

How can I troubleshoot this further?

 

Thanks for any response.

 

While browsing the forums I found someone suggesting to add an odata type to the statement.

pic5.png

 

It doesn't seem to help, but maybe I did not get it correctly.

 

Michel

 

 

In both the working and the failing case the control.Attachments.Name and the control.Attachments.Value of the attachments return this:

 

secretstuff.pdf 
appres://blobmanager/1c18e61fbcf34bc4a9dd9bfed5706806/1

 

 

2 REPLIES 2
Resolver I
Resolver I

Hi @MichelH,

 

I'm intrigued by your implementation to get this functionality, and will have to play around with it later!

 

In the meantime, if you'd like you're welcome to use the attachments component + flow I posted recently:

 

https://twitter.com/ohthreesixfive/status/1196945403121324033

 

Feel free to let me know if you run into any issues using it.

 

Cheers!

 

Ramiro

 

Thank you @ohthreesixfive  Ramiro,

 

The flow part is based on what I learned on John Liu's site, so all credits for that go to him and the attachments control taken out of the form and used as a generic upload component is what I saw in a recent video from Shane Young, he was uploading to azure, but the idea is the same, so all credits for that go to him.

 

Great idea to put this upload stuff in a component to (hopefully) assure portability between apps.

I will have a look.

 

Michel

 

Helpful resources

Announcements
New Badges

New Solution Badges!

Check out our new profile badges recognizing authored solutions!

New Power Super Users

Congratulations!

We are excited to announce the Power Apps Super Users!

Power Apps Community Call

Power Apps Community Call: February

Did you miss the call? Check out the Power Apps Community Call here.

Microsoft Ignite

Microsoft Ignite

Join digitally, March 2–4, 2021 to explore new tech that's ready to implement. Experience the keynote in mixed reality through AltspaceVR!

Top Solution Authors
Top Kudoed Authors
Users online (28,518)