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

Unable to publish my Bot to PVA #4813

Closed
2 of 8 tasks
arafattehsin opened this issue Nov 14, 2020 · 3 comments
Closed
2 of 8 tasks

Unable to publish my Bot to PVA #4813

arafattehsin opened this issue Nov 14, 2020 · 3 comments
Assignees
Labels
Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-reported Required for internal Azure reporting. Do not delete. Type: Bug Something isn't working

Comments

@arafattehsin
Copy link
Contributor

Describe the bug

After creating a profile, I couldn't publish my Bot to Power Virtual Agents.

Version

1.2.0

Browser

  • Electron distribution
  • Chrome
  • Safari
  • Firefox
  • Edge

OS

  • macOS
  • Windows
  • Ubuntu

To Reproduce

Steps to reproduce the behavior:

  1. Go to Publish
  2. Select Publish Profile
  3. Publish to Selected Profile
  4. It keeps on progressing... with no luck!

Expected behavior

The bot should have published.

Screenshots

image

Additional context

@arafattehsin arafattehsin added Needs-triage A new issue that require triage Type: Bug Something isn't working labels Nov 14, 2020
@jwiley84 jwiley84 added Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-reported Required for internal Azure reporting. Do not delete. labels Nov 16, 2020
@arafattehsin
Copy link
Contributor Author

Further more, I created a new PVA Bot and try to integrate with that. It showed me the data but failed with the below screenshots;

image

Logs;


{
"code": "FileIsIgnored",
"range": null,
"severity": "Warning",
"source": "settings/cross-train.config.json",
"message": "File 'cross-train.config.json' is unknown for the system and was ignored during the import."
}


{
"code": "FileIsIgnored",
"range": null,
"severity": "Warning",
"source": "generated/interruption/AMATransferBot.en-us.qna",
"message": "File 'AMATransferBot.en-us.qna' is unknown for the system and was ignored during the import."
}


{
"code": "FileIsIgnored",
"range": null,
"severity": "Warning",
"source": "dialogs/CheckBalanceDialog/knowledge-base/en-us/CheckBalanceDialog.en-us.qna",
"message": "File 'CheckBalanceDialog.en-us.qna' is unknown for the system and was ignored during the import."
}


{
"code": "FileIsIgnored",
"range": null,
"severity": "Warning",
"source": "generated/interruption/CheckBalanceDialog.en-us.qna",
"message": "File 'CheckBalanceDialog.en-us.qna' is unknown for the system and was ignored during the import."
}


{
"code": "FileIsIgnored",
"range": null,
"severity": "Warning",
"source": "generated/luis.settings.composer.westus.json",
"message": "File 'luis.settings.composer.westus.json' is unknown for the system and was ignored during the import."
}


{
"code": "DialogDoesNotMatchAppSchema",
"range": null,
"severity": "Error",
"source": "AMATransferBot.dialog",
"message": "Dialog 'AMATransferBot.dialog' does not match the app.schema. Details: 'JSON is valid against no schemas from 'oneOf'. Path 'recognizer', line 71, position 39. Inner errors:\r\n Invalid type. Expected Object but got String. Path 'recognizer', line 71, position 39.'"
}


{
"code": "RecognizerTypeIsNotSupported",
"range": null,
"severity": "Error",
"source": "dialogs/CheckBalanceDialog/CheckBalanceDialog.dialog",
"message": "The recognizer type 'Microsoft.CrossTrainedRecognizerSet' is not supported."
}


{
"code": "DialogDoesNotMatchAppSchema",
"range": null,
"severity": "Error",
"source": "dialogs/CheckBalanceDialog/recognizers/CheckBalanceDialog.lu.qna.dialog",
"message": "Dialog 'dialogs/CheckBalanceDialog/recognizers/CheckBalanceDialog.lu.qna.dialog' does not match the app.schema. Details: '$kind should be Microsoft.AdaptiveDialog'"
}

@cwhitten
Copy link
Member

@arafattehsin the default schema used in Composer is not entirely compatible with Power Virtual Agents. They have their own schema that they provide and validate against when you publish. See the following blogpost for explanation and tutorials on how to publish. https://powervirtualagents.microsoft.com/en-us/blog/power-virtual-agents-integration-with-bot-framework-composer-is-available-in-public-preview/

@arafattehsin
Copy link
Contributor Author

Hi @cwhitten - I would delightfully close this issue as I have got the way to make it working. Blog post coming 🔜

image

@a-b-r-o-w-n a-b-r-o-w-n removed the Needs-triage A new issue that require triage label Nov 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-reported Required for internal Azure reporting. Do not delete. Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants