D365 Bulk Operation

Overview

The D365 Bulk Operation node allows workflows to perform batch operations (Create, Update, or Delete) on records within Microsoft Dynamics 365 / Dataverse.

It connects securely to Dynamics 365 using a preconfigured Service Account and executes multiple record operations in a single task — ideal for processing lists of records, synchronizing data, or applying updates across large datasets.

Typical use cases include:

• Creating new entity records from imported data
• Updating specific fields across multiple records
• Deleting obsolete or temporary records in bulk

---

Configuration

When configuring this node in the workflow designer, a modal form appears with the following fields.

Field	Type	Description	Required	Visible When
ServiceAccount - Microsoft Dynamics 365	Service Account Picker	Select the configured Dynamics 365 service account to authenticate with.	✅	Always
Entity Type	Text	The logical name of the Dataverse entity (e.g., account, contact, custom_entityname).	✅	Always
Operation	Picklist	The bulk operation to perform. Options: - Create - Update - Delete	✅	Always
Field Mappings	Key/Value Dictionary	Defines the field schema for create/update operations. Example: { "name": "Account Name", "emailaddress1": "Email" }	✅	Create, Update
Record Values	JSON Array	Used for Create operations. Each inner array represents one record’s values in order of the field mappings. Example: [[ "Tentech", "info@tentech.com" ], [ "MinuteView", "contact@minuteview.com" ]]	✅	Create
Record Ids	String List	List of record GUIDs to update or delete. Example: ["7f3c2e10-4b19-4e64-a932-12aafd2db4f5", "50bb6a32-39af-4214-9a56-b4bbec4e099f"]	✅	Update, Delete

---

Behavior by Operation Type

🟢 Create

• Requires Field Mappings and Record Values
• Automatically creates new entity records in Dynamics 365
• Each inner array in Record Values corresponds to a single record
• The order of values must match the field order in Field Mappings

🟠 Update

• Requires Record Ids and Field Mappings
• Updates all specified records using the given field/value pairs
• Invalid GUIDs or missing fields are logged as individual errors

🔴 Delete

• Requires Record Ids
• Permanently deletes all records matching the provided IDs
• Invalid or missing record IDs are logged as errors

---

Outputs

After execution, the node returns several variables that can be used in downstream workflow nodes.

Output Variable	Type	Description
SuccessCount	Number	Number of records successfully processed.
FailureCount	Number	Number of records that failed to process.
ProcessedIds	List	Array of successfully processed record IDs.
Errors	List	Array of error messages for failed records.
Operation	Text	The operation performed (create, update, delete).
EntityType	Text	The entity type processed.

---

Example Configurations

Example 1 – Bulk Create Accounts

Setting	Value
ServiceAccount - Microsoft Dynamics 365	DynamicsProdService
Entity Type	account
Operation	Create
Field Mappings	{ "name": "Account Name", "emailaddress1": "Email" }
Record Values	[[ "Tentech", "info@tentech.com" ], [ "MinuteView", "contact@minuteview.com" ]]

Result: Two new account records are created in Dynamics 365 with corresponding name and email values.

---

Example 2 – Bulk Update Contacts

Setting	Value
ServiceAccount - Microsoft Dynamics 365	DynamicsProdService
Entity Type	contact
Operation	Update
Record Ids	["7f3c2e10-4b19-4e64-a932-12aafd2db4f5", "50bb6a32-39af-4214-9a56-b4bbec4e099f"]
Field Mappings	{ "telephone1": "123456789", "jobtitle": "Updated" }

Result: Updates both contacts with new phone and job title information.

---

Example 3 – Bulk Delete Leads

Setting	Value
ServiceAccount - Microsoft Dynamics 365	DynamicsProdService
Entity Type	lead
Operation	Delete
Record Ids	["2c661b8f-23a5-4cd1-bde2-48e6e2a84db8", "7a0a93c9-1e3d-4f5d-8a2e-96c7e03ebd2b"]

Result: Deletes the specified leads from Dynamics 365.

---

Validation Rules

• The node automatically validates that all required inputs for the chosen operation are present.
• If validation fails (e.g., missing Record Ids for Delete), the workflow halts with a Fail status.
• Invalid GUIDs or formatting errors are captured in the Errors output.

---

Status and Logging

Status	Description
Completed	All records processed successfully.
CompletedWithErrors	Some records failed; see Errors output for details.
Fail	Node failed due to configuration error, missing service account, or invalid JSON.

---

Notes

• The D365 service account must be preconfigured with correct client ID, secret, tenant, and org URL.
• Bulk operations use the Dataverse REST API, respecting user-level permissions defined in the connected environment.
• For large datasets, consider adding delays or batching in your workflow to avoid API throttling.

---

Troubleshooting

Issue	Likely Cause	Resolution
D365 Service Account not found	Invalid or missing service ID	Verify the selected service account is configured under Connections → Microsoft Dynamics 365.
Invalid RecordValues JSON format	Incorrect JSON array format	Ensure record values are provided as [[...],[...]].
Invalid ID format	One or more Record IDs not valid GUIDs	Check the list and correct the formatting.
Operation partially succeeded	Some records failed	Inspect Errors output and retry only the failed records.

---

Category: Integrations → Microsoft Dynamics 365 Visibility Control: OperationOutput Variable Prefix: D365BulkOperation

---