Dynamics 365 Dual-write: F&O to Dataverse Bidirectional Sync

TL;DR

• Bottom line: Dual-write provides near-real-time, bidirectional synchronization between Dynamics 365 Finance & Operations (F&O) apps and Microsoft Dataverse (CE apps) using an out-of-box, no-code/low-code framework with pre-built table maps. [src1]
• Key limit: 1,000 records per transaction from F&O to Dataverse, with a hard 2-minute timeout on all live sync transactions in both directions. [src2]
• Watch out for: Initial sync has a separate 500,000-row-per-run limit per legal entity, and single-threaded tables (Customers V3, Vendors V2) cannot exceed 70,000 rows from Dataverse without timing out. [src3]
• Best for: Keeping master data (customers, products, vendors) synchronized in near-real-time between F&O and CE apps (Sales, Customer Service, Field Service). [src1]
• Authentication: Managed by Power Platform integration -- no separate OAuth setup required; environments are linked via Lifecycle Services (LCS) or Power Platform admin center. [src1]

System Profile

Dual-write is a Microsoft-provided infrastructure that enables near-real-time, bidirectional data synchronization between Dynamics 365 Finance & Operations (F&O) apps and customer engagement (CE) apps built on Microsoft Dataverse. It ships as two Marketplace solutions installed on Dataverse that extend the table schema, plugins, and workflows to handle ERP-scale data volumes. Covers all F&O SKUs (Finance, Supply Chain Management, Commerce, Project Operations). Does NOT cover Business Central integrations.

API Surfaces & Capabilities

Dual-write is a synchronization framework, not a traditional API. It uses table-to-table maps defining how data flows between F&O data entities and Dataverse tables, handling OData and plugin orchestration automatically.

Rate Limits & Quotas

Per-Transaction Limits (Live Sync)

Initial Sync Limits

Authentication

Dual-write does not require separate OAuth or API key authentication. The integration is established by linking F&O and Dataverse environments through the Power Platform integration process.

Authentication Gotchas

• Only the user who set up the Dual-write connection can create table maps -- other admins cannot create maps without re-establishing the connection. [src5]
• All dual-write users in CE must be assigned the Dual-Write Runtime User security role or they cannot create rows in synced tables. [src3]
• All dual-write users need the Dual-Write App User role for read access to Company and Currency Exchange tables, which are global. [src3]

Constraints

• 1,000 record transaction limit: F&O-to-Dataverse live sync aborts any single transaction with >1,000 records. Custom X++ code must split batches using ttsbegin/ttscommit blocks of 1,000 or fewer. [src2]
• 2-minute timeout: Both sides must commit within 2 minutes. Includes time for Dataverse plugins (standard + custom). Can be increased to 5 minutes only via Microsoft Support request. [src2]
• Cloud-only: Dual-write requires cloud-hosted F&O and Dataverse. On-premise F&O deployments cannot use Dual-write. [src1]
• No partial retry on initial sync: If individual rows fail during initial sync, you cannot resync only those rows -- the first run is a full push. Subsequent runs with change tracking are incremental. [src3]
• Double quotes in data: Double quotes in source data fields cause initial sync to fail with MalformedLineException. Data must be cleaned before sync. [src3]
• Cross-company data sharing incompatibility: Dual-write does not support F&O entities with cross-company data sharing enabled (DIPV1002 error). [src5]

Integration Pattern Decision Tree

START -- User needs to sync data between F&O and Dataverse/CE apps
|-- Is the data master data (customers, vendors, products)?
|   |-- YES --> Dual-write with pre-built table maps
|   |-- NO --> Is it transactional data (orders, invoices)?
|       |-- YES --> Dual-write (prospect-to-cash, procure-to-pay)
|       |-- NO --> Consider Data Management Framework or custom integration
|-- What's the data volume per transaction?
|   |-- < 1,000 records --> Standard Dual-write live sync
|   |-- 1,000-500,000 records --> Split into transactions of 1,000 records each
|   |-- > 500,000 records --> Migrate independently, skip initial sync
|-- Do you need bidirectional sync?
|   |-- YES --> Dual-write (design conflict resolution via "Master" setting)
|   |-- NO, read-only from F&O --> Consider Virtual Entities (no data duplication)
|-- Is the F&O environment cloud-hosted?
|   |-- YES --> Dual-write supported
|   |-- NO (on-premise) --> Dual-write NOT supported; use OData or custom integration
|-- Encountering timeouts?
|   |-- Transaction timeout (2 min) --> Optimize Dataverse plugins, reduce mapped fields
|   |-- Initial sync timeout --> Check data volume against limits

Quick Reference: Pre-built Table Maps

Step-by-Step Integration Guide

1. Link F&O and Dataverse environments

