Exporting schema to alexa with slots

[piotr-dziubek]

Exporting schema to alexa dosent provide extra slots

To Reproduce
Create connection with alexa and then Import Intent slot matching example to your questions - and try to copy the schema from alexa.

{
  "interactionModel": {
    "languageModel": {
      "invocationName": "q and a",
      "types": [
        {
          "name": "EXAMPLE_QUESTIONS",
          "values": [
            {
              "name": {
                "value": "book a car"
              }
            },
            {
              "name": {
                "value": "reserver a car"
              }
            },
            {
              "name": {
                "value": "make a car reservation"
              }
            },
            {
              "name": {
                "value": "book a car for {PickUpDate}"
              }
            },
            {
              "name": {
                "value": "dummy utterance"
              }
            }
          ]
        }
      ],
      "intents": [
        {
          "slots": [
            {
              "name": "QnA_slot",
              "type": "EXAMPLE_QUESTIONS"
            }
          ],
          "name": "Qna_intent",
          "samples": [
            "{QnA_slot}"
          ]
        },
        {
          "name": "AMAZON.StopIntent"
        },
        {
          "name": "AMAZON.RepeatIntent"
        },
        {
          "name": "AMAZON.FallbackIntent"
        },
        {
          "name": "AMAZON.CancelIntent"
        }
      ]
    }
  }
}

and now when We try to ask alexa about that - it causes an error - it finds the question but it dont know what to do next

Expected behavior
Alexa should go with follow-up question - same as qnabot client

Version
QnaBot 5.2.0

[marcburnie]

Thanks for raising this issue and sorry for the delayed response. I've been able to reproduce this issue on the current release (v5.3.4). I'll let you know once we have a fix.

[marcburnie]

Currently, the Alexa export feature only exports utterances and not slots; this functionality was never implemented. We are adding this to our backlog for next year.