Forum Discussion
jocsch
May 05, 2023Brass Contributor
Secondary actions in adaptive cards broken for channel conversation
I have a strange behaviour in teams where an adaptive card is rendered differently depending on if the bot is posting it in a chat or in a teams channel. The adaptive card (reduced to the absolut...
jocsch
Jun 15, 2023Brass Contributor
Any updates here? I have retested and it is still inconsistent in the image handling.
Even worse, adding a secondary action now seems to block the rendering of the adaptive card in the IOS app completely.
Even worse, adding a secondary action now seems to block the rendering of the adaptive card in the IOS app completely.
Meghana-MSFT
Jun 18, 2023Former Employee
Apologies for the delay, we do not have any update to share. We are following up with engineering team for updates. We will keep you posted.
- DagwaiJun 20, 2023Copper Contributor
Primary actions are also not working in a Teams Channel.
Consider the following card;
{ "body": [ { "type": "Input.ChoiceSet", "label": "Pick One ", "choices": "${mylist}", "isRequired": true, "errorMessage": "Please select a an item", "id": "itemId" } { "type": "ActionSet", "actions": [ { "type": "Action.Execute", "verb": "confirm-selection", "title": "OK", "style": "positive", "data": { "dummy": "This is required for IOS to work" } } ] } ] }When this card is used in a personal / group conversation, and the user clicks on OK, the following is submitted (correctly)
{ "dummy": "This is required for IOS to work", "itemId" : 3 }When this card is used in a Teams Channel , and the user clicks on OK, the following is submitted (incorrectly)
{ "dummy": "This is required for IOS to work" }Note that itemId is missing in the response.
- Meghana-MSFTJun 29, 2023Former Employee
Dagwai - Apologies for the delay. Can you please check if you are facing this issue with "type": "Action.Submit" as well. We just checked with action.submit and it works well in both personal and channel scope.
- Meghana-MSFTJun 30, 2023Former EmployeeDagwai - We are also able to repro this issue, Action.Execute does not include Input Values when operating within a channel. A bug has been filed for this issue already. Also this is being tracked here - https://learn.microsoft.com/en-us/answers/questions/1295145/why-isnt-action-execute-including-input-values-whe