Solved: Re: Open attachment - Powerapps custom form - Shar...

CP153319 · ‎03-12-2018

I created a custom Powerapps form for a SharePoint list and was excited to utilize the new functionality of adding an attachment. It works great when adding a new item to the list (powerapp form opens, fill out the various fields, add attachment, save). The problem occurs when I open an existing list item (which also opens in the powerapps form) - when I click on the attachment to open it nothing happens.

Wondering if I have to have separate forms? One to attach the attachemnt and one to view it?

Thank you for reading.

Anonymous · ‎04-26-2018

I did not find a workaround how to fix this in View Form as this mode makes OnSelect event inaccessible, but this approach can help with opening attachments from list items in DataTable or EditView.

In OnSelect event you may use the following function which will open the first attachment:

Launch(Concatenate("{your list URI}","/Attachments/",Text({Item ID}),"/", First({item}.'{Attachments}').DisplayName))

If you are using Data Table then:

- replace Item ID with DataTable.Selected.ID and use the function in OnSelect event on any column

- replace item with DataTable.Selected

If you are using Edit View Form then:

- replace Item ID with ThisItem.ID and use the function in OnSelect event in the Attachment field or any other custom card

- replace item with ThisItem

In many cases, users require only one attachment, so this can be viable.

Hopefully, MS will fix this not opening attachments bug soon.

Fingers crossed.

Cheers

View solution in original post

Rebetcha · ‎03-12-2018

I did some testing. In my case the attachment started to download the moment I clicked it once. There is an on select property on the attachment control but did not figure out yet how to open an attachment on click. According to the support article this should be possible. https://docs.microsoft.com/en-us/powerapps/controls/control-attachments

v-monli-msft · ‎03-13-2018

Hi @CP153319,

I just tested with this new attachment feature rto open the exsiting attachment on web browser and I got the same result. After I click on the exsiting file, a popup window asks if this should be allowed. After I allowed it, it went back to the list view, the file is not opened. I will try to report this issue to pg and see if they have any suggestions.

Regards,

Mona

Community Support Team _ Mona Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

v-monli-msft · ‎03-13-2018

Hi @CP153319,

I just tested again with Chrome and Edge, both could download/open the Excel file. It seems that this issue only happens in IE from my side. Would you please change to these browsers to have a test?

Regards,

Mona

Community Support Team _ Mona Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Rebetcha · ‎03-13-2018

I tried it out in IE and Edge. In Edge it works fine, except in inprivate. IE doesn't work. Attachment does not open.

Anonymous · ‎03-15-2018

I have been fighting with this for hours without much sucess. Attachment opens in Firefox. But in IE11 (which is what all the intended users of this form use) it now opens a separate tab with a URL blob:CEE2CD22-7D22-40F9-B20C-915FD7FFC163

Rebetcha · ‎03-16-2018

That sounds like a bug. The ability to open attachments is fairly new. It is likely that something is not working as it should. I would recommend to create a support ticket through Office 365 Admin Center.

CP153319 · ‎03-19-2018

I haven't had a chance to test this on another browser (where I work eveyone is on IE and it's extremely difficult to get software installed on our machines(locked down pretty tight here)). Doesn't really matter for me if it works on Chrome or Edge anyways... I need it to work on IE. I imagine there are a few zillion people in the same boat.

Rebetcha · ‎03-19-2018

@v-micsh-msft: the SharePoint list item attachment functionality does not work as it should in IE (for mor info, read this thread). Can you log this as a bug with the product team?