Calling a D365FO Web Service from a Flow

 Here is a guide on how to call a custom Web Service in D365FO from a Flow. To call a Web Service you need to gain access by retrieving an access token and pass that token in the header of your call.

If you do not have a web service or you want to follow this example, you can download this file and import into your development environment, also you can view this post to see how a web service is made.

Create your flow

Begin by creating your Flow by selecting a template, since I make this flow in relation to my PowerApp post, I will choose the Power Apps button template. 



Basic Flow steps

These are the basic steps that you need to call a web service, you can of course do it a whole set of different ways, like use Azure Keyvault or passing parameters instead of hard coding [like I've done here].

Quick explanation:

*Variable, I just hardcoded this, you might choose different approach.

  1. Called by a power app. 

  2. initialize variables:
    1. TenantID*
    2. ClientID*
    3. Web service URL*
    4. ProductID, (input parameter from PowerApp), choose the Ask in PowerApps to create input parameter.


    5. Scope*
    6. Secret*. 

  3. Retrieve access token


  4. Compose the result (fetch the token variable from JSON)


  5. Initialize variable AccessToken, setting the value to the token 
  6. POST run web service. My web service needs JSON, the parameter name is "_data" (underscore included) and the exact parameter  name is needed when passing it in the body.

    PS! a common mistake here is to not include a whitespace in the Authorization parameter value, there must be a whitespace between the text Bearer and the access token variable.

  7. Compose response

  8. Initialize variable Response

  9. Respond to PowerApp, here you add the return parameters you'd like. You can have several, which is a very nice feature.


When finished setting up your flow test it by pressing the test button in the top rightmost corner. You will be presented with input boxes for your input parameters.



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