2

I have created an application for Microsoft Teams with Bot Framework. It's showing to user some Adaptive card with Input.Date and Action.Submit button on it. The problem is, when Teams client app localization is set to different language than english (tested on US and GB - all worked fine) the data on backend service from Input.Date is not present in Action object's Value property. I was using web version of Teams client for testing. I have tried it with polish and german languages. Incomplete Action.Value on polish language

And on english localization it works fine: Complete data on english language

I have tested it also on desktop version of Teams and result was a little bit different - one of the dates did came through, but with day replaced with month (difference in polish and english date format), the other one has selected 28th november, so number 28 couldn't be converted to month number. Result from desktop Teams app

It seems that problem is with the Teams client application itself and it's date input handling. I have found some issue ticket on similiar problem on MS Github: Github issue ticket. Ticket is from april and since then not much have changed.

My question is: Is there some workaround for this problem that allowes using localization other than english and still get valid data from Input.Date or is there work beeing done on this topic?

Improve this question
1
  • Thanks for reaching out!! This is a known issue. We have a bug on this and we are working on it.
    – Gousia Begum
    Commented Nov 22, 2019 at 11:36

1 Answer 1

Reset to default
2

The bug is described in detail here: https://github.com/OfficeDev/BotBuilder-MicrosoftTeams/issues/195

Long story short, Teams submit actions try to interpret each date value from the string representation as though it's in American English, regardless of the locale settings.

Like Gousia said, the problem is being worked on.

Improve this answer
2
  • Thank You for your answer. Guess I'll have to wait for this problem to be fixed. But, like You have mentioned in linked github post, the date input field is essential for many business applications, so I hope this won't last too long.
    – Lucas P.
    Commented Nov 24, 2019 at 20:56
  • I hope it doesn't last too long too. In the meantime, you might consider using Input.Text instead so that you can interpret the date result on the bot side. Please remember to accept this answer if it's acceptable or let me know what else you need otherwise.
    – Kyle Delaney
    Commented Nov 25, 2019 at 18:31

Not the answer you're looking for? Browse other questions tagged or ask your own question.