Answered

MS Power Automate Desktop: cannot access property "attachments" from the output of Teams "Get message details"

(0) Share

Report

Posted on by mgubko

In my Power Automate Desktop I invoke "Get message details" to receive details of Teams message and store output into variable MessageDetails.

I can inspect the content of flow variable MessageDetails, and I see the list "attachments" as one of properties.

However, when I try to use MessageDetails, for example, in "For each" statement, I cannot see "attachments" in the list of available properties. If I enter %MessageDetails.attachments% manually, I get the error that "Variable MessageDetails does not have a property attachments".

How do I access property attachments of the Connector object MessageDetails returned from Teams message "Get message details" step?

Categories:

Power Automate Desktop

I have the same question (0)

All responses (7)

Answers (1)

Sort by

Deenuji_Loganathan_ 6,255 Moderator on at

Like (0)

Report
Copy link

Link copied!

@mgubko

If possible could you pls share screenshot of your flow after hiding all sensitive info?

Was this reply helpful? Yes No
mgubko 13 on at

Like (0)

Report
Copy link

Link copied!

Thanks for the fast answer. Post updated, screenshot added.

Was this reply helpful? Yes No
Deenuji_Loganathan_ 6,255 Moderator on at

Like (0)

Report
Copy link

Link copied!

@mgubko

There appears to be a bug in the "get message details" action as it doesn't display the attachments property. Please report this issue with microsoft.

However, another workaround is as follows: Instead of using "Get message details," utilize "Get messages." Then, using a for-each loop, you can apply the necessary filters using an if condition (if required), and you'll obtain a list of attachments. This approach will display all attachment names individually.
However, neither "Get message details" nor "Get messages" returns the content data of attachments.

Thanks,
Deenuji Loganathan 👩‍💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥

-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀

Was this reply helpful? Yes No
mgubko 13 on at

Like (0)

Report
Copy link

Link copied!

@Deenuji, thanks a lot. The workaround you suggested helps, but then a similar bug appears on the next step:
1. I initialize LatestMessage to the 1st element the list of all messages.
2. Now I can iterate for each attachment in LatestMessage.attachments.
3. But when I want to use the content of attachment, the flow does not see its property contentURL.
4. As before, in the inspector window I can see all properties.

Any idea how to access the properties of attachment?

Was this reply helpful? Yes No
Verified answer

Deenuji_Loganathan_ 6,255 Moderator on at

Like (1)

Report
Copy link

Link copied!

@mgubko

Seems like a bug in teams cloud package. that's why I mentioned this point in my previous point as well.

"However, neither "Get message details" nor "Get messages" returns the content data of attachments."

It will just return the file name that's it. not able to get the content data using those actions. please feel free to raise this issue with Microsoft.

Thanks,
Deenuji Loganathan 👩‍💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥

-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀

Was this reply helpful? Yes No
mgubko 13 on at

Like (0)

Report
Copy link

Link copied!

Thanks for helping, @Deenuji , but even raising a bug to Microsoft raises a bug for me (updated app this morning 😀)

Was this reply helpful? Yes No
mgubko 13 on at

Like (1)

Report
Copy link

Link copied!

In fact, the hack is to convert attachment to JSON and then ingest URL using text functions. But this is, of course, weird.

Was this reply helpful? Yes No