Disassociate Records
dynamics_crm.disassociate
ActionCRM & salesconnection required
Calls the Microsoft Dynamics 365 API with the connection's credentials.
Remove a relationship between two rows through a navigation property, leaving both rows in place.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Microsoft Dynamics 365
- Secret shape
- {"client_id": "…", "client_secret": "…", "refresh_token": "…"}
- Config it needs
- org_url, tenant, api_version
- Resolved by
- config.connection_id, else node.connection_id
Configuration
5 fields, 4 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
entity_set The entity set to work with: 'accounts', 'contacts', 'opportunities', 'leads', 'incidents' (cases), 'tasks', or any other table's entity set name, including custom tables. It is the plural name from the table's 'Copy set name' in Power Apps, which is not always the plural of the table name. | string | Yes | — | — | accounts |
record_id The row's primary key GUID, or an alternate-key predicate such as firstname='Joe',emailaddress1='joe@contoso.com'. | string | Yes | — | — | 00000000-0000-0000-0000-000000000001 |
navigation_property The navigation property holding the relationship to remove. | string | Yes | — | — | contact_customer_accounts |
target_record_id The id of the related row to remove. A collection-valued navigation property holds many rows, so the one to remove has to be named; a single-valued one holds exactly one and the id is ignored. | string | Yes | — | — | 00aa00aa-bb11-cc22-dd33-44ee44ee44ee |
relationship_kind Whether the navigation property holds a collection of rows (one-to-many from the 'one' side, or either side of a many-to-many) or a single related row (the 'many' side of a one-to-many). | string | No | collection | one of "collection", "single" | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"entity_set": "accounts",
"navigation_property": "contact_customer_accounts",
"record_id": "00000000-0000-0000-0000-000000000001",
"relationship_kind": "collection",
"target_record_id": "00aa00aa-bb11-cc22-dd33-44ee44ee44ee"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
entity_set The entity set holding the row that was changed. | string | — |
record_id The row the relationship was removed from. | string | — |
navigation_property The navigation property that was cleared. | string | — |
target_record_id The related row that was removed, if named. | string | — |
disassociated True when Dataverse accepted the disassociation. | boolean | — |
{
"disassociated": false,
"entity_set": "",
"navigation_property": "",
"record_id": "",
"target_record_id": ""
}Notes
- A collection-valued navigation property is DELETE .../{nav}({target_record_id})/$ref, so the related row must be named; the single-valued form is DELETE .../{nav}/$ref and ignores it.
Related Microsoft Dynamics 365 nodes
See Disassociate Records run in a workflow.
In a technical demo we add the Microsoft Dynamics 365 connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.