There were already couple of posts with this topic but without definitive answers.
According to recently published documentation: https://docs.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/cards/cards-format?t...
To include a mention in an Adaptive Card your app needs to include the following elements
And a bit vague code with following example how to add that:
"msteams": {
"entities": [
{
"type": "mention",
"text": "<at>John Doe</at>",
"mentioned": {
"id": "29:123124124124",
"name": "John Doe"
}
Many 3rd party websites are full with information about that ID value - some say it should be Teams user ID (or Azure AD orgID - same thing), but this example format doesn't look like this - i have tried various version with full OrdID, without "-", etc ,even using pure JSON from this article example - all lead to Flow simply failing.
It seems need to have very Teams specific context like that 'id':
"id": "29:1GcS4EyB_oSI8A88XmWBN7NJFyMqe3QGnJdgLfFGkJnVelzRGos0bPbpsfJjcbAD22bmKc4GMbrY2g4JDrrA8vM06X1-cHHle4zOE6U4ttcc",
"objectId": "9d3e08f9-a7ae-43aa-a4d3-de3f319a8a9c",
"givenName": "Larry",
"surname": "Brown",
"email": "Larry.Brown@fabrikam.com",
"userPrincipalName": "labrown@fabrikam.com"
Any idea how to retrieve that from the team? Some Graph query maybe?
Is there's anything else required for "Post your own adaptive card as Flow bot to a channel" to simply process this mentions ? And also, how to make it multi-user if this is possible?
Solved! Go to Solution.
Managed to self-resolve it , instead of trying to get that "29:" Teams ID bot ID context, using "8:orgid" instead:
"type": "mention",
"text": "<at>John Doe</at>",
"mentioned":
{
"id": "8:orgid:{org-ID-of-the-user}",
"name": "John Doe",
}
Managed to self-resolve it , instead of trying to get that "29:" Teams ID bot ID context, using "8:orgid" instead:
"type": "mention",
"text": "<at>John Doe</at>",
"mentioned":
{
"id": "8:orgid:{org-ID-of-the-user}",
"name": "John Doe",
}
Hi,
Its great that you were able to solve your issue here. It looks like graph was doing some interesting transforming of the data which made it a little unintuitive.
Regards,
Alex
-------
Community Support Team _ Alex Rezac
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I think main issue here that all @ metnions in adaptive cards documentation only says 29:xxxxxxxxxx ID in Bot Framework context. I posted GitHub query on that documentation page and got reply with screenshot saying that 29:xxxxx ID is obtainable via Bot Builder etc. But for Flow this is not very intuitive indeed to use that - would make so much sense to make <at> work like they do in the Flow bot messages without jumping via hoops of determining orgID etc.
For example, I want to have @ mentions in the adaptive card dynamically generated - with <at>User1</at>,<at>User2</at>, etc it's quite simple to make Flow read this from SPO list for example, but when i need to make dynamically generated list of users to mention in form of string which looks like this: {"type":"mention","text":"<at>User1</at>","mentioned":{"id":"8:orgid:1234etc","name":"User1",}},{"type":"mention","text":"<at>User2</at>","mentioned":{"id":"8:orgid:5678etc","name":"User2",}}, - and then still have to match all these users with <at>User1</at>, <at>User 2</at> - it's is such overengineering to be honest..
Hey vbvbvb,
Could you help with an example on how to get the orgid and org-ID-of-the-user in your example?
"id": "8:orgid:{org-ID-of-the-user}"
Also, should I always use "8:" at the front?
Thanks!
Hi @Anonymous ,
OrgID or objectID can be obtained via multiple ways - get Azure AD user, via Graph query , etc. As example:
Get-ADUser -Identity user -Properties * > look for objectGUID
8:orgid: always has to be there, followed by user object ID (orgID), for example:
"id": "8:orgid:e1418d64-096c-4cb0-b903-ebb66562d99d"
I managed to automate that via Flow too via HTTP request to Azure AD action using Graph query :
https://graph.microsoft.com/v1.0/users?$filter=mail eq 'jon.doe@contoso.com'&$select=id
Output would be like this and you just have to use Pase JSON to get dynamic value for orgID to use (for example write to SPO list of something to use later in @metnions .
Hi vbvbvb,
Thanks for the quick response! I have tested it out in a simple card with just text and it seems to be working.
I'm having trouble integrating this into my actual adaptive card that looks abit like this below.
I read that the msteams entities part of the code should be placed after the $schema.
Could you help to take a look to see where it should be included?
{
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"type": "AdaptiveCard",
"version": "1.0",
"body": [
{
"type": "TextBlock",
"text": "Mention_Test",
"weight": "Bolder",
"size": "Medium"
},
{
"type": "ColumnSet",
"columns": [
{
"type": "Column",
"width": "stretch",
"items": [
{
"type": "TextBlock",
"spacing": "None",
"text": "Created 1234",
"isSubtle": true,
"wrap": true
}
]
}
]
},
{
"type": "TextBlock",
"text": "<at>testing</at>",
"size": "Medium",
"wrap": true
},
"msteams": {
"entities": [
{
"type": "mention",
"text": "<at>testing</at>",
"mentioned": {
"id": "8:orgid:baae7aa8-035a-zzzz-yyyy-xxxx",
"name": "test123"
}
}
]
}
]
}
Hi @Anonymous,
I think you need to correct two things in your json. Try and use version 1.2 of the schema. They added mentioned support in that one:
Also the name of the user was different in the mentioned section. So I changed that too.
Here is a new code snippet:
{
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"type": "AdaptiveCard",
"version": "1.2",
"body": [
{
"type": "TextBlock",
"id": "MentionTextBlock",
"text": "Mention_Test",
"weight": "Bolder",
"size": "Medium"
},
{
"type": "ColumnSet",
"id": "MentionColumnSet",
"columns": [
{
"type": "Column",
"id": "MentionColumn",
"width": "stretch",
"items": [
{
"type": "TextBlock",
"id": "MentionTextBlock2",
"spacing": "None",
"text": "<at>Testing</at>",
"isSubtle": true,
"wrap": true
}
]
}
]
}
],
"msteams": {
"entities": [
{
"type": "mention",
"text": "<at>Testing</at>",
"mentioned": {
"id": "8:orgid:yourid",
"name": "Testing"
}
}
]
}
}
Is the OrgID constant for every user in a org?
Hi @AlexBal,
Like mentioned by @vbvbvb it's the user object ID. So it will be different for every user.
Indeed, @AlexBal , it would be different for every user, but constant throughout the tenant.
I'm having a problem having a dynamic username for the mention. Have you come up with a way to do this? The solution I am using appears to break in Android, but works successfully everywhere else.
@cdn4lf works fine in Adaptive cards in Android and visually still in iOS, but using that method with OrgID slightly break card design and this bug is get worked on already. If in you case you just get blank card in Android when @ mentions are used, you have issue in card JSON. Try to reduce card code it to bare minimum, ensure you are using adaptive card version 1.2+ etc.
@vbvbvb here is the link to my other post /question. Would you be able to assist with correcting the issue?
https://powerusers.microsoft.com/t5/Building-Flows/Teams-Adaptive-Card-Mentions/m-p/650918#M87114
I think you have to be sure that both mention TextBlock and msteams part have "Name, Surname" identical to that in 'name':
"items": [ { "type": "TextBlock", "id": "MentionTextBlock2", "spacing": "None", "isSubtle": true, "wrap": true, "text": "Dear <at>{$root.Name} {$root.Surname}</at>," }
"msteams": {
"entities": [
{
"type": "mention",
"text": "<at>{$root.Name} {$root.Surname}</at>",
"mentioned": {
"id": "8:orgid:{$root.id}",
"name": "{$root.Name} {$root.Surname}"
}
}
]
},
When I attempt to use your suggestion I get an invalid json error when attempting to launch the flow.
The request failed. Error code: 'MissingOrInvalidBotAdaptiveCardRequest'. Error Message: 'The specified Teams flowbot adaptive card request is missing or invalid. The tracking Id is '23fc4d80-7b06-4261-9073-0232d4c77de1'.'.
When I switch it back to <at>username</at>, everything works. What it appears to be is that the Android version of Teams isn't reading the mention the same way, when part of an adaptive card, and is falling back to the static name of the mention instead of the dynamic code.
Probably you would have to change the way how Name, Surname is populated. Can't you use HTTP to Azure AD query or Get O365 user action and use returned DisplayName value to use in mentions?
@vbvbvb I am using the 0365 connector to get the employee information from AD. From there, I am get their unique ID as well as their display name/surname/given name.
The problem is that Android is falling back to the default text and not properly reading the information. Apparently this could be due to issues with the developer preview.
From what I understand, the <at>name</at> is a placeholder and references the mention entity below. The name within that mention entity is what is supposed to appear, but doesn't due to the issues with the developer preview.
Using the mention token called within Power Automate also doesn't work within the new card editor, as it simply passes the information then fails.
Considering my complete lack of knowledge, I had a hard time using the orgid method. If it can be of any help, I added this to the adaptive card and it worked perfectly fine for what I needed.
{
"type": "TextBlock",
"text": "<at>youradress@mail.com</at>",
}
@Hellder Can you please share how you added that to your card and the complete syntax please? I also want to achieve this.
Episode Seven of Power Platform Connections sees David Warner and Hugo Bernier talk to Microsoft MVP Dian Taylor, alongside the latest news, product reviews, and community blogs. Use the hashtag #PowerPlatformConnects on social media for a chance to have your work featured on the show! Show schedule in this episode: 0:00 Cold Open 00:30 Show Intro 01:02 Dian Taylor Interview 18:03 Blogs & Articles 26:55 Outro & Bloopers Check out the blogs and articles featured in this week’s episode: https://francomusso.com/create-a-drag-and-drop-experience-to-upload-case-attachments @crmbizcoach https://www.youtube.com/watch?v=G3522H834Ro/ @pranavkhuranauk https://github.com/pnp/powerapps-designtoolkit/tree/main/materialdesign%20components @MMe2K https://2die4it.com/2023/03/27/populate-a-dynamic-microsoft-word-template-in-power-automate-flow/ @StefanS365 https://d365goddess.com/viva-sales-administrator-settings/ @D365Goddess https://marketplace.visualstudio.com/items?itemName=megel.mme2k-powerapps-helper#Visualize_Dataverse_Environments @MMe2K Action requested: Feel free to provide feedback on how we can make our community more inclusive and diverse. This episode premiered live on our YouTube at 12pm PST on Thursday 30th March 2023. Video series available at Power Platform Community YouTube channel. Upcoming events: Business Applications Launch – April 4th – Free and Virtual! M365 Conference - May 1-5th - Las Vegas Power Apps Developers Summit – May 19-20th - London European Power Platform conference – Jun. 20-22nd - Dublin Microsoft Power Platform Conference – Oct. 3-5th - Las Vegas Join our Communities: Power Apps Community Power Automate Community Power Virtual Agents Community Power Pages Community If you’d like to hear from a specific community member in an upcoming recording and/or have specific questions for the Power Platform Connections team, please let us know. We will do our best to address all your requests or questions.
Super Users – 2023 Season 1 We are excited to kick off the Power Users Super User Program for 2023 - Season 1. The Power Platform Super Users have done an amazing job in keeping the Power Platform communities helpful, accurate and responsive. We would like to send these amazing folks a big THANK YOU for their efforts. Super User Season 1 | Contributions July 1, 2022 – December 31, 2022 Super User Season 2 | Contributions January 1, 2023 – June 30, 2023 Curious what a Super User is? Super Users are especially active community members who are eager to help others with their community questions. There are 2 Super User seasons in a year, and we monitor the community for new potential Super Users at the end of each season. Super Users are recognized in the community with both a rank name and icon next to their username, and a seasonal badge on their profile. Power Apps Power Automate Power Virtual Agents Power Pages Pstork1* Pstork1* Pstork1* OliverRodrigues BCBuizer Expiscornovus* Expiscornovus* ragavanrajan AhmedSalih grantjenkins renatoromao Mira_Ghaly* Mira_Ghaly* Sundeep_Malik* Sundeep_Malik* SudeepGhatakNZ* SudeepGhatakNZ* StretchFredrik* StretchFredrik* 365-Assist* 365-Assist* cha_cha ekarim2020 timl Hardesh15 iAm_ManCat annajhaveri SebS Rhiassuring LaurensM abm TheRobRush Ankesh_49 WiZey lbendlin Nogueira1306 Kaif_Siddique victorcp RobElliott dpoggemann srduval SBax CFernandes Roverandom schwibach Akser CraigStewart PowerRanger MichaelAnnis subsguts David_MA EricRegnier edgonzales zmansuri GeorgiosG ChrisPiasecki ryule AmDev fchopo phipps0218 tom_riha theapurva takolota Akash17 momlo BCLS776 Shuvam-rpa rampprakash ScottShearer Rusk ChristianAbata cchannon Koen5 a33ik Heartholme AaronKnox okeks Matren David_MA Alex_10 Jeff_Thorpe poweractivate Ramole DianaBirkelbach DavidZoon AJ_Z PriyankaGeethik BrianS StalinPonnusamy HamidBee CNT Anonymous_Hippo Anchov KeithAtherton alaabitar Tolu_Victor KRider sperry1625 IPC_ahaas zuurg rubin_boer cwebb365 Dorrinda G1124 Gabibalaban Manan-Malhotra jcfDaniel WarrenBelz Waegemma drrickryp GuidoPreite If an * is at the end of a user's name this means they are a Multi Super User, in more than one community. Please note this is not the final list, as we are pending a few acceptances. Once they are received the list will be updated.
Join us for an in-depth look into the latest updates across Microsoft Dynamics 365 and Microsoft Power Platform that are helping businesses overcome their biggest challenges today. Find out about new features, capabilities, and best practices for connecting data to deliver exceptional customer experiences, collaborating, and creating using AI-powered capabilities, driving productivity with automation—and building towards future growth with today’s leading technology. Microsoft leaders and experts will guide you through the full 2023 release wave 1 and how these advancements will help you: Expand visibility, reduce time, and enhance creativity in your departments and teams with unified, AI-powered capabilities.Empower your employees to focus on revenue-generating tasks while automating repetitive tasks.Connect people, data, and processes across your organization with modern collaboration tools.Innovate without limits using the latest in low-code development, including new GPT-powered capabilities. Click Here to Register Today!
We are excited to share the ‘Power Platform Communities Front Door’ experience with you! Front Door brings together content from all the Power Platform communities into a single place for our community members, customers and low-code, no-code enthusiasts to learn, share and engage with peers, advocates, community program managers and our product team members. There are a host of features and new capabilities now available on Power Platform Communities Front Door to make content more discoverable for all power product community users which includes ForumsUser GroupsEventsCommunity highlightsCommunity by numbersLinks to all communities Users can see top discussions from across all the Power Platform communities and easily navigate to the latest or trending posts for further interaction. Additionally, they can filter to individual products as well. Users can filter and browse the user group events from all power platform products with feature parity to existing community user group experience and added filtering capabilities. Users can now explore user groups on the Power Platform Front Door landing page with capability to view all products in Power Platform. Explore Power Platform Communities Front Door today. Visit Power Platform Community Front door to easily navigate to the different product communities, view a roll up of user groups, events and forums.
We are so excited to see you for the Microsoft Power Platform Conference in Las Vegas October 3-5 2023! But first, let's take a look back at some fun moments and the best community in tech from MPPC 2022 in Orlando, Florida. Featuring guest speakers such as Charles Lamanna, Heather Cook, Julie Strauss, Nirav Shah, Ryan Cunningham, Sangya Singh, Stephen Siciliano, Hugo Bernier and many more. Register today: https://www.powerplatformconf.com/
User | Count |
---|---|
84 | |
31 | |
30 | |
25 | |
24 |
User | Count |
---|---|
114 | |
59 | |
47 | |
44 | |
41 |