Dynamics 365 Finance and SCM Integration Patterns

D365 FO Integration Design and Patterns

Blog about Dynamics 365 Finance and SCM Integration Patterns and learnings using azure integration services.

Dynamics 365 FO: Priority based throttling for integrations

Priority-based throttling introduces service protection settings that prevent the over-utilization of resources to preserve the system’s responsiveness and ensure consistent availability and performance for environments running Finance and Operations apps. What is throttling and why? The problem with the OData and custom webservice is that when you make more calls than the endpoints can process, the system performance will be impacted because of the resources that run the OData/Custom webservice endpoints and the rest of the system are shared. So the number of requests sent by oData and Custom web service to the system will start to affect system reliability,Continue reading “Dynamics 365 FO: Priority based throttling for integrations”

Dynamics 365 UO: Set financial dimension using oData integration

Use case: I had to set financial dimension values for Purchase Order Lines using oData while inserting data into D365 Unified Operations. To set the financial dimensions, we need to set the value for the field “DefaultLedgerDimensionDisplayValue“. When I tried to set the value, I got the following error. Write failed for table row of type ‘PurchPurchaseOrderLineEntity’. Infolog: Error: The number of dimension values specified in XXXX is different from the number set up in the active format for data entities.Things to try: • Make sure the number of dimension values specified matches the active format for data entities. •Continue reading “Dynamics 365 UO: Set financial dimension using oData integration”

D365 Finance and Operations integration using BYOD

This blog explains the integration option to export data entities from Dynamics 365 F&O into a Microsoft Azure SQL database. D365FO provides a feature via Data Management Frame called bring your own database (BYOD). The BYOD feature lets D365 administrators export one or more data entities that are available in D365FO into an Azure SQL database. The BYOD feature lets: Define one or more SQL databases that admin can export D365 FO entity data into. Export either all the records (full push) or only the records that have changed or been deleted (incremental push). Use the rich scheduling capabilities ofContinue reading “D365 Finance and Operations integration using BYOD”

Dynamics 365 UO DMF Data Export using Logic Apps

This Blog describes the method of implementing Dynamics 365 UO’s Data Management Framework Recurring Integration Module using the Logic App. The blog provides a technical implementation of queuing and dequeuing of the Jobs using REST API of Dynamics 365 UO’s Recurring Integration Module. Dynamics 365 for Operation provides two primary sets of APIs, Recurring Integration APIs & Data Management Platform (DMF) package APIs, to support file-based integration scenarios. These APIs allow DMF data files as well as data projects to be imported and exported from Dynamics 365 for Operations.In this use scenario for Dynamics 365UO  recurring integrations, data will beContinue reading “Dynamics 365 UO DMF Data Export using Logic Apps”

Integration Design Patterns for D365 FO

Dynamics 365 for Unified Operations has evolved into purpose-built applications to help you manage business functions. This would mean that there would be integration with diverse systems. The blog describes integration patterns, integration scenarios, and best practices. There is a number of ways users can interact with the D365 UO. There are different ways to populate data to Dynamics 365 UO and retrieve data from D365 UO. In my personal opinion, the integration option can be decided based on the following three criteria Retrieve data from D365 UO or Populate data to D365 UO Real-Time interaction with D365UO or BatchContinue reading “Integration Design Patterns for D365 FO”

Dynamics 365 FO Integration using Business Events

This blog describes a method to use Azure Integration with Dynamics 365 FO Business Events. The Dynamics 365 FO Business Events can send events/trigger/notification to external applications such as Azure Integrations, which can use this trigger to handle specific integration or business process scenarios. The Events existed in Finance and Operations were previously confined to use within Finance and Operations. The new capability provides a framework that will allow business processes in Finance and Operations to capture business events as business processes are executed and send the events to an external system or application. More about business event can beContinue reading “Dynamics 365 FO Integration using Business Events”