Skip to main content

Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that sends data to a Microsoft Dynamics 365 location.
ms_dyn_api.png

Microsoft Dynamics 365

Create a Microsoft Dynamics 365 Destination​

  1. Click the + icon on the Nexset that will be sent to the Microsoft Dynamics 365 destination, and select the Send to Destination option from the menu.

  2. Select the Microsoft Dynamics 365 connector from the list of available destination connectors. Then, select the credential that will be used to connect to your Dynamics 365 organization, and click Next; or, create a new Microsoft Dynamics 365 credential for use in this flow.

  3. In Nexla, Microsoft Dynamics 365 destinations can be created using pre-built endpoint templates, which expedite destination setup for common Dynamics 365 endpoints. Each template is designed specifically for the corresponding Dynamics 365 endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    Microsoft Dynamics 365 destinations can also be configured manually, allowing you to send data to Dynamics 365 endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Microsoft Dynamics 365 endpoints. Each template is designed specifically for the corresponding Dynamics 365 endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

    Add New Records to Entity

    This endpoint template creates new records for a specified entity in your Dynamics 365 organization. Use this template when you need to create new records such as accounts, contacts, opportunities, or custom entities. You can create multiple related entity records in a single operation using deep insert.

    • Enter the entity type in the Entity Type field. This should be the logical collection name of the Dynamics 365 entity (e.g., accounts, contacts, opportunities). Note that this should be the logical collection name, not the display name. The entity type determines which entity will receive the new records.

    This endpoint sends data as JSON in the request body to create new records in the specified entity. The request body should contain the entity data in JSON format, with field names matching the logical names of entity attributes. You can create multiple related entity records in a single operation using deep insert by including related entity data in the request body.

    The entity type must be the logical collection name (e.g., accounts), not the display name (e.g., "Accounts"). Field names in the request body must match the logical names of entity attributes. For detailed information about creating records, available entities, field names, and deep insert capabilities, see the Microsoft Dynamics 365 Web API create documentation.

Configure Manually​

Microsoft Dynamics 365 destinations can be manually configured to send data to any valid Dynamics 365 Web API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Dynamics 365 Web API after each call to a new Nexla webhook data source.

API Method​

  1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Dynamics 365 Web API from the Method pulldown menu. Dynamics 365 Web API typically uses POST method for creating records, PATCH method for updating records, and DELETE method for deleting records.

Data Format​

  1. Select the format in which the Nexset data will be sent to the Dynamics 365 Web API from the Content Format pulldown menu. Dynamics 365 Web API expects JSON format for all requests.

API Endpoint URL​

  1. Enter the URL of the Dynamics 365 Web API endpoint to which data will be sent in the URL field. This should be the complete URL including your organization URL (from your credential), the API path (e.g., /api/data/v9.0/accounts), and any required query parameters (e.g., https://contoso.crm.dynamics.com/api/data/v9.0/accounts). Include any required query parameters in the URL.

Ensure the API endpoint URL is correct and includes the entity collection name. The Dynamics 365 Web API endpoint URL should point to the entity collection where you want to create records (e.g., /api/data/v9.0/accounts for accounts). You can test the endpoint using the Test button after configuring the URL.

Request Body​

  1. Configure the request body that will be sent to the Dynamics 365 Web API. The request body should contain the entity data formatted as JSON, with field names matching the logical names of entity attributes. The request body format is typically {message.json} to send the entire Nexset data as JSON, or you can construct a custom JSON structure with specific field mappings.

The request body must be valid JSON and must match the Dynamics 365 Web API's expected format for the specified entity. Field names in the request body must match the logical names of entity attributes. For detailed information about request body formats, available entities, field names, and deep insert capabilities, see the Microsoft Dynamics 365 Web API create documentation.

Save the Destination​

  1. Once all of the relevant steps in the above sections have been completed, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the destination configuration for later use.