Unanswered

Tag in Teams Using Get @mention token for a user Not Working

(0) Share

Report

Posted on by bep7161

Hi all,

I am trying to tag a user in a reply in Teams when a certain criteria is met using the Get @mention token for a user, when I tag myself it runs successfully. However, when I try to tag another user I am getting a error stating "Resource '...@miami.edu' does not exist or one of its queried reference-property objects are not present." Below are my Flow and the Error message that I am receiving:

I appreciate any help that anyone can offer for fixing this issue. Also, I have verified the users email address using Office 365 Users.

Best,

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (0)

FreddieV 157 on at

Like (0)

Report

A couple of things:

I'd personally be interested to see what the output is when Power Automate successfully gets an @mention token for a user.
I note that you appear to be using a private channel (just guessing that based on the name of it)-is the user you are trying to @mention also added to the channel? The error "'One of its queried reference-property objects are not present" appears to hint at this being the case
If they are, then I wonder if your connector has access to ultimately find the user details from AzureAd or whatever.

Was this reply helpful? Yes No
bep7161 2 on at

Like (0)

Report

When I use my profile in the Get @mention token, it runs to success and the reply message is posted and I am tagged just like the two examples below:

You are correct I am testing this in a Private channel, because the use case for this specific flow requires we have a bit more security. I have found that 'Post a message as Flow Bot to a channel' always errors when trying to access a private channel. I researched that and there is no fix for it that I can find. That is why I have turned to this option of getting what I need posted and then replying to it. The other user I am attempting to tag is a member of the Team and private channel, I even made them an owner of both to see if that changed any permissions, but I don't think that is where this error is happening. I even tried to add the step of verifying the user in Office 365 then using 'Mail' from that to get the @mention token and I received the same error.

Was this reply helpful? Yes No
adrianmonteil 2 on at

Like (0)

Report

I have the same problem did you solve it ?

Was this reply helpful? Yes No