OAuth offers clear advantages over basic authentication, establishing it as the superior choice for data integration projects that involve processing or consuming your Dynamics 365 Business Central data. In this blog post, we will explore the secure and flexible nature of OAuth, its advantages over basic authentication, and its role in data integration projects. By following the steps outlined in this concise guideline, you will be able to create a connection manager using OAuth authentication for integration with Dynamics 365 Business Central online.

While migrating from CRM to CRM, or any other Source system to CRM, in an ETL, records will need to be associated with users. And since the Source and Target Systems are different, there may not be a guarantee that some users may still exist in the organization. And in such cases, such users become either unlicensed, or stub users. These type of users have restrictions when it comes to being set as an owner of records, and in this blog post, we will see how this can be handled efficiently.

It is not unusual to run into a business requirement that you need to extract Dynamics 365 metadata during your ETL process. We used to believe that this is not a general requirement until we have recently announced our DES deprecation replacement solution, in which it is important to have a way to retrieve the list of Option Set values along with their label values in the system since Dynamics Entity Changes feature only returns integer values for those option set/picklist options. In this blog post, we will discuss this scenario and how to work with our DES deprecation replacement solution.

This post will walk you through how to query the Dynamics Business Central/NAV REST API data by using the Premium OData Source component.

Many of our clients are switching their Authentication to OAuth for their connections in our CDS and Microsoft Dynamics 365 CRM components. OAuth provides a better security infrastructure to protect your Dynamics data. The process of switching to OAuth authentication can be a bit confusing in the beginning if you have never worked on the concept before. In this post, we will walk you through the process with some great details to help you understand what is required and how OAuth works for our CDS/CRM connections.

While our Dynamics 365 toolkit supports Microsoft Dynamics 365 BC/NAV for reading and writing data, but the toolkit does not currently support Codeunit services. In this blog post, we will show you how to call Dynamics BC/NAV Codeunit services using the OData components that we have in the SSIS Productivity Pack product.

For most of you who work in the Dynamics or Power Platform community, you must have heard, Microsoft has recently announced some of the terminology changes for the CDS and Power Platform. In this blog post, I would like to share some of my personal perspectives on those changes.

Explore working with Dynamics BC/NAV Codeunit web service by using HTTP Connection Manager and Web Service components offered in our SSIS Productivity Pack.