Skip to main content

Azure Logic with AX–callable endpoint

There are lots of ways to work with Azure Logic. This will be my first of many hopefully to show you how you can use Azure Logic with AX.

Have a read of this post from the Azure Logic team first. It explains how you can create a callable endpoint in Azure Logic.

Logic apps as callable endpoints

In my post I will show you how you can use AX to call an Azure Logic endpoint.

SNAGHTML2b98aec (I am not a graphics guy but the little fire on the end of the rocket is my addition)

First start by writing a job that sends a post message to request bin. Request bin is a good site which you can use to send a message to it and it displays the results in a readable way.

Navigate to request bin and copy the URL into the job. Then run the job to see the result.

static void _jsonJob(Args _args)
{
    RetailWebRequest    request;
    RetailWebResponse   response;
    str                 rawResponse;
    Map                 data;
    RetailCommonWebAPI  webApi = RetailCommonWebAPI::construct();

    str _requestUrl = @'http://requestb.in/1a07xyj1';
    //str _requestUrl = @'https://prod-02.northcentralus.logic.azure.com:443/workflows/bb7f4b0c834f418cbf7d2fa969c4bcea/triggers/manual/run?api-version=2016-06-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=AAAAAAAAAAAAAAAAAAAAA;
    str _postData =
    @'
    {
            "email": "munib@fakeemail.com",
            "name": "Munib A Ahmed"
    }
    ';
    str _header = '';
    str _contentType = 'application/json';

    response = webApi.makePostRequest(_requestUrl, _postData, _header, _contentType);

    rawResponse = response.parmData();
    data = RetailCommonWebAPI::getMapFromJsonString(rawResponse);
    info(rawResponse);
}

Below is what you should see in request bin.

image

Now, lets do it via Azure Logic.

1) In Azure Logic create a new app

image

 

 

3) Create a HTTP request. This will give you a URL which you can call.

image

Use http://jsonschema.net/ to copy your message and get a schema. This schema can be pasted into the HTTP request.

image

I create an action to send an custom response. I added parts of my request and some additional elements.

Run the job in AX and have a look at the response.

image

This is just a quick test but think of similar examples. You can possibly create a framework in AX where you send a message after an invoice is posted. That message could be json, string, xml or filestream. Then you can have Azure Logic send an SMS, email, integrate with SalesForce/CRM or all other connectors.

Labels:

Popular posts from this blog

Approve Workflow via email using template placeholders #Dyn365FO

Dynamics 365 for Finance and Operations has placeholders which can be inserted into the instructions. Normally you would want this to show up in the email that is sent. One of the most useful ones is the URL link to the exact record that you are approving. In the workflow configurations use the placeholder and build up your message. Towards the end it has workflow specific ones. The URL token is %Workflow.Link to web% . For the technical people the token is replaced in this class WorkflowDocumentField. This is what I inserted into my email template. <BODY> subject: %subject% <BR> message: %message% <BR> company: %company% <BR> for: %for% <BR> </BODY> Should look like this. The final result looks like this. If you debug these are the place holders that are put together.
Read more

Purchase requisition – Price

The price fields on the purchase requisition are non-editable for catalogue items. It is expected that a trade agreement be created. The price fields are only editable for these conditions: Form is opened view AP -> Periodic -> Purchase Requisition -> All purchase requisition, or Line type is “Non-catalogue item”, or User is task owner. Ie. The task is assigned to the user. In other words he/she maybe the purchaser that gets the price. User is approval owner. Ie. The approval is assigned to the user. In other words he/she maybe the manager that approves the final requisition. For catalogue items on the purchase requisition line can only select between the vendor directly associated with the item and the cheapest vendor as found through the purchase price trade agreements. If another vendor is requested the vendor can be blanked and the user can enter a “Proposed vendor” in the proposed vendor field on the general tab page for the purchase requisition line.   NOTE: ...
Read more

Dynamics 365 Invoice Capture Feature

Microsoft recently released the new Invoice Capture for Dynamics 365 Finance. I ran through installing and configuring it.  From that experience, below is my brain dump and hopefully it can help with things that are not so obvious. Three type of invoice captures There are three invoice type paths that can be captured. These drive the screen layout and what kind of information is mandatory. PO invoice Header-only Cost invoice When an invoice comes in, you can select one of the three invoice types. Below are the three screen layouts and differences. PO invoice – Invoices of this type are associated with purchase orders. The purchase order details must be determined on each invoice line. Both the header and the lines must be reviewed in Invoice capture. This will create a pending vendor invoice. Header-only – Invoices of this type are associated with purchase orders. The purchase order field on the invoice header is a mandatory field. If the Automatically create invoice lines featur...
Read more