Establish the Power Platform integration by connecting your F&O environment to a Dataverse instance via LCS or Power Platform Admin Center. [src1]

Via LCS:
1. Open LCS > Environment details for your F&O environment
2. Click "Power Platform Integration" > "Setup"
3. Select existing Dataverse environment or create new one
4. Confirm linking

Verify: In F&O, navigate to System Administration > Setup > Dual-write -- the admin workspace should appear.

2. Install Dual-write Marketplace solutions

Install the two required solutions on your Dataverse environment from the Dynamics 365 admin center. [src1]

Via Power Platform Admin Center:
1. Navigate to admin.powerplatform.microsoft.com
2. Select your Dataverse environment
3. Go to Resources > Dynamics 365 apps
4. Install "Dual-write core solution" and "Dual-write application solution"
5. Wait 10-30 minutes for installation

Verify: Open Dual-write admin workspace in F&O -- table maps should populate.

3. Configure and run initial synchronization

Run initial sync following the dependency order: Company > Currency > Customers > Vendors > Products > Transactional data. [src3]

Recommended order:
1. Company and currencies (prerequisites)
2. Chart of accounts and financial dimensions
3. Customers V3 (single-threaded: <70K rows from Dataverse)
4. Vendors V2 (single-threaded: <70K rows from Dataverse)
5. Products (multi-threaded: up to 500K rows)
6. Sales orders and lines
7. Remaining maps

For tables >500K rows: migrate independently + skip initial sync

Verify: Check Initial sync details tab -- status should show Completed.

4. Configure alert notifications for production

Set up error thresholds to automatically pause Dual-write during outages. [src4]

In Dual-write admin workspace:
1. Select table map to monitor
2. Click "Create alert settings"
3. Configure: 10 Application errors in 15 minutes > Pause + email
4. Restart table map for alerts to take effect

Verify: Trigger a test error and confirm notification delivery + automatic pause.

Code Examples

X++: Split large transactions into Dual-write-safe batches

// Input:  Collection of records to create in F&O (syncs to Dataverse)
// Output: All records created in batches of 1,000 within 2-min timeout

int batchCounter = 0;
boolean commitPending = false;

while select myRecordBuffer
    where myRecordBuffer.Status == MyStatus::Pending
{
    if (batchCounter == 0)
    {
        ttsbegin;
        commitPending = true;
    }

    myRecordBuffer.insert(); // Triggers Dual-write sync

    batchCounter++;

    if (batchCounter >= 1000)
    {
        ttscommit;
        commitPending = false;
        batchCounter = 0;
    }
}

if (commitPending)
{
    ttscommit; // Commit remaining records
}

PowerShell: Monitor Dual-write map status

# Input:  Dataverse environment URL + access token
# Output: List of Dual-write table maps and status

$envUrl = "https://yourorg.crm.dynamics.com"
$token = "Bearer <your-access-token>"

