Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

adaptive cards example gives an error #423

Closed
dampee opened this issue Nov 11, 2018 — with docs.microsoft.com · 7 comments
Closed

adaptive cards example gives an error #423

dampee opened this issue Nov 11, 2018 — with docs.microsoft.com · 7 comments
Assignees
Labels
Area: actionable messages Feedback on actionable message content

Comments

Copy link

dampee commented Nov 11, 2018

If you try this against a MicrosoftTeams incoming webhook. Teams will return the error: "Summary or Text is required."


Documentdetails

Dit gedeelte niet bewerken. Het is vereist om problemen te koppelen tussen docs.microsoft.com en GitHub.

@jasonjoh jasonjoh added the Area: actionable messages Feedback on actionable message content label Nov 12, 2018
@jasonjoh
Copy link
Contributor

Thanks @dampee. As far as I know Teams doesn't support adaptive via webhook. Why are you using this Outlook documentation against a Microsoft Teams webhook?

@jasonjoh
Copy link
Contributor

@dampee Does the Teams documentation point you here perhaps? If they're leading you down the wrong path I want to make sure that gets addressed :)

@mastef
Copy link

mastef commented Nov 26, 2018

@jasonjoh When you're in Microsoft Teams and are configuring the webhooks connector, you are being sent here.

image

The first link ( "Office 365 connector format" ) sends you to the legacy docs https://go.microsoft.com/fwlink/?linkid=837668

And the second link ( "Get started with Office 365 Connector Cards." ) sends you here http://aka.ms/o365-connectors

@jasonjoh
Copy link
Contributor

Thanks @mastef! That link takes you to https://docs.microsoft.com/en-us/outlook/actionable-messages/actionable-messages-via-connectors, which uses MessageCard format (not Adaptive). Perhaps it would be helpful to add a note to the top of that page that states Adaptive isn't supported by connectors.

@mastef
Copy link

mastef commented Nov 26, 2018

I'm not 100% sure as I just started exploring this today, but that's how I ended up looking through the outlook docs, instead of the microsoftteams docs. Might act as an entry point

jasonjoh added a commit that referenced this issue Jan 7, 2019
Added note to clarify that only actionable messages sent via email to Outlook support Adaptive Card, and that O365 connectors and Teams connectors must continue to use MessageCard.

Fixes #423
@swissarmychainsaw
Copy link

swissarmychainsaw commented Feb 2, 2020

Thanks @dampee. As far as I know Teams doesn't support adaptive via webhook. Why are you using this Outlook documentation against a Microsoft Teams webhook?

Here is the page, and in my mind it clearly implies that Adaptive Cards are supported by Teams: https://docs.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/cards/cards-reference#adaptive-card

Types of cards
This table shows the types of cards available to you.
"Adaptive Card"

Farther down it shows an X for "connectors" which I guess means it won't work.

@Gregster66
Copy link

Thanks @dampee. As far as I know Teams doesn't support adaptive via webhook. Why are you using this Outlook documentation against a Microsoft Teams webhook?

Here is the page, and in my mind it clearly implies that Adaptive Cards are supported by Teams: https://docs.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/cards/cards-reference#adaptive-card

Types of cards
This table shows the types of cards available to you.
"Adaptive Card"

Farther down it shows an X for "connectors" which I guess means it won't work.

That document states that Adaptive Cards work with some aspects of MS Teams, like Bots. You can see that it states that using Connectors is not supported, and wehbooks fall under the category of "Connectors"

@ghost ghost locked as resolved and limited conversation to collaborators Jul 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Area: actionable messages Feedback on actionable message content
Projects
None yet
Development

No branches or pull requests

5 participants