SSIS Dynamics CRM / Dataverse / PowerApps Destination

Connect to Dynamics 365, Dataverse or on-premises CRM.

Create a ZS-DYNAMICS-CRM connection and choose the authentication type: OAuth 2.0 Client Credentials or OAuth Delegated (interactive sign-in, for MFA / 2FA) for Dynamics 365 Online and Dataverse, or IFD and Active Directory for on-premises CRM. Then select the organization and click Test Connection. The older Online Federation (user name / password) mode is deprecated.

• One connection for CRM Source and CRM Destination
• Custom TokenUrl (e.g. US GCC)
• Retry on throttling such as HTTP 429

Connection manager help

Upsert and split inserted, updated and failed rows.

Set Operation to UpdateOrInsert and put the table’s primary key (for example accountid) or an alternate key in UpsertKeyField; the key must be mapped. Each row then goes to the Inserted or Updated output (blue arrows), or to the error output (red arrow).

• Primary key or alternate key
• DoNotCreateOutputs removes unused outputs for speed

Bulk update or delete existing records.

Update uses the same settings as upsert with Operation = Update and a primary or alternate key. For Delete, set Operation = Delete and map only the primary key column. Delete child records first if CRM reports that the record is associated with another object.

• BatchSize rows per request
• EnableParallelProcessing, 1 to 40 threads

Keep good rows flowing; capture bad ones.

Drag the red error arrow to a downstream component and set Redirect for both Error and Truncation. Failed records land there while the remaining rows are still loaded. A summary at the end reports total, inserted, updated, deleted and error counts.

• Progress reported every N rows
• UseDefaultIfLookupFails writes null for unmatched lookups