Dynamics 365

Discover more about the Dynamics 365 connector and how to use it on the Digibee Integration Platform.

The Dynamics 365 connector enables integrations with the Microsoft Dynamics 365 CRM product. It allows you to query, create, update, or delete data stored in Dataverse, the database used by Dynamics 365 CRM.

Parameters

Configure the connector using the parameters below. Fields that support Double Braces expressions are marked in the Supports DB column.

General

Parameter	Description	Type	Supports DB	Default
Alias	Name (alias) for this connector’s output, allowing you to reference it later in the flow using Double Braces expressions. Learn more.	String	✅	dynamics-1
Fail on Error	If enabled, interrupts the pipeline execution when an error occurs. If disabled, execution continues, but the "success" property will be set to false.	Boolean	❌	N/A

Authentication

Parameter	Description	Type	Supports DB	Default	Visible when
BaseURL	URL of the Dynamics 365 instance.	String	✅	https://org10ac0015.crm2.dynamics.com	—
Use Dynamic Account	If enabled, the connector uses the account dynamically via the Store Account connector; otherwise, it uses the account statically as configured in Accounts on the Platform.	Boolean	❌	false	—
Scoped	If enabled, isolates the stored account from other sub-processes. Not supported for accounts used in headers or body. To learn more, read the Dynamic Accounts documentation.	Boolean	❌	false	Dynamic Account is enabled
Account Name	Name of the account defined in the Store Account connector.	String	✅	N/A	Dynamic Account is enabled
Dynamics Azure Account	Account that contains Azure AD credentials for Dynamics 365. Supported type: Azure Key.	Account	❌	N/A	Dynamic Account is disabled

Dynamics API

Parameter	Description	Type	Supports DB	Default
API Version	Version of the Dynamics 365 Web API to use.	String	✅	9.2
HTTP Method	HTTP method for the Dynamics 365 request. Supported method: GET, POST, PATCH, DELETE.	Select	❌	GET
Entity Name	Entity to interact with in Dynamics 365 (for example, account or contact). Depending on the method and entity, additional configuration fields may appear. Displayed only after successful authentication.	Select	❌	N/A
Interactive Mode (POST, PATCH)	If enabled, shows additional fields in the form to help you build the request. If disabled, you must manually enter the raw JSON.	Boolean	❌	False
Body (POST, PATCH)	JSON content of the request.	JSON	✅	N/A

Advanced Settings

Parameter	Description	Type	Supports DB	Default
Request timeout (seconds)	Maximum timeout for HTTP requests to the Dynamics 365 API.	Integer	❌	30

Documentation

Parameter	Description	Type	Supports DB	Default
Documentation	Optional field to describe the connector configuration and any relevant business rules.	String	❌	N/A

Supported operations

The Dynamics 365 connector supports operations that follow the REST standard. You can perform the following HTTP methods:

• GET: Retrieve records

• POST: Create new records

• PATCH: Update existing records

• DELETE: Remove records from Dataverse

GET requests

When performing GET requests, the connector supports two query modes:

• OData: Enables straightforward data retrieval using URL-based queries.

• FetchXML: Allows advanced data retrieval through an XML-based query language similar to SQL.

These query modes are unavailable when the Entity ID parameter is provided.

POST or PATCH requests

When performing POST or PATCH requests, the connector provides two primary ways to define the record data:

• Body: Allows the user to manually insert a JSON containing the specific fields and their respective values.

• Interactive Mode: Automatically generates the available fields, allowing the user to simply provide the values for each one.