Overview
This node integrates with Microsoft Dataverse to manage entity records within Dataverse tables. Specifically, the Update operation for the Entity Record resource allows users to modify existing records by specifying the table name, record ID, and fields to update.
Typical use cases include:
- Updating customer or contact information in a CRM system.
- Modifying opportunity details during sales processes.
- Adjusting inventory or product data dynamically based on external triggers.
For example, you might update an account's phone number or change the status of an opportunity record automatically when certain conditions are met in your workflow.
Properties
| Name | Meaning |
|---|---|
| Entity Table Name | The logical name of the Dataverse entity table where the record exists (e.g., accounts, contacts). |
| Record ID | The unique identifier (GUID) of the record to update. |
| Fields to Send | A collection of fields to update on the record. Each field includes: |
| - Field Name: The schema name of the field to update. | |
| - Field Value: The new value to set for that field. |
Output
The output JSON for the Update operation contains:
{
"success": true,
"recordId": "GUID-of-updated-record"
}
success: Boolean indicating if the update was successful.recordId: The unique identifier of the updated record.
No binary data is output by this operation.
Dependencies
- Requires an active connection to Microsoft Dataverse via an API key or OAuth credential configured in n8n.
- The node uses the Dataverse Web API endpoints to perform CRUD operations.
- Proper permissions on the Dataverse environment are necessary to update records.
Troubleshooting
Common Issues:
- Invalid or missing Record ID: Ensure the GUID provided corresponds to an existing record.
- Insufficient permissions: The API credentials must have write access to the specified entity table.
- Incorrect field names or values: Field names must match the schema names in Dataverse; values must be valid for the field type.
Error Messages:
- Errors returned from the API will be included in the output if "Continue On Fail" is enabled.
- Typical errors include HTTP 404 (record not found), 403 (forbidden), or 400 (bad request due to invalid fields).
Resolution:
- Verify the entity table name and record ID.
- Check API credentials and permissions.
- Validate field names and data types before sending.