Docs
Search K

Appearance

D365 Update Record ​

Description ​

The D365 Update Record node updates a single record in Microsoft Dynamics 365 / Dataverse.
You specify the target record by its unique Record ID (GUID) and provide a set of field mappings that define which columns to update and what values to apply.

This node is typically used to:

  • Modify existing records after a lookup or search
  • Update status fields, owners, or related data
  • Push calculated or external values back into Dynamics 365

How to Use ​

When added to a workflow, this node presents a configuration form with the following input fields.

FieldTypeDescriptionRequiredVisible When
ServiceAccount - Microsoft Dynamics 365Service Account PickerSelect the service account with permission to update records in Dynamics 365.✅Always
Entity TypeTextThe logical name of the entity to update (e.g., account, contact, opportunity, or custom entity).✅Always
Record IdTextThe unique identifier (GUID) of the record to update.

Example: 7f3c2e10-4b19-4e64-a932-12aafd2db4f5		✅Always
Field MappingsKey/Value DictionaryDefines the fields to update and their new values.

Example:
{ "telephone1": "03 9000 0000", "emailaddress1": "info@tentech.com" }		✅Always
Return ColumnsList of TextOptional list of columns to return after the update. Use this when you want to capture the updated record values for later workflow steps.

Example: ["name", "modifiedon"]		❌Optional

Behavior ​

  • The node connects to the selected Dynamics 365 service account.
  • The record is identified by its Record ID (must be a valid GUID).
  • The specified fields are updated with the provided values.
  • If Return Columns are provided, the node retrieves those values from the updated record and outputs them for use in downstream nodes.
  • The update uses the Dataverse REST API, which enforces all entity-level permissions and validation rules.

Example Configurations ​

Example 1 – Update Account Contact Details ​

SettingExample Value
ServiceAccount - Microsoft Dynamics 365DynamicsProdService
Entity Typeaccount
Record Id7f3c2e10-4b19-4e64-a932-12aafd2db4f5
Field Mappings{ "telephone1": "03 9000 0000", "emailaddress1": "info@tentech.com" }

Result:
The specified Account record is updated with a new phone number and email address.

Example 2 – Update Contact and Return Confirmation Fields ​

SettingExample Value
ServiceAccount - Microsoft Dynamics 365DynamicsProdService
Entity Typecontact
Record Idb223fb3e-1e26-4b73-8a8d-6f0f5a5d9caa
Field Mappings{ "jobtitle": "Engineering Manager", "department": "Operations" }
Return Columns["fullname", "modifiedon"]

Result:
Updates the contact record and returns the fullname and modifiedon fields as confirmation.

Outputs ​

After successful execution, this node produces the following output variables.

Output VariableTypeDescription
Record IdTextThe unique ID of the record that was updated.
Entity TypeTextThe entity type that was updated.
Updated ValuesObject(Optional) If Return Columns were specified, this object contains the returned field values from Dynamics 365.

Example Workflow Usage ​

  1. Use a D365 Get Record or D365 Search Records node to find a record and capture its ID.
  2. Pass that ID into the Record Id input of this node.
  3. Define the Field Mappings for the fields you want to modify.
  4. (Optional) Use Return Columns to retrieve updated values such as timestamps or owner details.
  5. Chain this node with other actions (e.g., Email Notification, D365 Execute Action) to continue the workflow.

Status Messages ​

StatusDescription
CompletedRecord updated successfully.
FailUpdate failed due to invalid ID, missing field, or connection error.

Error Handling ​

If the update fails, the workflow will stop at this node and display an error message. Common causes include:

  • Invalid or missing Dynamics 365 service account
  • Invalid Record Id (must be a valid GUID)
  • Incorrect entity or field names (must use logical names)
  • Insufficient permissions for the connected service account
  • Data validation errors in Dynamics 365 (e.g., required field missing)

Example JSON (for reference only) ​

json
{
  "ServiceAccount-Microsoft Dynamics 365": "DynamicsProdService",
  "Entity Type": "account",
  "Record Id": "7f3c2e10-4b19-4e64-a932-12aafd2db4f5",
  "Field Mappings": {
    "telephone1": "03 9000 0000",
    "emailaddress1": "info@tentech.com"
  },
  "Return Columns": ["name", "modifiedon"]
}

Notes ​

  • All field names must use logical names as defined in Dynamics 365 (e.g., telephone1, not “Business Phone”).
  • The Record Id must be a valid GUID. If you’re retrieving it from a previous node, wrap it in {VariableName} syntax.
  • When Return Columns are included, ensure they exist and are retrievable by the connected user’s permissions.
  • This node is ideal for integration workflows where records must be updated dynamically based on search results, AI outputs, or data transformations.

Category: Integrations → Microsoft Dynamics 365 Task Name: D365UpdateRecord

Tentech 2024