Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OnChooseIntent: AdaptiveCard template appears broken #6969

Closed
2 of 8 tasks
taicchoumsft opened this issue Apr 14, 2021 · 2 comments
Closed
2 of 8 tasks

OnChooseIntent: AdaptiveCard template appears broken #6969

taicchoumsft opened this issue Apr 14, 2021 · 2 comments
Assignees
Labels
Type: Bug Something isn't working
Milestone

Comments

@taicchoumsft
Copy link
Member

taicchoumsft commented Apr 14, 2021

Describe the bug

  1. Set up a brand new bot with LUIS/QnA, or Orchestrator/QnA, in the root dialog.
  2. Add a OnChooseIntent trigger (aka intent disambiguation trigger)
  3. Try creating a test condition where this trigger will be hit

Instead of seeing the adaptive card with choices, we get an error:

image

Snip of error message, looks like $schema property is missing a value:

"empty_1.en-us.lg:Unexpected character at Path , line 3, position 15 when parsing 
 {
 "$schema",
 "version": "1.0",
 "type": "AdaptiveCard",
 "speak": "",
 "body": [
 {
 "type": "TextBlock",
 "text": "I'm not sure which one you mean.",
 "weight": "Bolder"
 },
 {
 "type": "TextBlock",
 "text": "Can you pick one ?",
 "separator": "true"
 },
 {
 "type": "Input.ChoiceSet",
 "placeholder": "Placeholder text",
 "id": "userChosenIntent",
 "choices": [
 {
 "title": "Test",
 "value": "luisResult"
 },
 {
 "title": "See an answer from the Knowledge Base",
 "value": "qnaResult"
 },
 {
 "title": "None of the above",
 "value": "none"
 }
 ],
 "style": "expanded",
 "value": "luis"
 },
 {
 "type": "ActionSet",
 "actions": [
 {
 "type": "Action.Submit",
 "title": "Submit",
 "data": {
 "intent": "chooseIntentCardResponse"
 }
 }
 ]
 }
 ]
 }

Version

Nightly 235171

Browser

  • Electron distribution
  • Chrome
  • Safari
  • Firefox
  • Edge

OS

  • macOS
  • Windows
  • Ubuntu
@taicchoumsft taicchoumsft added Type: Bug Something isn't working Needs-triage A new issue that require triage labels Apr 14, 2021
@cwhitten
Copy link
Member

@taicchoumsft, you're updating this template as part of the orchestrator disambiguation, right? can you include the fix for this in it?

@taicchoumsft
Copy link
Member Author

OK thanks @cwhitten , I'll take care of this as part of that effort

@taicchoumsft taicchoumsft self-assigned this Apr 15, 2021
@taicchoumsft taicchoumsft added this to the R13 milestone Apr 15, 2021
@taicchoumsft taicchoumsft removed the Needs-triage A new issue that require triage label Apr 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants