About the Microsoft Dynamics 365F&O category

[anon99371720]

Put topics about this connector package here.
Always check the ‘How to use the Alumio connector packages’ topic.

Extra information

System documentation: Microsoft Dynamics 365 F&O API Reference

Connector package documentation

Table of Contents

• 1. Setting up HTTP Client Microsoft Dynamics 365 F&O
  • 1.1 Steps
• 2. Subscribing to entities from Microsoft Dynamics 365 F&O
  • 2.1 Steps
  • 2.2 General concept
• 3. Publishing entity to Microsoft Dynamics 365 F&O
  • 3.1 Steps
  • 3.2 General concept

1. Setting up HTTP Client Microsoft Dynamics 365 F&O

1.1 Steps

1. Please refer to this page to register Microsoft Dynamics 365 Finance & Operations to Azure Active Directory. Follow the guide and save the tenant ID, client ID, and client secret of the app registration.
2. In the Alumio Dashboard, go to Clients → HTTP Clients. Create a new HTTP Client.
3. Select Microsoft Dynamics 365 F&O HTTP Client as PlatForm and click the next step
4. Fill in the Base URI, Tenant ID, Client ID, and Client Secret of your Microsoft Dynamics 365 F&O instance and app credentials.
5. You can optionally set a base HTTP client to use for the connection by selecting an HTTP client configuration or setting your own HTTP client in the Advanced HTTP client field
6. Click the Grant access to Microsoft Dynamics 365 F&O button to get the access token.
7. You can optionally change how Alumio logs every HTTP request made by the HTTP client
8. Click the next step, fill in the name of the HTTP Client, and finally, you can save the HTTP Client for use.
   
   

2. Subscribing to Entities from Microsoft Dynamics 365 F&O

2.1 Steps

1. Go to Connections → Incoming, create a new incoming configuration, and select Microsoft Dynamics 365 F&O Subscriber as the subscriber.
2. Select the entity you want to subscribe from Microsoft Dynamics 365 F&O.
3. Add any request parameters needed to subscribe to the entity (optional).
4. Select the Microsoft Dynamics 365 F&O HTTP Client to use
5. You can optionally add a transformer to transform the request parameters into something you will request from Microsoft Dynamics 365 F&O.
6. You can also optionally enable pagination to allow Alumio to fetch paginated entities.
   
   

2.2 General Concept

We follow OData Microsoft Dynamics 365 F&O API documentation on building this connector so you can easily use the connector based on Microsoft Dynamics 365 F&O API Reference.

Entity

It’s the entity you want to do (fetching data from Microsoft Dynamics 365 F&O). Please refer to the Microsoft Dynamics 365 F&O API Reference page.

OData Request Parameters

It’s the parameters you can provide to get the needed entity based on Microsoft Dynamics 365 F&O API Reference Documentation. For example, if we want to subscribe to Product Ratings with endpoint /data/ProductRatings with data using ID = 123 and Name = ‘Lorem’, we simply add this Json at the Request parameter area.

It will transform to /data/ProductRatings(ID=123,Name=’Lorem’)
That’s why we need to define the ProductRatings property inside the payload property in the Request Parameters field.

Alumio will then make a request to Microsoft Dynamics 365 F&O.

Input Transformer

Any transformers set here will be executed after the Request Parameters are loaded. So, you can add any transformer to provide and transform the request parameters into anything you need, either as path parameters and/or as query parameters of an entity.

HTTP Client

The HTTP Client configuration you will use to access Microsoft Dynamics 365 F&O.

3. Publishing Entity to Microsoft Dynamics 365 F&O

3.1 Steps

1. Go to Connections → Outgoing, create a new outgoing configuration, and select “Microsoft Dynamics 365 F&O Publisher” as the publisher.
2. Select the Method you want the publisher to use with the data.
3. Select the Microsoft Dynamics 365 F&O entity to which the data will be published.
4. You can optionally add any query data to the request on the key query.
5. You can optionally add any payload data to the request on the key payload.
6. Select the HTTP Client to use.
   
   

3.2 General Concept

Like the subscriber, the publisher has similar methods on how to use it. The difference is the payload that will be submitted by the publisher originating from the data (from routes, from transformers in outgoing configuration). However, you can also add or modify the payload using the Request Transformer.

Method

Currently, we support POST and PUT methods.

Entity

We support publishing to most Microsoft Dynamics 365 F&O endpoints but not with publishing binary files at the moment. Please refer to the entities from the Microsoft Dynamics 365 F&O API Reference page. Based on the documentation, some endpoints may need one or more path parameters.

Action

We support publishing to most Microsoft Dynamics 365 F&O endpoints. Please refer to Microsoft Dynamics 365 F&O API Reference Documentation page.
Please look at the example below.
For example, we want to update a sales order line. Please select the PATCH method, then the sales order line as the entity action of the publisher.
The documentation describes that we need SalesOrderLine property as a request body. In that case, you must provide the SalesOrderLine property into the payload property in the data, either as an output from Routes or from Transformers in the Outgoing Configuration. Here is an example of the required data.

HTTP Client

It’s the HTTP Client configuration or prototype that you will use to access Microsoft Dynamics 365 F&O.