Actions6
Overview
This node integrates with the Microsoft Dynamics 365 Dataverse API, enabling users to perform various operations on Dataverse entities. Specifically, the Update record operation allows updating an existing record in a selected Dataverse entity by specifying the record ID and the columns to update.
Common scenarios for this node include:
- Automating updates to customer or contact records based on external triggers.
- Synchronizing data changes from other systems into Dataverse.
- Modifying specific fields of an entity record without replacing the entire record.
For example, you could use this node to update the email address and phone number of a contact record identified by its unique record ID.
Properties
| Name | Meaning |
|---|---|
| Record Id | The unique identifier of the record to update in the selected Dataverse entity. |
| Entity Name | The Dataverse entity where the record exists (e.g., contacts, accounts). |
| Columns | One or more columns to update, each with: |
| Column Name | The specific column/field in the entity to update. |
| Column Value | The new value to set for the specified column. |
The Entity Name property is populated dynamically by loading available entities from Dataverse. Similarly, the Column Name options are dynamically loaded based on the selected entity.
Output
The node outputs JSON data representing the result of the update operation for each input item. The output JSON typically contains the updated record information as returned by the Dataverse API after applying the changes.
If multiple columns are updated, the output reflects the final state of those columns post-update.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to connect securely to the Dataverse API.
- Relies on the Dataverse API endpoints for listing entities, retrieving entity columns, and performing update operations.
- The node caches entity and column metadata to optimize repeated calls.
Troubleshooting
- Authentication errors: Ensure that the API key or authentication token credential is valid and has sufficient permissions to update records in the target Dataverse environment.
- Invalid Record Id: If the specified record ID does not exist or is malformed, the node will throw an error. Verify the record ID correctness.
- Entity or Column not found: Selecting an entity or column that does not exist or is inaccessible will cause failures. Refresh the entity and column lists if needed.
- Data type mismatches: Providing values incompatible with the column's expected data type may result in API errors. Validate input values accordingly.
- API rate limits or connectivity issues: Network problems or API throttling can cause intermittent failures. Retry or check network status.
Error messages typically include details about the failed API call or validation issue, helping pinpoint the root cause.