Automate your sales orders in the European Union with airSlate SignNow

How to create outlook signature

[Music] hello everybody let's get straight to it in this video I will walk you through a functional demo of how to generate a sales order in Dynamics 365 for finance an operation based on the customer email the major steps of this process would include one sending email as the customer be using Microsoft flow and Lewis artificial intelligence to determine the sender of the email and Link it to a customer account in d 365 3 generating a sales order header based on the customer identified in the previous step number four creating cells or lines based on the email body and artificial intelligence findings and five generating confirmation email to be sent to the customer this video was inspired by yon team fouls from Dynamics calm and his great post on creating sales order using Luis we will share a link to that post in the description for this video so what is Luis Luis is used to create logic that stands behind bots that you can build that are available for example for Skype but also we can use Luis with Microsoft flow for that purpose I have created an app called sales order in that app I have two intense one is called none and that's a default intent that is used to specify utterances that would result in no action from from bot I have created an an intent called items to order let's take a look at it in here we have six utterances that I have created to train artificial intelligence on how to recognize where the items are you can see I have five examples of utterances and I marked parts as items if I switch and antilles views and look at talking views you see the original values that I've entered so here I give machine learning examples of how my customers may potentially ask me to order parts behind that there is one entity have created an it is called item and here are all the label utterances that have this entity specified once they app is completed we can train it and then publish it and you can see that app was published on May 15 once we configured our app now we can use it in our Microsoft flow so let's take a look I have created a flow called sales order from email and I'm gonna walk you through the major building blocks of it the first step is define an action that is called one email arrives and you can see here is I say that any email that arrives in my inbox and has a filter on the subject order so the system will only consider emails that have word order in the subject of the email the next step is to convert HTML to text that will make it easier for Lois to interpret it and you can see that I'm using the body of the email as the content the next step is to get predictions that is where I link my app that I have created sales order I also feed the data from the previous tab HTML to text as the utterance text and my desired intent is items to order the next step is to find a customer account the condition that I have to create is I would like to use the email of the sender and try to match it to a primary contact email of my customers in Dynamics 365 and return any customer account that that has a match on email that is a way we will try to identify a customer in d 365 for financing operation based on the sender's email and you can see that I'm using the entity name customers in the next step it is time to create sales order header and sales order lines and for that I'm using applied to each loops for the sales order header creation I will use values from a previous step and the previous step was actually fine because summer account so once I have an email of the sender I will try to match it to a primary contact email of any customer in the 365 if there is a match I will use the information of that customer to create sales order header so let's take a look at create cells or header action as mentioned in the article we have to use the entity called sales order headers and I'm using the sales row headers version 2 we also need to provide basic information to create a sales order header in this case it is the company that is coming from a customer that we identified in the previous tab and the customer account itself that again comes in from the previous tab find customer in Dynamics 365 once we have these two pieces of information company and the customer account we can create a sales or header one sales order header is created it's time to create sales or alliance you can see that I'm using different input for this loop I'm using input not from the previous tab I'm using the input from entity array which was my get predictions from Luis so I'm basically using the information that Luis obtained from the body of email to extract item numbers to create sales order lines let's take a look at the create sales reliance action first piece of information that we will need is a company same as with a sales order header that comes in either from the previous tab of create sales or header or the step before that get customer record the next piece of information that we need is an item itself in here I'm using the entity value I'm basically letting Louis run identify which entities it found and I'm using the values that it was able to identify to populate past item number and the description again through trial and error I found out that the country in and region is also needed to create sales or reliance that is why I'm using the country region of the customer that was identified in the previous step and the last piece of information that I need to create a sales order line is actually less sales order number itself and of course the sales order number comes in from the previous tab of creating sales order header once I have this information accompany and item number sales order number and the country in region I will be able to create sales order lines in dynamic 365 and the last action that I have here is to generate confirmation email back to my customer and here you see that my two email address is actually from email address from the stand before my subject also has a placeholder or dynamic data which includes sales from number that we generated and in the body email I'm also using the customer name again this is a dynamic placeholder a mouse referencing the item numbers and the units of measure that we use that concludes the review of flow setup the next step is to test this flow I will click on test and I will say let's I will perform a trigger action manually myself and I'm gonna click on save and test now the flow is waiting for me to perform an action to initiate the flow and the action as you remember is to send an email to a customer service rep in my subject line I'm mentioning the word order remember only emails that have word order in the subject will be considered and then I'm tapping a typical tags that I was able to train Louis on and I'm saying hi there I would like to order items 100 and 200 once the email is sent I will be waiting for the flow to start working and start interpreting that email and execute as you can see the flow is being executed right now and we can see that the flow ran successfully let's take a look at few stats here get prediction steps shows us what Luis has found I will scroll down click on show more and under my entities array I see that the system identified a type of entity item and the entity value is 100 so that was our first item and if I scroll down here it found another value for the same entity item in this case it was 200 so the two values were found for the entity item 100 and 200 those are our item numbers now let's take a look at the fine customer step we see that the filter query is actually matching on my personal email and based on that email it found customer us 0:03 in company USMS based on that email because that's the only customer that has a primary email address that I used so we have identified our customer for us 0:03 based on the email and that customer name is here is forest for sailors so once we know who the customer is we can now create a cell sorter header let's take a look at that step and we're using this two basic pieces of information the company you SMF and the customer count you as 0:03 to create our sales your header we can now create sales or lines we have two instances of sales order line creation and the first one we are creating a sales or alignment for item 100 for the sales order number 849 that sales order number was created in the previous step and if I click on next button here I can see that I'm creating a second sales order line for the same customer for the same sales order 4:9 but now it is for the item 200 so two cells or lines were successfully created and if I scroll to the last step of my flow I can see that email was sent to the original sender the subject includes the sales order ID that was generated and in the body of email we are mentioning the customer name cells your number and also the item number and you will see there will be two emails generated because there were two cells row lines created so that's so that's a limitation of the systematic alright so now let's go back to dynamics and you can see that before I had three six unconfirmed sales orders now that number has a jump to 37 and if we go back to the flow just remember we expecting to see a cell's for a number that ends with 849 I'm gonna click on my list of unconfirmed sales orders I will find order 849 and once I click on it I can see there are two cells or reliance for the item 100 and 200 that were created and now if I open my email that I used to send the email to the customer service rep I can see there are two emails that were generated that mentioning my name and the sales or a number that was generated in the system and you can see them right here there are two emails because flow generates one email per sales order line that basically concludes our demonstration of the functionality let me just say a few words about the quantity and limitations that we have I was not able to use entity values to populate quantity field for some reason the system did not allow me to pick any entity values except for the this score which was an integer value that it may have used so that's a limitation that exists right now so it makes the whole solution a bit less practical because the sales or lines are created for the default quantity of one there is no way to populate the quantities that we got to fight in the body of email and populate them the sales or line quantity so that's a current limitation hopefully Microsoft will address it soon or if you know how to do that you can let us know in the comments the in conclusion I think it's a pretty interesting application of artificial intelligence services when it comes to automation of sales or creation it may have some benefits especially if we have improvements in the how Lewis values can be used in the flow to create sales orders in the in Dynamics 365 but there's always room for improvement hope you enjoyed that video until the next time [Music]