Attachment unable to be sent to Sharepoint List through Power Automate

(0) Share

Report

Posted on by BT-20041250-0

I have an app which has been working well all along.

Recently due to an ownership update of the app, together with the other connections, the app started to have unexplained behaviour.

For example, all fields in an approval form can be reflected successfully on the list except the attachment which is reflected as nothing received. No connection issues have been flagged on both power automate and app. In fact, all the runs have been successful.

More info:

Sharepoint list attachments enabled under advanced settings
No changes made to the attachment card on power app:
- DataField={Attachments}
- Update=DataCardValue33.Attachments
- Default=ThisItem.Attachments

Would appreciate any tips, thanks

Update:

Seems like the app is still able to pass attachments to sharepoint, but only for some file types.

.msg files can be attached successfully, while .xlsx files still cannot be attached.

With this new finding, connection should not be an issue then.

Does anyone know if there is a setting somewhere that restricts file types for attachments?

And why is it that xlsx files are suddenly not allowed, when previously there were no issues.

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Vish WR 3,748 on at

Like
a
(0)

Report
Copy link

Link copied!

@BT-20041250-0

Can you recreate the connection and try to test and see if it works!

Vishnu WR

LinkedIn - My Tech Space

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥

Was this reply helpful? Yes No
Suggested answer

11manish 3,333 on at

Like
a
(0)

Report
Copy link

Link copied!

This issue is most likely caused by how attachments are being passed after the ownership and connection update.

While other fields work because they are simple data types, attachments require proper binary content handling.

If you are using Power Automate, ensure you are passing both the file name and content (ContentBytes) correctly.

Also, re-authenticate all connections, verify the flow’s attachment step, and check whether the attachment control is still properly bound.

Even if the flow shows success, the attachment may not be included if the content is not passed correctly.

Was this reply helpful? Yes No
Suggested answer

Kalathiya 2,456 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello @BT-20041250-0,

Could you please confirm or debug following things?

#1. Verify the connection. If it’s not working correctly, please recreate the connection and try again.

#2. Ensure that the transferred owner/user has the required permissions in SharePoint.

#2. If the automation is running successfully, check whether the attachment is being stored in the SharePoint list item correctly and open it. if it's not opening then might be it's corrupted due to the content passed wrong way or file extension issue.
#3. If you are still facing an issue then please share screenshots of:

- Your Power Automation implementation including trigger perameter and add attachment action screen shot.

- From Power Apps - Power Automate trigger code

- Last run history screen shot including that trigger parameters value and add attachment action

If this response resolves your issue, please mark it as the Verified Answer so it can help other community members as well.

---------------------------------------------------------------------------------

📩 Need more help? Just mention @Kalathiya and I’ll be happy to assist.

✔️ If this answer helped you, please tick “Does this answer your question?” so it can be marked as the Verified Answer.

💛 A Like always motivates me to keep contributing!

Was this reply helpful? Yes No
BT-20041250-0 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Update:

Seems like the app is still able to pass attachments to sharepoint, but only for some file types.

.msg files can be attached successfully, while .xlsx files still cannot be attached.

With this new finding, connection should not be an issue then.

Does anyone know if there is a setting somewhere that restricts file types for attachments?

And why is it that xlsx files are suddenly not allowed, when previously there were no issues.

Was this reply helpful? Yes No