The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Let us continue with our previous posts on using Microsoft Bot Framework
In our previous post we had configured, tested and trained our LUIS application.
Here we will update our bot application code and see how it works.
Add a new Dialog class named LUIS Dialog
The class implements LuisDialog interface and has attribute Serializable to it.
We also need to add an attribute LuisModel that takes in model id and subscription key.
To get the model id and subscription key, open the LUIS application we had created. (https://www.luis.ai/)
Get App Id from the Dashboard.
And API key from My Keys section.
Now one by one we will implement logic for each of our Intent, for this we will use LuisIntent Attribute.
Here we have wrote a method for each of the intent that we had configured earlier.
We would need to make following changes to our ModelController.cs to call the LUISDialog
Let us look at the Intent one by one
For Luis Intent – None :-
i.e. when no Intent found or Intent is None.
Here bot will reply with Sorry I do not understand if the intent is none.
Here the work meeska (utterance) is associated to None Intent.
Inside Bot emulator –
For Luis Intent – Greeting :-
If the user types in Hi or Hello the bot will respond with “Please let me know…” as it will figure out that the intent is Greeting.
For Luis Intent – QueryProduct:-
If the user types in “Do you have product1?” the Bot associates it to our Query Product intent as we had trained our LUIS app for this. Here if user asks for Product1, Product2 or Product3 the bot responds that it has those products else it responds with “Sorry we do not have that product”.
QueryProduct Intent associated to Product Entity –
Inside Bot Emulator –
For Luis Intent – Interest:-
For Intent Interest, we call our Form Dialog that we had created in the following post Using FormFlow in Microsoft Bot Framework.
It basically asks user about the product he is interested in, name and description and creates a lead record in CRM.
Interest intent –
The lead record created in CRM.
In the next post, we will see how to publish the application to Azure.
Hope it helps..
Business Applications communities