About the Microsoft Dynamics 365 Navision and Business Central Category

anon99371720 · September 21, 2022, 10:00am

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

Extra information

System documentation: API(V2.0) for Dynamics 365 Business Central - Business Central | Microsoft Learn

Connector package documentation

1. Setting up HTTP Client D365 Business Central

1.1 Steps

Before we begin please enable the APIs for Dynamics 365 Business Central base on this guide Enabling APIs for Microsoft Dynamics NAV - Business Central | Microsoft Learn.
In Alumio Dashboard, go to Clients > HTTPS Client. Create a new HTTP Client and select D365 Business Central HTTP Client as the HTTP Client.
Fill in the Base URL,Tenant ID, Client ID, Client Secret, and Scopes.
You can optionally enable logging of request to get the log of the authentication.
Press “Grant access to Microsoft D365 Business Central”.
The Key will show up and you can save the HTTP Client for use.

2. Subscribing to Entities from D365 Business Central

2.1 Steps

Go to Connections → Incoming and create a new incoming configuration and select “D365 Business Central” Subscriber as the subscriber.
Select the module you want to subscribe from D365 Business Central.
Fill in the “Company ID” you want to use on the request.
Add any request parameters needed to subscribe to the entity (optional).
You can optionally add a transformer to transform the request parameters into something you need.
Select the D365 Business Central HTTP Client to use
You can add a pagination feature to allow Alumio to fetch a paginated entity.

2.2 General Concept

We follow D365 Business Central documentation on building this connector, so you can easily use the connector based on D365 Business Central API Reference.

Module

It’s the list of end points you can subscribe from D365 Business Central. Please refer the end points from OpenAPI Specification - Business Central | Microsoft Learn.

Company ID

It’s the Company ID in D365 Business Central that you want to request to.

Request Parameters

These are the parameters you can provide to get the needed entity based on D365 Business Central API Reference.
Please look at the example below on how to fill Request Parameters field when subscribing “Details of employee”.

The end point in D365 is using oData input, so for the end point /employees({{employee_id}}) we need to provide the ID inside the odata key as an array.
Alumio will transform it into /employees(555)

Another example is when we want to filter a certain phone number from the end point of “Returns a list of employees”.
We can add the filter at the query like

Odata is the odata data of the url. For example the (id).
Query is defined set of data attached to the end of a url.
Example: www.url.com?type=true&start=0

D365 Business Central will filter with the field phoneNumber equal 4567.

Input Transformer

Any transformer’s set here will be executed before the Request Parameters loaded. So, you basically 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

It’s the HTTP Client configuration or prototype you will use to access Business Central.

3. Publishing entity to D365 Business Central

3.1 Steps

Go to Connections → Outgoing, create a new outgoing configuration and select “D365 Business Central” Publisher as the publisher.
Select the action that you want the publisher to do with the data.
Select the “D365 Business Central” entity you want the data to be published to.
You can optionally add any query parameters to the request.
You can also optionally add any transformers to transform the data into anything you need before submitting it to D365 Business Central.
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), though you can also add or modify payload using the Request Transformer.

Action

Currently we support Create (HTTP POST method), Update (HTTP PUT method), and Delete (HTTP DELETE method).

Entity

We support publishing to most D365 Business Central endpoints. Please refer to the entities in Management APIs from D365 Business Central API Reference page. Based on the documentation, some endpoints may need one or more odata parameters.

For endpoints that require object as the request payload, please look at the example below. For example, we want to use “Create customerReturnReasons”.
You will need to make sure there is a payload key inside the data like

Another example, when we need to use “Update vendorPaymentJournals”.
We need to add the ID inside the key odata as an array and make the update data inside the payload key like

Odata is the odata data of the url. For example the (id).
Query is defined set of data attached to the end of a url.
Example: www.url.com?type=true&start=0
Payload is the data contained within a request.

Company ID

It’s the Company ID in D365 Business Central that you want to process.