microsoft / microsoft/AdaptiveCards
[Rendering] Power Automate's "Get an @mention token for a user" action generates the correct <at>...</at> but the Workflows bot is no longer able to render user @mentions
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2k
- Forks
- 595
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 1
Description
Target Platforms
Other
SDK Version
1.5
Application Name
Microsoft Teams
Problem Description
This action in Power Automate would generate a HTML-like tag to the effect of <at>user-id</at> :
Cards posted by the Workflows app used to be able to render this correctly, but now it can only be rendered properly by cards posted as a user:
Screenshots
Card JSON
{
"$schema": "https://adaptivecards.io/schemas/adaptive-card.json",
"type": "AdaptiveCard",
"version": "1.5",
"msteams": {
"width": "full"
},
"body": [
{
"type": "TextBlock",
"text": "Dear Executive Staff, please be aware of the following meeting that has been scheduled. A calendar entry has also been created within the mailboxes of those notified.",
"wrap": true,
"color": "Accent",
"size": "Small"
},
{
"type": "TextBlock",
"text": "Staff notified: @{outputs('Get_an_@mention_token_for_a_user')?['body/atMention']}",
"wrap": true,
"size": "Small",
"color": "Accent"
}
],
"msTeams": {
"width": "full"
}
}
Sample Code Language
No response
Sample Code
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue identifies no repository file, test, or entry point. Start by reproducing the supplied Adaptive Card JSON through the Workflows bot and compare it with a card posted as a user; done means determining whether the regression is in this project and documenting or fixing the rendering behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100