D365 Data Integration Strategy - Locus IT Services

D365 Data Integration Strategy

Posted by LocusIT.com | , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,  |

D365 Data Integration Strategy

This topic is intended to help architects and developers make sound design decisions when they implement D365 Data Integration scenarios for Microsoft Dynamics 365 for Finance and Operations.

D365 Data Integration (import/export) Strategy

The topic describes integration patterns, integration scenarios, and integration solutions and best practices for Dynamics 365 Finance and Operations. However, it does not include technical details about how to utilize or set up every integration pattern. It also doesn’t include sample integration code.

Synchronous D365 Integration Patterns vs. Asynchronous D365 Integration Patterns

Processing can be either synchronous or asynchronous. Often, the type of processing that you must use determines the integration pattern that you pick.

A synchronous pattern is a blocking request and response pattern, where the caller is blocked until the caller has finished and gives a response. A asynchronous pattern is a non-blocking pattern, where the caller submits the request and then continues without waiting for response.

Before you compare synchronous and asynchronous patterns, you should be aware that all the REST and SOAP integration APIs that Finance and Operations provides can be invoked either synchronously or asynchronously.

Both Dynamics 365 OData and custom services are synchronous D365 integration patterns, because when these APIs are called, business logic is immediately run in Microsoft Dynamics 365 Finance and Operations. Here are some examples:

  • If Dynamics 365 OData is used to insert product records, the records are immediately inserted as part of the Dynamics 365 OData call.
  • If custom service is used to look up on-hand inventory, business logic is immediately run as part of the JSON/SOAP call, and an inventory sum is immediately returned.

Batch data APIs are considered asynchronous D365 integration patterns, because when these APIs are called, data is imported or exported in batch mode. For example, calls to the Import From Package API can be synchronous. However, the APIs schedules a batch job to import only a specific data package. The scheduling job is immediately returned, and the work done later in batch job. Therefore, batch data APIs are categorized as asynchronous.

Batch data Application program interface (APIs) are designed to handle large volume data imports and exports. It’s difficult to define what exactly qualifies as a large volume. The appropriate response relies upon the entity, and on the amount of business logic that is run during import or export. However, here is a rule of thumb: If the volume is more than a few hundred thousand records, you should use the batch D365 Data Integration for API.

In general, when you’re trying to choose an D365 integration patterns, we recommend that you consider the following questions:

  • Is there any business requirement that the integration should be in real time?
  • What’s the requirement for the peak data volume?
  • What is the frequency?

Typical Scenarios and Patterns that use Dynamics 365 OData Integrations

Here are some typical scenarios that use D365 Data Integration

Create and update product information

A manufacturer runs Microsoft Dynamics 365 Finance and Operations, but defines and configures its product by using a third-party application that is hosted on-premises. This manufacturer needs to move its production information from the on-premises application to Finance and Operations. When a product is defined, or when it’s changed in the on-premises application, the user should see the same change, in real time, in Finance and Operations.

Read the status of customer orders

A company runs Microsoft Dynamics 365 Finance and Operations but has a self-hosted customer portal where customers can check the status of their orders. Order status information has been maintained in Finance and Operations.

Approve Microsoft Dynamics BOM

A organization runs Finance and Operations but uses a Product Lifecycle Management (PLM) system that is hosted on-premises. The Product Lifecycle Management system has a workflow that sends the finished BOMs information to Finance and Operations for approval.

Locus IT has provided customized solutions for data integration strategies with Microsoft Dynamics 365. Our services and solutions help our clients accomplish specific goals and address unique operational challenges in the industry. For more information please contact us.

Locus IT Project Management Office
What’s it?