$response = Invoke-RestMethod `
  -Uri "$envUrl/api/data/v9.2/dualwriteentitymaps" `
  -Headers @{ "Authorization" = $token; "Accept" = "application/json" } `
  -Method Get

$response.value | ForEach-Object {
    [PSCustomObject]@{
        Name       = $_.msdyn_name
        Status     = $_.msdyn_status
        LastSync   = $_.msdyn_lastsynctime
        ErrorCount = $_.msdyn_errorcount
    }
} | Format-Table -AutoSize

Data Mapping

Table Map Architecture

Data Type Gotchas

• Currency decimal precision: Dual-write extends Dataverse currency fields from 4 to up to 10 decimal places. Requires opt-in feature toggle; without it, rounding differences cause sync failures. [src1]
• Date effectivity: F&O supports date-effective records (past, present, future on same table). Dual-write adds this concept to Dataverse tables. [src1]
• Company/Legal Entity scoping: Every F&O record is scoped to a legal entity (DataAreaId). Company must be synced before any company-scoped data. [src3]
• Double quotes in string fields: Cause MalformedLineException during initial sync. Must be cleaned from source data. [src3]

Error Handling & Failure Points

Common Error Codes

Failure Points in Production

• Transaction timeout during high-volume operations: Synchronous Dataverse plugins consume the 2-minute window. Fix: Move heavy plugins to async; reduce mapped field count. [src2]
• Initial sync stuck at 0%: F&O data export taking >5 min due to virtual columns or missing indexes. Fix: Add missing indexes; update to PU37+. [src3]
• Catch-up queue purge: Error records auto-deleted after 1 day. Fix: Monitor daily; retry or export before 24-hour purge. [src4]
• Legal entity limit error: >40 legal entities during setup triggers "Exceeds maximum partitions." Fix: Link only needed entities; 250 limit applies post-setup. [src3]
• Cascading map failures: Stopping parent map while dependent maps run causes failures. Fix: Stop in reverse dependency order; restart: Company > Currency > Customers. [src3, src7]
• Data conflicts on resume: Records fail validation in destination after pause/resume. Fix: Review catch-up errors tab; retry after fixing validation issues. [src4]

Anti-Patterns

Wrong: Running Dual-write maps during bulk data migration

// BAD -- Each migrated record triggers individual sync, destroying performance
1. Enable Dual-write map for Customers V3
2. Start DMF import of 200,000 customers
3. Each insert triggers sync -- 200K individual operations
4. Result: hours instead of minutes; possible timeouts

Correct: Complete migration first, then enable Dual-write

// GOOD -- Migrate independently, then enable live sync
1. Import 200,000 customers into F&O via DMF
2. Import matching 200,000 accounts into Dataverse
3. Enable Dual-write maps with "Skip initial sync"
4. Result: migration in minutes; Dual-write handles only new changes

Wrong: Creating >1,000 records in a single X++ transaction

// BAD -- Exceeds Dual-write 1,000-record limit
ttsbegin;
while select forUpdate myRecord where myRecord.Status == Status::New
{
    myRecord.Status = Status::Active;
    myRecord.update(); // All 5,000 updates in ONE transaction
}
ttscommit; // FAILS: Dual-write rejects >1,000 records

Correct: Batch records into groups of 1,000

// GOOD -- Split into safe batches
int counter = 0;
ttsbegin;
while select forUpdate myRecord where myRecord.Status == Status::New
{
    myRecord.Status = Status::Active;
    myRecord.update();
    counter++;
    if (counter >= 1000) { ttscommit; ttsbegin; counter = 0; }
}
ttscommit;

Wrong: Running Contact initial sync while Customer map is active

// BAD -- Shared address tables cause lock contention
1. Customer V3 map: Running (live sync active)
2. Start initial sync for Contacts
3. Result: performance degradation, address table locks, errors

Correct: Pause Customer map during Contact initial sync

// GOOD -- Stop conflicting maps first
1. Pause Customer V3 map
2. Run Contact initial sync to completion
3. Resume Customer V3 map (catchup handles queued changes)

Common Pitfalls

• Not syncing prerequisite maps first: Company and Currency must be synced before company-scoped data. Fix: Follow dependency order: Company > Currency > Customers > Vendors > Products. [src3]
• Sandbox != production limits: Sandbox has lower Dataverse API limits and less compute. Fix: Load-test with production-equivalent data volumes. [src7]
• Ignoring single-threaded constraints: Treating Customers V3 as multi-threaded leads to timeouts >70K rows. Fix: Migrate single-threaded tables independently; skip initial sync. [src3]
• Missing Dual-Write security roles: Users without Runtime User or App User roles fail on synced tables. Fix: Assign both roles to all CE users in Dual-write processes. [src3]
• Heavy synchronous plugins on synced tables: Custom plugins consume the 2-minute timeout budget. Fix: Convert to async; optimize to <500ms. [src2, src7]
• Unmonitored error queues: Catch-up errors purged after 24 hours = permanent data loss. Fix: Configure alert notifications in admin workspace; set email alerts. [src4]

Diagnostic Commands

# Check Dual-write map status in F&O
# Navigate: System Administration > Setup > Dual-write > Table maps

# Check initial sync progress
# Dual-write admin workspace: select map > "Initial sync details" tab

# View catch-up errors after resume
# Dual-write admin workspace: select map > "Catch-up errors" tab

# Check Dataverse API limits usage
# Power Platform Admin Center > Environments > Analytics > API calls

# Test environment connectivity
# Dual-write admin workspace: "Test connection" button

# View activity log for a table map
# Dual-write admin workspace: select map > "Activity log" tab

# Download detailed error logs
# Activity log: click event > "Download logs"

Version History & Compatibility

When to Use / When Not to Use

Cross-System Comparison

Important Caveats

• Dual-write is cloud-only: on-premise F&O deployments cannot use it. Hybrid scenarios require Azure-based middleware. [src1]
• The 2-minute timeout includes ALL Dataverse processing: standard plugins, custom plugins, workflows, and business rules all consume from the same budget. Heavy customization is the #1 cause of timeout failures. [src2]
• Initial sync and live sync have different limits: 500K rows per run vs. 1,000 records per transaction. Error handling also differs (full push vs. per-record retry). [src2, src3]
• Microsoft can increase the 2-minute timeout to 5 minutes via support request, but this should be a last resort after optimizing plugins and field mappings. [src2]
• Dual-write pricing is included with F&O licenses -- no additional API call costs. However, Dataverse storage costs increase due to data duplication. [src6]
• Information in this card is subject to change with each Microsoft release wave. Always verify current limits against official Microsoft Learn documentation. [src1]