microsoft / microsoft/AdaptiveCards
[Rendering] Power Automate "Post to a Teams channel/chat" only supports v1.4
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
N/A
Application Name
Microsoft Teams
Problem Description
This documentation says v1.5 is supported in Teams, but the "Post to a channel/chat when a webhook request is received" Power Automate workflow still only supports v1.4.
Posting to Teams via o365 connector is getting removed, we rely on v1.5 features to be able to display our automated messages correctly.
Screenshots
No response
Card JSON
{
"type": "AdaptiveCard",
"body": [
{
"type": "TextBlock",
"size": "Medium",
"weight": "Bolder",
"text": "${title}"
},
{
"type": "Table",
"columns": [
{
"width": 1
},
{
"width": 1
},
{
"width": 1
}
],
"rows": [
{
"type": "TableRow",
"cells": [
{
"type": "TableCell"
},
{
"type": "TableCell"
},
{
"type": "TableCell"
}
]
},
{
"type": "TableRow",
"cells": [
{
"type": "TableCell"
},
{
"type": "TableCell"
},
{
"type": "TableCell"
}
]
},
{
"type": "TableRow",
"cells": [
{
"type": "TableCell"
},
{
"type": "TableCell"
},
{
"type": "TableCell"
}
]
}
]
}
],
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"version": "1.5"
}
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
Start with the linked Teams adaptive-card support documentation and the supplied v1.5 card JSON. Verify whether the Power Automate workflow is within this repository’s scope and identify where its supported card version is controlled. Done means the workflow accepts the reported v1.5 features, or the issue is redirected if that behavior is external.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100