microsoft / microsoft/AdaptiveCards
[Function not implemented] choices.data Data.Query This function cannot be used on the teams mobile platform
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2k
- Forks
- 595
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 1
Description
Target Platforms
UWP
SDK Version
1.5
Application Name
teams (ios &android) Android version :1416/1.0.0.2025132902/0715
Problem Description
I created an adaptive card that includes the Data.Query function.
After deploying the bot, it works fine on both the web and desktop versions.
But this function cannot be implemented in the latest versions of Teams for iOS and Android.
I repeated the operation many times and it was always the same. At least it was normal on the desktop. But because there are too many options, it is difficult to use on the phone without being able to search.
Show as below
Screenshots
Teams for iOS and Android.
Teams PC and web (Successed)
Card JSON
{
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"type": "AdaptiveCard",
"version": "1.5",
"body": [
{
"type": "TextBlock",
"text": "Select assistant",
"weight": "Bolder",
"size": "Medium"
},
{
"type": "Input.ChoiceSet",
"id": "assistantChoice",
"placeholder": "Type to search for an assistant",
"isRequired": true,
"errorMessage": "Please select an assistant",
"choices": [],
"style": "filtered",
"choices.data": {
"type": "Data.Query",
"dataset": "assistants"
}
}
],
"actions": [
{
"type": "Action.Submit",
"title": "Submit"
}
]
}
Sample Code Language
nodejs
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
No repository file, test, or entry point is identified. Start by reproducing the supplied Adaptive Card JSON with Data.Query on Teams for iOS and Android, then compare it with the reported successful web and desktop behavior; done means the choice search works on both mobile platforms or the limitation is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100