[bot-type-ahead-search-adaptive-cards][csharp] selecting item from dynamic choice set shows error

[kuojianlu]

Bug description:
For sample https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/bot-type-ahead-search-adaptive-cards/csharp.
After selecting an item from the dynamic choice set, Adaptive Card shows below error, and the "Submit" button does not work.

Reproducing steps:

1. Send "dynamicsearch" command to bot.
2. Search a query like "Microsoft" in the Adaptive Card input box.
3. Select an item from the search result list.
4. Click "Submit" button. There is no response for the clicking operation.
5. If adding "errorMessage" setting to DynamicSearchCard.json like below, then after selecting an item, the error message will show in the Adaptive Card.

          "items": [
            {
              "choices": [
                {
                  "title": "Static Option 1",
                  "value": "static_option_1"
                },
                {
                  "title": "Static Option 2",
                  "value": "static_option_2"
                },
                {
                  "title": "Static Option 3",
                  "value": "static_option_3"
                }
              ],
              "isMultiSelect": false,
              "style": "filtered",
              "choices.data": {
                "type": "Data.Query",
                "dataset": "npmpackages"
              },
              "id": "choiceSelect",
              "type": "Input.ChoiceSet",
              "errorMessage": "There was an error", // ADD THIS SETTING
            }
          ],

[Meghana-MSFT]

Thank you for reporting this, we will check this and get back to you.

[Meghana-MSFT]

@kuojianlu - We ran the https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/bot-type-ahead-search-adaptive-cards/csharp sample and it is working fine at our end.

We checked in Teams web app in Windows. Could you please let us know the OS or app version details which could help us in having a repro.

[kuojianlu]

@Meghana-MSFT Thank you for replying. I also use Teams web app in Windows.

OS: Windows_NT x64 10.0.23486
Teams version: Developer preview

I just tried the demo-manifest (https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/bot-type-ahead-search-adaptive-cards/csharp/demo-manifest) as well, it also did not work on my side. The "Submit" button did not work.

[Meghana-MSFT]

@kuojianlu - Could you please share test account credentials where this issue is reproducible? Please share the credentials at microsoftteamsdev@microsoft.com.

[Meghana-MSFT]

@kuojianlu - We raised bug for this issue, we will keep you posted on the updates.

[CodeABao]

any updates?

[01]

@Meghana-MSFT @ChetanSharma-msft Any updates we are facing exact issue suddenly on latest teams update. Microsoft Teams Version 1.6.00.20074 (64-bit), but seems to also be occuring on web version. and is critically affecting functionality for enterprise bot servicing IT Support needs of employees

[AleVitali]

Maybe this can help to find the issue: if I insert into the choice field an array with the possible values with an explicit "type": "Insert.Choice" works.

I tried to return that field from my backend, but it's filtered.

[Meghana-MSFT]

Unfortunately, we do not have an ETA to share. Team is working on the bug; we will keep you posted on the updates. Thank you.

[ChetanSharma-msft]

Hello Everyone,
This issue is fixed now.
Could you please verify once and let us know the updates?

[dylanw-oss]

Hello Everyone, This issue is fixed now. Could you please verify once and let us know the updates?

The fix does not work, I can still repo the issue in JS sample, using Teams web.

[AleVitali]

We had to drop the feature as, when we tried to select an option, the validation failed complaining about a missing value

[SandeepGamot]

Hi @Meghana-MSFT, @ChetanSharma-msft this problem has occurred back.
We had a POC done based on Dynamic Typeahead search a few weeks back, which was working fine.
But when we're currently trying to implement it as a feature across our Ms-Teams bot this particular error is occurring.
We've tried this on Teams web.

Any recent changes? Let me know if I need to create a new issue for this as this one is already closed.

[Meghana-MSFT]

Since another issue has been raised for this, we will track the issue in above mentioned thread. ##1213