You’re offline. This is a read only version of the page.
11
Hello, all,
We're looking to deploy a chat bot in O365 SharePoint and have followed these steps:
The chatbot webpart has been deployed to our App Catalog:
The App has been added to the site in which we would like to deploy it to:
After adding the webpart to the SharePoint page and then clicking "Edit web part", we input the following details into the "Chatbot Webpart"
Bot ID: fdc7b2764859499b948a996ec542b683
BOT Name: Unable to connect, my dude
BOT logo: {blank}
When I try to use the chat bot through SharePoint, I get the following error:
What's really strange is when I try and connect to another user's Bot ID (taken from another thread here), I get the following message:
(^Bot ID 7f109be3-f5ea-4c49-bc96-f6aa4b15a81d)
This functionality was initially working when we incorporated it into SharePoint and tried it a few months ago. Each bot is also currently working when testing them in the "Demo site". Currently, the SharePoint functionality won't work with any bots created in Teams nor any created through the PVA portal. We have tried removing and re-adding the SharePoint package, and re-adding the App. We've tried creating new bots, and nothing has worked for the past 4 weeks. We're completely at a loss for what is causing this. Any ideas?
This has been solved with the help of Microsoft. The fix was to update the Bot ID to add the dashes that were present in the other user's bot (Bot ID 7f109be3-f5ea-4c49-bc96-f6aa4b15a81d) to my bot:
Bot ID: fdc7b2764859499b948a996ec542b683 (original)
versus
Bot ID: fdc7b276-4859-499b-948a-996ec542b683 (updated)
After this change, the bot worked. Which means that if anyone would like to use this same solution, they will need to add the dashes to the Bot Schema in the same locations as above.
#1
Romain The Low-Code...
25
#1
Pablo Roldan
25
#3
stampcoin
10
Share
Report
All responses (
Answers (
