Closed SreekanthOAuth closed 3 years ago
@Batta32 Would you please look at this.
Hey @EricDahlvang, I'm no longer part of the Kobuk team. Feel free to contact to @ldardick or @matiasroldan6.
@Batta32 - Any update please.
Hi @SreekanthOAuth. We are working on this issue and we let you know as soon as we have any update. Thanks.
Hi @SreekanthOAuth, we could not replicate the issue using the following versions: 4.11.0 and 4.13.0 Find attached an image with the custom event details (BotMessageSend and BotMessageReceived):
We could not run the sample using version 4.6.2 due to some issues when running locally or deploying the bot to Azure. Having said that:
Any additional information is welcome. Thanks
closing due to no activity
What project is affected?
Microsoft Bot framework - Virtual Assistant
What language is this in?
Typescript
What happens?
Below are the versions of botbuilder, we are not getting the conversationId as part of BotMessageSend event.
And we are using React application to load the Webchat by using the directline token. Below are the versions
BotMessageSend
What are the steps to reproduce this issue?
Create the VA project with Typescript language and update the package.json with the above version and do the npm install.
https://microsoft.github.io/botframework-solutions/virtual-assistant/tutorials/create-assistant/typescript/3-create-project/
What were you expecting to happen?
conversationId should come in BotMessageSend telemetry event
Please let us know if you need any further details on this.
Also, please be noted, this issue is not just with BotMessageSend events, it's happening with BotMessageRecevived and some built-in events.
Thanks, Sreekanth (Ecolab)