Posts

Every Dynamics 365 implementation involves connections to other systems, utilizing technologies such as oData and custom web services. However, Dynamics 365 lacks built-in functionality to monitor outgoing or incoming requests, leaving no out-of-the-box solution for monitoring or alerts. Application Insights, a feature of Azure Monitor, enables monitoring for web applications like D365. To integrate Application Insights, we also need Azure API Management (APIM), which acts as a gateway for routing requests to Dynamics 365. ...

There are many ways to import data from external systems into Dynamics 365. One that I prefer is to import data using Recurring Integration. I won’t describe how to configure Recurring Integration in detail. You can find many articles on this – for example, this one from the atomicax.com blog. I will present how to create an Azure Logic app and configure the mechanism for importing data. In my scenario, I will put data into an Azure SQL table – it could also be a local SQL Server or another source that the Logic App connector could read data from. I will read this data using the stored procedure and send it to Dynamics 365 using an HTTP request. Let’s look at this solution in detail. ...

In one of the last Tech Talks, we can watch how to print warehouse labels via an external service (cloud label printing). The Microsoft engineers also presented that it is possible to print labels from the cloud Dynamics 365 F&O in the on-premises software such as BarTender or NiceLabel in many ways but the official documentation doesn’t show this in detail. Link to the TechTalk video: Beyond the DRA Cloud Label Printing for Dynamics 365 Supply Chain Management | TechTalk ...

In my very first post, I would like to talk about Azure App Service Hybrid Connection. During Dynamics 365 implementation, we usually have to design and develop many integrations. The integrations are various – web services, importing data from sources such as SQL databases using e.g. Recurring Integration, or Odata. The technologies are different, but so are the services we need to connect to. If they are exposed “to the world” then establishing communication with cloud-based D365 should not be a major problem. ...