Dynamics 365 FO (Direct)

Connector Details

Connector AttributesDetails
NameDynamics 365 FO (Direct)
DescriptionDynamics 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 TypeClass D


Feature NameFeature Details
Load StrategiesFull Load, Incremental Load
Metadata ExtractionSupported
Data AcquisitionSupported
Data PublishingSupported
Automated Schema Drift HandlingNot Supported

Source Connection Attributes

Connection ParametersData TypeExample
Connection NameStringDynamics365FOConnector
Dynamics URLStringhttps://your-dynamics-instance.operations.dynamics.com
Azure Tenant IDStringyour-azure-tenant-id
OAuth Client IDStringyour-oauth-client-id
OAuth Client SecretStringyour-oauth-client-secret
Client Details Secret Name (Optional)Stringyour-secret-name
Bronze Schema (Optional)String
Silver Schema (Optional)String

Connector Specific Configuration Details

  1. Dynamics 365 FO (Dataverse via Synapse Link) connector has optional values such as Bronze Schema and Silver Schema

  2. 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.

  3. The extraction piece inherits the CData JDBC base class. Just overloading the configure secrets method to build the connection string from the JSON object.

  4. The publishing side implements it's own class. The class features are largely borrowed from the DDU workflow.

  5. The Log Table gives more fine-grained information about failures that can be achieved in the standard publish metrics.

  6. 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.

  7. 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"}
  8. More details around this connector

Screenshot To Use Connector