User Guide > Map Connectors > Source and Target Map Connectors > Microsoft Dynamics 365 Multimode
Was this helpful?
Microsoft Dynamics 365 Multimode
Microsoft Dynamics 365 is a set of intelligent business applications offered by Microsoft. These applications help you run your entire business and deliver greater results through predictive, AI-driven insights. A Microsoft Dynamics 365 account is required before you can use our Microsoft Dynamics 365 connector. The connector is based on the OData (Open Data Protocol) standard, which is a widely accepted standard for building and consuming RESTful APIs.
The multimode connector allows you to read, write, or append data to multiple tables at one time within one map. You can quickly setup a multimode connector using the multimode wizard. For more information, see Setting Up Multimode Target Connector Using Multimode Wizard.
Prerequisites
You should have a valid Microsoft Dynamics 365 account and the required access tokens.
Connector-Specific Notes:
• Data Operations: Perform CRUD (Create, Read, Update, Delete) operations on the Dynamics 365 entities. Use HTTP methods (GET, POST, PUT, DELETE) to interact with records.
• Querying Data: Use OData queries to filter, sort, and retrieve specific data from Dynamics 365.
• Metadata Operations: OData services expose metadata (like entities, attributes, and relationships) that describes the structure of the data, making it self-descriptive. Clients can understand the data model and query capabilities through this metadata.
• Authentication: Authenticate using OAuth 2.0. This ensures secure access to data and services.
• Batch Operations: Bundle multiple operations into a single HTTP request using batch operations, reducing the number of round-trips to the server.
• Integration: Integrate Dynamics 365 with other systems, applications, and services. This could include custom applications, third-party services, or other Microsoft products.
• Field names that you see in the MS Dynamic 365 application may not appear exactly same in DataConnect. They may be slightly different though same in meaning and relevance. The reason is DataConnect fetches the field data from MS Dynamic 365 through REST API calls and DataConnect displays exactly what it has received in the response data from the API. For example, Invoice ID in MS Dynamic 365 application is displayed as invoicenumber in DataConnect.
Connector Parts
Connector parts are the fields you configure to connect with a data source or target. The fields that are available depend on the connector you select. Multimode connectors are target only connectors. For a list of all parts for target connectors, see Specifying Target Connector, Parts, and Properties.
Specify the following connector parts for the Microsoft Dynamics 365 connector:
Connector Part
Description
Client ID
This is the Application (client) ID of the App you have registered in Azure AD. You can find this information on the Overview page of your Azure portal.
Client secret value
The client secret value that you have created using the Certificates & secrets>New client secret option. This value can only be seen when you are creating it, hence write it down at the time of creation.
Tenant ID
This is the Directory (tenant) ID. You can find this information on the Overview page of your Azure portal.
Dynamics 365 domain
The web address used to navigate to your Dynamics 365 commerce sites in. You can find this information on the Environments>your-environment page of the admin.powerplatform portal. It will be listed as domain-name.crm.dynamics.com.
For example if actual environment URL is https://orgc8888f2c.crm.dynamics.com/ the value you need to provide is orgc8888f2c.
Property Options
You can specify the following target properties:
Property
Description
Flush Frequency
Number of records buffered in the memory before being written to the target. Default value is 0 (all records are written at once).
When inserting many records, change the default to a higher value to improve performance.
Batch Response
The file to which CRUD operation results are written. The format is one entry per record, indicating success or failure. If operation fails, information about cause of failure is returned.
Default is to not write a batch response file.
Enable Batch Processing
Allows you to group related SQL statements into a batch and submit them in one go to the database server. This is a performance tuning option.
Default value is TRUE.
Batch Execution Size
Number of queries to execute in one batch. Default value is 50.
The Enable Batch Processing property must be set to TRUE when using this property.
Query Options
A query option is basically requesting that a service perform a set of transformations such as filtering, sorting, etc. to its data before returning the results. Given below are some examples of the options (for more details, see Query options overview):
• Select
account?$select=revenue,name
• Filter
account?$filter=name eq ‘Milk’
account?$filter=revenue gt 150000
account?$select=revenue,name,openreveneue&$filter=openrevenue gt 10000 and name eq ‘new account’
• Orderby
Orderby name ascending: account?$orderby=revenue asc
Orderby name descending: account?$orderby=revenue desc
Supported Output Modes
Microsoft Dynamics 365 Multimode connector supports the Multimode output mode. For more information, see Target Output Modes.
Supported Data Types
The following data types are supported:
• Edm.Boolean
• Edm.DataTimeOffset
• Edm.Date
• Edm.Decimal
• Edm.Guid
• Edm.String
• Edm.Int32
• Edm.Int64
Limitations
The current Microsoft dynamics 365 connector does not support web API actions.
Last modified date: 12/03/2024