{"id":342,"date":"2022-12-23T11:41:44","date_gmt":"2022-12-23T11:41:44","guid":{"rendered":"http:\/\/4us2use.at\/?p=342"},"modified":"2022-12-23T12:01:30","modified_gmt":"2022-12-23T12:01:30","slug":"patch-powerapps-attachment-to-sharepoint-library","status":"publish","type":"post","link":"http:\/\/4us2use.at\/?p=342","title":{"rendered":"Patch PowerApps Attachment to SharePoint Library"},"content":{"rendered":"\n

Problem: <\/strong><\/p>\n\n\n\n

You can’t easily patch a file (any filetype) directly to a SharePoint Library (it’s different than working with a SharePoint list!). For this it takes several steps as a workaround.<\/p>\n\n\n\n

Solution:<\/strong><\/p>\n\n\n\n

As a very first step create a new PowerApp and connect it with your library.
Secondly connect ANY SharePoint list to the app where attachments are enabled and embed an edit form for both lists.<\/p>\n\n\n\n

\"\" <\/p>\n\n\n\n

In the form of the library add a custom data card and copy the attachment field from the list form to the empty custom data card – you can remove the error for “Parent.Default” by just deleting it. Afterwards you can also remove the data connection to the list and the related form since we just needed it temporary to copy over the attachment control. It should look simply like this:
\"\"<\/p>\n\n\n\n

Not the trick begins…
If you upload an attachment and check it’s value, you’ll just see a URI for a temporary blob storage like in my example: appres:\/\/blobmanager\/36446683a549421988f5b9f4b3bbdbb2\/1<\/p>\n\n\n\n

This format can not be used for further processing!
This is why we require a temporary image control.
Set the Image <\/strong>property of this control to:
L<\/em>ast(fileUpload.Attachments).Value<\/em> <\/strong>
(where fileUpload is the name of my attachment control)<\/p>\n\n\n\n

Now we need convert the output of the Image to a format we’ll be able to use later in a Power Automate Flow to create the file in the SharePoint library. For better understanding I’ll split the steps to not complicate the formula.<\/p>\n\n\n\n

In the OnAddFile <\/strong>property of the attachment add following formulas:
(if you place any label and set it’s Text property to the variable, you can see what happens)
Set(varFileContent,JSON(imgTEMP.Image,JSONFormat.IncludeBinaryData))<\/strong>;
Set(varFileStreamBase64,Mid(varFileContent,Find(“,”,varFileContent)+1));
Set(varFileStreamBase64Final,Substitute(varFileStreamBase64,””””,””));<\/em><\/strong><\/p>\n\n\n\n

Explanation:
In the first line we extract the Base64 encoded file content.
Next we remove the beginning of the file until “…Base64,” – this is where the real file content starts.
Last but not least we’re removing the character ” from the end of the file content string.<\/p>\n\n\n\n

Now we need a Flow – just create a new Flow out of your PowerApp like this:
\"\"<\/p>\n\n\n\n

Now we just need to add a button to test.
OnSelect: ‘
Po<\/strong><\/em>werApps-UploadFileToSharePointLIBRARY’.Run(Last(fileUpload.Attachments).Name, varFileStreamBase64Final)<\/em><\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

That’s it – I hope you enjoy and buy me a beer \ud83d\ude09<\/p>\n\n\n\n\"1\"2\"3\"4\"5 (No Ratings Yet)
<\/span><\/span>Loading...<\/span>\n","protected":false},"excerpt":{"rendered":"

Problem: You can’t easily patch a file (any filetype) directly to a SharePoint Library (it’s different than working with a SharePoint list!). For this it takes several steps as a workaround. Solution: As a very first step create a new PowerApp and connect it with your library.Secondly connect ANY SharePoint list to the app where … <\/p>\n

Continue reading “Patch PowerApps Attachment to SharePoint Library”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[11,6],"tags":[],"_links":{"self":[{"href":"http:\/\/4us2use.at\/index.php?rest_route=\/wp\/v2\/posts\/342"}],"collection":[{"href":"http:\/\/4us2use.at\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/4us2use.at\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/4us2use.at\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/4us2use.at\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=342"}],"version-history":[{"count":5,"href":"http:\/\/4us2use.at\/index.php?rest_route=\/wp\/v2\/posts\/342\/revisions"}],"predecessor-version":[{"id":352,"href":"http:\/\/4us2use.at\/index.php?rest_route=\/wp\/v2\/posts\/342\/revisions\/352"}],"wp:attachment":[{"href":"http:\/\/4us2use.at\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=342"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/4us2use.at\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=342"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/4us2use.at\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=342"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}