Microsoft Dynamics CRM and Dataverse provide customer, sales, service, and business-data management through a structured table model and application APIs that support querying and updating business records.
The Flowgear Microsoft Dynamics CRM Node lets you query Dataverse tables and create or update records from a Workflow. Use it when you want Flowgear to read CRM data, page through result sets, or write batched business changes into a Dynamics CRM or Dataverse environment.
0.1.0.2 - Current release.
0.1.0.1 - Removed query paging controls from templates and kept continuation paging inside the Node.
0.1.0.0 - Added eager startup and lazy continuation for streamed invokes.
0.0.0.9 - Aligned the V2 connector contract and public help article.
0.0.0.1 - Initial release.
0.0.0.3 - Template changes.
0.0.0.7 - Node name correction.
| Property |
Type |
Description |
Instance URL |
String |
The base URL for the Dynamics 365 or Dataverse instance, for example https://org.crm.dynamics.com. |
Client ID |
String |
The client identifier from the Entra application registration. |
Client Secret |
Masked |
The client secret associated with the Entra application registration. |
- Register an Entra application that can access your Dynamics CRM or Dataverse environment.
- Grant the permissions required for your CRM scenario.
- Add the application as an application user in the Dynamics CRM or Dataverse environment and assign the required security roles.
- Configure the Flowgear Connection with
Instance URL, Client ID, and Client Secret.
- Test the Connection before using the Node in a Workflow.
| Parameter |
Type |
Description |
Connection |
Connection |
The connection for the Dataverse environment. |
Request |
Object |
A query definition containing Entity, optional Select, optional Filter, and optional Order. |
| Return |
Type |
Description |
Response |
Array |
The returned Dataverse rows merged with the request context that identified the query. |
| Parameter |
Type |
Description |
Connection |
Connection |
The connection for the Dataverse environment. |
Request |
Array |
Payloads describing the target Entity and Attributes to create. |
Batch Size |
Integer |
The number of items to include per batch request. The default is 20. |
| Return |
Type |
Description |
Response |
Array |
The mutation result for each request item, including the echoed request context and CRM-specific fields such as Action, Success, Id, Message, and ErrorCode when available. |
Flowgear |
Object |
Default mutation fields containing IsSuccess and Message. |
| Parameter |
Type |
Description |
Connection |
Connection |
The connection for the Dataverse environment. |
Request |
Array |
Payloads describing the target Entity, required Id, and Attributes to update. |
Batch Size |
Integer |
The number of items to include per batch request. The default is 20. |
| Return |
Type |
Description |
Response |
Array |
The mutation result for each request item, including the echoed request context and CRM-specific fields such as Action, Success, Id, Message, and ErrorCode when available. |
Flowgear |
Object |
Default mutation fields containing IsSuccess and Message. |
- Query methods do not append default mutation fields to returned rows.
- If a query returns no matching records, the Node emits zero rows.
- If the first provider query call fails, the provider error surfaces to the Workflow instead of being converted into a query error row.
- Query templates omit
Top and PageSize. The Node ignores stale saved values and follows Dataverse continuation links internally.
Query retrieves its first Dataverse page while the Node invoke is awaited. It retrieves continuation pages only as the Workflow consumes rows.Create and Update execute the first bounded request batch while the Node invoke is awaited, then process later batches as the Workflow consumes results. Empty Request input emits zero rows and does not send a provider mutation.- Create and Update preserve the existing CRM-specific mutation fields and also add Flowgear mutation metadata under
Flowgear.