Publishing Enterprise People bot to PVA fails

[thomas-chung]

Describe the bug

Publishing profile allows us to create profiles for publishing to Power Virtual Agent. Normally when testing our enterprise skills we default choose Publish to Azure and that flow works. However, if we choose to publish PVA the flow fails in the deploy stage with following errors:

{
  "code": "LanguageGenerationWithoutDialog",
  "range": null,
  "severity": "Error",
  "source": "language-generation/en-us/actions.en-us.lg",
  "message": "Language generation file 'actions.en-us.lg' cannot be imported because it doesn't correspond to any dialog. Only files attached to a dialog can be imported. Delete this file and try again."
}
{
  "code": "LanguageGenerationWithoutDialog",
  "range": null,
  "severity": "Error",
  "source": "language-generation/en-us/cards.en-us.lg",
  "message": "Language generation file 'cards.en-us.lg' cannot be imported because it doesn't correspond to any dialog. Only files attached to a dialog can be imported. Delete this file and try again."
}
{
  "code": "LanguageGenerationWithoutDialog",
  "range": null,
  "severity": "Error",
  "source": "language-generation/en-us/icons.en-us.lg",
  "message": "Language generation file 'icons.en-us.lg' cannot be imported because it doesn't correspond to any dialog. Only files attached to a dialog can be imported. Delete this file and try again."
}
{
  "code": "LanguageGenerationWithoutDialog",
  "range": null,
  "severity": "Error",
  "source": "language-generation/en-us/profile.en-us.lg",
  "message": "Language generation file 'profile.en-us.lg' cannot be imported because it doesn't correspond to any dialog. Only files attached to a dialog can be imported. Delete this file and try again."
}
{
  "code": "LanguageGenerationWithoutDialog",
  "range": null,
  "severity": "Error",
  "source": "language-generation/en-us/userList.en-us.lg",
  "message": "Language generation file 'userList.en-us.lg' cannot be imported because it doesn't correspond to any dialog. Only files attached to a dialog can be imported. Delete this file and try again."
}

There are a couple of sub-issues we think:

1. The PVA publishing scenario was not part of our planned scenario for Enterprise Assistant/People/Calendar, therefore was not tested and is not expected to work (it indeed doesn't work).
2. The publishing profile can give inexperienced dev a false sense of security that their bot can publish to either because the flow doesn't really say what works/don't work across both. However, in reality something that works for Azure bots (see above messages) wouldn't work for PVA publishing. This should surface better in our tool sets (perhaps as an normal error in Composer).

Version

Version: 2.0.0-nightly.240366.4a6ec2c
Electron: 8.2.4
Chrome: 80.0.3987.165
NodeJS: 12.13.0
V8: 8.0.426.27-electron.0

Browser

• Electron distribution
• Chrome
• Safari
• Firefox
• Edge

OS

• macOS
• Windows
• Ubuntu

To Reproduce

Steps to reproduce the behavior:

1. Create an Enterprise People bot from template
2. Create a new publishing profile for PVA
3. Attempt to publish bot to PVA

Expected behavior

Either it succeeds, or warns the user well before the publishing stage their bot would fail to publish to PVA, or remove the ability to publish the bot to PVA for certain template (from most ideal to least ideal expected behavior)

Screenshots

Additional context