Selecting a choice in Dynamic Typeahead Search still shows errorMessage string meant for when no choice is selected.

[SandeepGamot]

Repro Steps:

1. Implement a simple dynamic typeahead search card following the below shape

{
  "type": "Input.ChoiceSet",
  "isRequired": true,
  "errorMessage": "Select atleast one user",
  "id": "users",
  "choices": "${users}",
  "isMultiSelect": true,
  "placeholder": "Select user(s)",
  "value": "${defaultUsers}",
  "style": "filtered",
  "choices.data": {
    "type": "Data.Query",
    "dataset": "users"
  }
}

2. Start the bot in MS-Teams Web app using Chrome (any browser should do) and navigate to the dynamic typeahead search component
3. Select any choice and click on submit
4. See the bug where the string specified in errorMessage field show up. In this case "Select atleast one user".

Expected Behaviour

There shouldn't be an error when at least one choice is made and the submit button is clicked. Only when no choice is made and submit button is clicked we show the error.

According to related closed issue #868 it was resolved but currently it's happening in MS-teams Web for nodejs based projects.

[microsoft-github-policy-service]

Hi @SandeepGamot! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies.

Best regards, Teams Platform

[Meghana-MSFT]

@SandeepGamot - Thank you for reporting this, we will check this and get back to you. It looks like your issue is similar to MicrosoftDocs/msteams-docs#10533. Could you please confirm?

[SandeepGamot]

@Meghana-MSFT the underlying bug is same in the issue you mentioned. Only difference is in the framework used, they're using C# and we're using Node.

[Meghana-MSFT]

Thank you for your confirmation. We will keep you posted on the bug fix updates.

[SandeepGamot]

Thanks for the update @Meghana-MSFT
Any rough ETA on this?

[Meghana-MSFT]

Unfortunately, we do not have any ETA to share. We are following up for updates and we will keep you posted.

[SandeepGamot]

Hi @Meghana-MSFT any updates?

[Meghana-MSFT]

Unfortunately, we do not have any updates to share. We will keep you posted.

[SandeepGamot]

Hey @Meghana-MSFT any new updates?

[Meghana-MSFT]

@SandeepGamot - We are checking this internally with the engineering team. We will keep you posted once the fix has reached public rings.

[SandeepGamot]

Hi @Meghana-MSFT sorry to bother again. Any new updates?

[Meghana-MSFT]

@SandeepGamot - Apologies for the inconvenience caused to you. The fix has not reached public rings yet. We will keep you posted.