Episode recorded in Portorož, Slovenia

Johan and Gustav chat with Max Sentchell, a Microsoft Technical Architect who created the popular DW Helper tool out of frustration with manually configuring dual write mappings. His GitHub tool automates the painful process of setting up 80-90 mappings in the correct sequence across multiple environments.

The conversation debunks a major misconception: dual write isn't broken, it just works differently than traditional integrations by syncing database fields directly. Most "dual write errors" actually originate in Finance & Operations or Dataverse, not the connector itself.

The real challenge isn't technical though. Dual write projects fail when organizations treat them as mere technical implementations rather than fundamental workflow changes. CRM and ERP teams can no longer work in silos - they need unified processes, shared deployments, and coordinated database refreshes.

Max's key insight: dual write exposes hidden master data quality issues, but the technology works reliably when teams collaborate properly from day one. The upcoming move to Power Platform Admin Center will make this unified approach more visible to customers.