Connector Details

Connector Attributes	Details
Name	Dynamics 365 FO (Direct)
Description	Dynamics 365 Finance and Operations (FO) is a comprehensive enterprise resource planning (ERP) solution developed by Microsoft, designed to streamline and optimize financial, supply chain, manufacturing, and human resource management processes for large and medium-sized organizations. It offers a unified platform that integrates financial management, inventory management, procurement, sales, production, and human capital management functionalities, enabling businesses to manage their operations more efficiently and effectively. Dynamics 365 FO provides advanced analytics and reporting capabilities, real-time insights, and predictive analytics to help organizations make data-driven decisions and adapt to changing market dynamics. With its flexible deployment options, scalability, and extensibility, Dynamics 365 FO empowers organizations to drive digital transformation, improve operational agility, and achieve business growth.
Connector Type	Class D

Features

Feature Name	Feature Details
Load Strategies	Full Load, Incremental Load
Metadata Extraction	Supported
Data Acquisition	Supported
Data Publishing	Supported
Automated Schema Drift Handling	Not Supported

Source Connection Attributes

Connection Parameters	Data Type	Example
Connection Name	String	Dynamics365FOConnector
Dynamics URL	String	https://your-dynamics-instance.operations.dynamics.com
Azure Tenant ID	String	your-azure-tenant-id
OAuth Client ID	String	your-oauth-client-id
OAuth Client Secret	String	your-oauth-client-secret
Client Details Secret Name (Optional)	String	your-secret-name
Bronze Schema (Optional)	String
Silver Schema (Optional)	String

Connector Specific Configuration Details

Dynamics 365 FO (Dataverse via Synapse Link) connector has optional values such as Bronze Schema and Silver Schema
These connectors service both the CRM and FnO ERPs of Dynamics 365. The only difference in implementation is in the dynamics_erp portion of the connection string.
The extraction piece inherits the CData JDBC base class. Just overloading the configure secrets method to build the connection string from the JSON object.
The publishing side implements it's own class. The class features are largely borrowed from the DDU workflow.
The Log Table gives more fine-grained information about failures that can be achieved in the standard publish metrics.
Each record is pushed independently to the target in parallel using multi-threading. Failed records are moved to the quarantine database along with metadata about the operation and the failure.

Example for Dynamics - CE connection string:

'{"dynamics_erp": "dynamics365", "dynamics_url": "my.fno.dynamics.com", "azure_tenant": "abc-123", "client_id": "my_client_id", "client_secret": "my_client_secret", "extra_clients_secret_name": "ddu-publishing-secrets"}

Screenshot To Use Connector