Call a logic app from a business event

Business events in D365 is a nice feature that one can latch on to and use in integrations. In this post we will explore how to call a logic app from a business event that has been triggered.


Pre-requisites:

- Azure subscription with credit
- D365FO with privileges to manage business events
- Office 365 subscription or email via Outlook.com

Business event setup, part 1, schema

In D365FO you have several standard out of the box business events called Business events catalog, located at System administration --> Setup --> Business events. 

  1. Locate and highlight the Business event ID, PurchaseOrderConfirmedBusiness. Press the link Download schema to download the schema file (indicated with a green circle in picture below).


  2. Open the downloaded file in notepad and keep it open to use it later


Logic app

Go to azure portal, make sure you have credit and able to create a new Logic App. I like using the Azure portal App for simple examples like this. We are to create the simplest logic app possible for our example.

  1. Create a new blank Logic app
  2. Add a new step


  3. Expand the step and copy in the entire content of your schema file into the text area Request Body JSON Schema, and save the logic app.


  4. Add another step, search up Office 365 Outlook and scroll down to Send an email (v2). You can also use Outlook.com if you do not have a Office 365 subscription. 


  5. Now you need to expand the new step and sign in with your office365 account to provide access to your email.
  6. After signed in fill in the mandatory fields, to, subject and body. In the body I have also added some parameters from the JSON schema which will fetch data provided from the business event. For testing reasons make sure your own email address is in the To field.


  7. Save the logic app
  8. Copy the URL from the first step



Business event setup, part 2, activate business event

Now we need to create an endpoint and activate the business event.

  1. Open the Business events catalog, located at System administration --> Setup --> Business events.
  2. Go to the Endpoints pane
  3. Create new Endpoint
  4. Choose type Microsoft Power Automate
  5. Give it a name and paste in your URL from step 8 (your logic app URL address) in previous section, then press OK.

  6. Now we need to activate the business event, select your business event named PurchaseOrderConfirmedBusinessEvent and press +Activate.


  7. Now a new dialog appears, choose your legal entity and the endpoint you've just created.
  8. Press OK to finish this step

You now have a basic logic app and a business event activated. To test your business event and logic app. Go and confirm a purchase order, you can monitor the run history in the logic app and see the resulting email in your email inbox. Under is an example email received from my environment.




Location: Bergen, Norway

Comments

Post a Comment

Popular posts from this blog

Call a simple Logic app from X++

Image
Logic apps can be called manually from D365FO with code I've made a basic Logic App that receive a short JSON. 1. Get JSON schema Get your JSON sample and go here and paste it in  https://www.liquid-technologies.com/online-json-to-schema-converter . Press Generate Schema and you have your schema in the box below. Example JSON : {   "sku": "875828",   "externalMaterialReference": "400267" } Example JSON Schema { "$schema" : "http://json-schema.org/draft-04/schema#" , "type" : "object" , "properties" : { "sku" : { "type" : "string" }, "externalMaterialReference" : { "type" : "string" } }, "required" : [ "sku" , "externalMaterialReference" ] } 2. Create Logic App In the Azure Portal or in your Visual Studio, cre
Read more

SysOperationFramework with use of Query

Image
 The SysOperation framework is very good and effective, but unforutnatly a bit complicated to get in to and do as you want.  I had one case in which a simple table should be updated, the job was to be able to set in batch. Also it had to use a query so that the user could easily set up the ranges as he pleased. Note that I will use the same query for updating the table which I mentioned. So the same query is used all the way through ending in using Quer::updateRecordset For this you need: Data contract class Controller class Service class Simple query oject Action Menu item Main menu where to make the menu item available. 1. Data contract class Note the simple query highlighted in bright yellow .  [DataContractAttribute     , SysOperationGroupAttribute('Parameters',  "Parameters", '1')] internal final class CustAutoCancelUpdateDataContract {     str             packedQuery;     MCRAutoCancel   autoCancel;     public Query getQuery()     {         return new Qu
Read more

Retail Attributes on sales lines

Image
Recently I've dived into Retail. There will be some posts about retail and the problems I've faced with solutions. First off will be the Retail Attributes, they can be problematic here is a data base diagram illustrating a simplyfied view, assuming the value is of type text. And here is the select statement for listing all sales lines with their attributes.         SalesTable salesTable;         SalesLine salesLine;         RetailSalesTableInstanceValue instanceValue;         EcoResAttribute attribute;         EcoResAttributeValue attributeValue;         EcoResTextValue      textValue;     while select salesId                  from  salesLine             join SalesId                   from salesTable                 where salesTable.SalesId == salesLine.SalesId             join SalesId, RecID                 from instanceValue                 where    instanceValue.SalesId == salesLine.SalesId                 &&  
Read more