Output
Dynamics CRM Output
Creates records in a Dynamics 365 CRM (Dataverse) table, or — Upsert — updates the records whose key columns match and creates the rest, then passes the rows on.
When to use it
Use it to load leads from a spreadsheet, keep accounts in step with the ERP, or update opportunity stages in bulk.
In a pipeline
Excel InputRename ColumnDynamics CRM Output
Settings
| Setting | Type | Required | Default or hint |
|---|---|---|---|
| Connection | select | Yes | Add a connection below |
| Target Table | select | Yes | Select a table |
| Write Mode | select | — | append |
| Key columns | select | — | Columns that identify a row |
Example
Load event leads
- Target Table=leads
- Write Mode=Upsert
- Key columns=emailaddress1
| emailaddress1 | firstname | lastname |
|---|---|---|
| ann@harbour.example | Ann | Lee |
| raj@cole.example | Raj | Patel |
| emailaddress1 | firstname | lastname |
|---|---|---|
| ann@harbour.example | Ann | Lee |
| raj@cole.example | Raj | Patel |
Worth knowing
- Columns are sent as the table's logical column names; bind lookups with columns such as parentcustomerid_account@odata.bind = /accounts(<id>).
- Upsert on the table's own id column is a single PATCH; on other keys the record is looked up first.
- Dataverse has no transaction across requests: an error stops the node, and the records before it stay written. Replace is not offered. Previews never write.